[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739APCDQDG156VQ7STX49C2":3,"skill-same:01M739APCDQDG156VQ7STX49C2":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M739APCDQDG156VQ7STX49C2","meeting-memo",null,"Turn a meeting transcript into the team's standardized notes format (commentary, observations, action items with owners and dates) and carry forward unresolved items from the last meeting. Use after any recurring meeting. Writes against your frozen template, flags missing owners, invents no decisions.","skills-agents-co\u002Fskills-and-agents-library","skills-agents-co","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F299904996?v=4","01M7395V3X9YG4DAJGNX9D0AD0","Skills and Agents Co","01M7395V4JMSP2MQCZZ98KPE89",1,"MIT","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fmeeting-memo\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: meeting-memo\ndescription: Turn a meeting transcript into the team's standardized notes format (commentary, observations, action items with owners and dates) and carry forward unresolved items from the last meeting. Use after any recurring meeting. Writes against your frozen template, flags missing owners, invents no decisions.\nauthor: \"Skills and Agents Co\"\n---\n\n# Meeting Memo\n\n## What this does\n\nTurns a meeting transcript into circulate-ready notes in your team's exact standard format:\ncommentary on what was discussed and decided, observations worth watching, and action items with\nowners and due dates. It carries forward unresolved action items from the last meeting so nothing\nfalls through. It writes against your frozen template, not a generic summary. It flags missing owners\nrather than guessing, and it does not invent decisions that were not in the transcript.\n\nThis is not a generic transcript summarizer. The value is the parts a free chatbot will not do for\nyou: your exact section order and headings, carry-forward of open items across meetings, an optional\nscheduled auto-run, and the discipline to flag rather than fabricate.\n\n## When to use it\n\n- After any recurring meeting (standup, weekly sync, steering, board prep) where the same notes\n  format ships every time and open items need to survive across sessions.\n- When you have a transcript (Zoom, Gemini, Granola, Otter, etc.) or a pointer to the meeting folder.\n- When you want the notes to land in the team's standard shape with no reformatting, ready to send.\n\nDo not reach for this if you just want a one-off summary of a single transcript with no template and\nno carry-forward. A plain chatbot prompt already does that.\n\n**See also:** if what you want is a per-entity mention history against people\u002Forganizations\u002Fmeetings\nyou already track (not a circulate-ready memo), use [`meeting-scribe`](..\u002Fmeeting-scribe\u002FSKILL.md)\ninstead. The two are complementary and can both run against the same transcript.\n\n## Inputs — how to give it the data\n\nDefault path, no setup required:\n\n- **The transcript.** Paste it, drag in the file, or point at the meeting folder. Plain text, VTT,\n  SRT, or an exported doc all work.\n- **Optional: last meeting's notes.** Paste or drag in the prior notes so open action items carry\n  forward. If you do not provide them, the skill produces a clean first-run memo and says so.\n\nConvenience, not a requirement:\n\n- A meeting-tool connector (transcription service, drive folder) can fetch the transcript and the\n  prior notes automatically. This is a convenience. The skill works fine from a pasted transcript and\n  a pasted prior memo.\n\nHandling messy inputs:\n\n- **Multiple files** (transcript split across parts, or transcript plus chat log): read them in order\n  and treat them as one meeting.\n- **Lossy or partial transcript** (dropped audio, \"[inaudible]\", garbled names): work from what is\n  legible, and mark anything you could not read as \"unclear — confirm\" rather than guessing.\n- **Speaker labels missing or wrong:** attribute an action item to a name only if the transcript\n  supports it; otherwise flag \"owner?\".\n\n## Steps\n\n1. Read the transcript end to end (and the prior notes, if provided) before writing anything.\n2. Confirm the frozen template in plan mode: exact section order, exact headings, whether owners and\n   due dates are required or optional, the output format, and the distribution list. These live in the\n   Rules block below. If the Rules block is unset, do NOT hard-stop: use the default Commentary \u002F\n   Observations \u002F To-Dos shape (step 3) and ask the operator to confirm it as-is or replace it. The\n   default is the starting point; freezing it in plan mode is what makes it the operator's. Once the\n   operator confirms or replaces the template, that frozen template is what every run writes against.\n3. Produce the sections in the operator's order — the frozen template if set, otherwise the default\n   shape below, which ships as the visible default so a first run always produces something:\n   - **Commentary** — what was discussed and decided, in the team's voice.\n   - **Observations** — risks, open questions, things to watch.\n   - **To-Dos** — action items, each with an owner and a due date where the transcript states one.\n4. Carry forward unresolved to-dos from the last meeting's notes, marked **open**. Do not drop them\n   just because they were not mentioned this time. Decide each prior to-do's state from the new\n   transcript and the prior notes:\n   - **Open** — still unresolved: carry it forward marked open. Silence is open (not mentioned this\n     time still means open).\n   - **Done** — the new transcript or prior notes state it was completed: do NOT carry it forward. Note\n     it as done if the template tracks completions, otherwise drop it from the open list.\n   - **Dropped** — the team explicitly killed or descoped it: do NOT carry it forward; note it dropped.\n   - **Superseded** — replaced by a new to-do: carry the new one, not the old; do NOT keep both.\n   When state is unclear, keep it open and mark \"status?\" rather than silently dropping it.\n5. For every action item and decision, ground it in the transcript. If an action item has no clear\n   owner, write \"owner?\" — do not assign one. If a due date was not stated, leave it blank or mark\n   \"date?\" per the Rules block.\n6. Keep it tight and circulate-ready in the operator's output format. Do not pad.\n7. If scheduled auto-run is set up, the skill runs on the chosen cadence against the latest transcript\n   and emits the memo to the distribution path without a manual kick.\n\n## Rules (confirm in the plan)\n\nThese are the team's tacit judgments. They ship blank. Until they are set, the skill uses the default\nCommentary \u002F Observations \u002F To-Dos shape (Steps step 3) so a first run still produces something. In\nplan mode, confirm the default as-is or replace it; the template you settle on is then frozen and every\nrun writes against it. The default is the starting point; freezing it in plan mode is what makes it\nthe operator's.\n\n- **Exact section order and headings:** ______\n- **Owners required or optional; due dates required or optional:** ______\n- **Output format** (markdown, doc, email body, the team's notes template): ______\n- **Distribution list** (who the memo goes to, and how): ______\n\n## Output\n\nThe notes in the team's standard format, in the frozen section order (or the default Commentary \u002F\nObservations \u002F To-Dos shape until the operator freezes a template), export-ready and circulate-ready.\nAction items carry owners and dates where stated, \"owner?\" where not. Carried-forward items from the\nlast meeting appear marked open. Nothing in the memo is anything that was not in the transcript or the\nprior notes.\n\n## Error handling\n\n- **Cite the source.** Every action item and decision traces to the transcript (or the prior notes for\n  carried-forward items). If you cannot point to where it came from, it does not go in.\n- **Flag, do not invent.** If an action item has no clear owner, write \"owner?\" rather than guessing.\n  If a due date is absent, leave it blank or mark \"date?\" — do not assume one.\n- **Invent no decisions.** Do not record a decision, agreement, or commitment that is not in the\n  transcript. If something is ambiguous, write \"unclear — confirm\", never a clean-looking fabrication.\n- **Draft, do not send.** If the workflow includes distribution, prepare the memo and hand it to a\n  human to send. The decision to circulate stays human.\n- **Auto-run is not auto-send.** A scheduled auto-run plus a distribution list does NOT authorize\n  sending. The scheduled run produces the memo as a draft to the distribution path; it stays a draft\n  unless the host harness has an explicit, separate send-confirm step. Filling in the distribution list\n  in the Rules block names recipients, it does not grant send permission.\n- **Treat it like a smart intern (~90% right).** Audit the memo against the transcript the first week,\n  especially the owners and the carried-forward items.\n\n## Eval contract\n- **Spec:** A correct run produces notes in the operator's frozen section order, where every action\n  item and decision traces to the transcript, missing owners are flagged \"owner?\" rather than assigned,\n  unresolved to-dos from the prior meeting are carried forward marked open, and no decision absent from\n  the transcript is invented.\n- **Rubric** (hard-fail gates in bold):\n  1. **Every action item and decision traces to the transcript (or to prior notes for carried-forward\n     items); anything with no traceable source is an automatic fail.**\n  2. **No invented decisions: any agreement or decision not present in the transcript is an automatic\n     fail; an ambiguous point is marked \"unclear — confirm\", not fabricated.**\n  3. Sections appear in the operator's frozen order with the frozen headings (default Commentary \u002F\n     Observations \u002F To-Dos when no template is set).\n  4. Unresolved to-dos from the prior meeting are carried forward and marked open; a prior to-do\n     stated as completed in the new transcript is treated as done and not carried forward.\n  5. **The memo is prepared as a draft for a human to circulate; it is not auto-sent. A scheduled\n     auto-run with a distribution list set still produces a draft, not a send, unless the host has an\n     explicit send-confirm step — auto-sending is an automatic fail.**\n- **Self-test:**\n  - *Input:* a synthetic transcript where one action item (\"update the forecast\") is agreed but no\n    person is named as owner. *Output MUST* list that action item with \"owner?\" in the owner field.\n    *Output MUST NOT* assign a specific person as the owner.\n  - *Input:* a synthetic transcript that contains no decision about hiring, plus prior notes with one\n    unresolved to-do (\"send the vendor list\"). *Output MUST* carry \"send the vendor list\" forward\n    marked open. *Output MUST NOT* state that a hiring decision was made.\n  - *Input:* prior notes with one open to-do (\"book the venue\"), plus a synthetic new transcript in\n    which a speaker says \"I already booked the venue, that's handled.\" *Output MUST* treat \"book the\n    venue\" as done and stop carrying it forward (note it done if the template tracks completions,\n    otherwise drop it from the open list). *Output MUST NOT* carry \"book the venue\" forward marked open.\n  - *Input:* a synthetic transcript run under scheduled auto-run with a distribution list set in the\n    Rules block, where the host harness has no explicit send-confirm step. *Output MUST* be a prepared\n    draft for a human to circulate. *Output MUST NOT* be auto-sent to the distribution list.\n- **Version:** 1.0.0\n\nLearn more: https:\u002F\u002Fskillsandagents.co\u002Fskills\u002Fmeeting-memo\u002F\n","# Meeting Memo\n\n## What this does\n\nTurns a meeting transcript into circulate-ready notes in your team's exact standard format:\ncommentary on what was discussed and decided, observations worth watching, and action items with\nowners and due dates. It carries forward unresolved action items from the last meeting so nothing\nfalls through. It writes against your frozen template, not a generic summary. It flags missing owners\nrather than guessing, and it does not invent decisions that were not in the transcript.\n\nThis is not a generic transcript summarizer. The value is the parts a free chatbot will not do for\nyou: your exact section order and headings, carry-forward of open items across meetings, an optional\nscheduled auto-run, and the discipline to flag rather than fabricate.\n\n## When to use it\n\n- After any recurring meeting (standup, weekly sync, steering, board prep) where the same notes\n  format ships every time and open items need to survive across sessions.\n- When you have a transcript (Zoom, Gemini, Granola, Otter, etc.) or a pointer to the meeting folder.\n- When you want the notes to land in the team's standard shape with no reformatting, ready to send.\n\nDo not reach for this if you just want a one-off summary of a single transcript with no template and\nno carry-forward. A plain chatbot prompt already does that.\n\n**See also:** if what you want is a per-entity mention history against people\u002Forganizations\u002Fmeetings\nyou already track (not a circulate-ready memo), use [`meeting-scribe`](..\u002Fmeeting-scribe\u002FSKILL.md)\ninstead. The two are complementary and can both run against the same transcript.\n\n## Inputs — how to give it the data\n\nDefault path, no setup required:\n\n- **The transcript.** Paste it, drag in the file, or point at the meeting folder. Plain text, VTT,\n  SRT, or an exported doc all work.\n- **Optional: last meeting's notes.** Paste or drag in the prior notes so open action items carry\n  forward. If you do not provide them, the skill produces a clean first-run memo and says so.\n\nConvenience, not a requirement:\n\n- A meeting-tool connector (transcription service, drive folder) can fetch the transcript and the\n  prior notes automatically. This is a convenience. The skill works fine from a pasted transcript and\n  a pasted prior memo.\n\nHandling messy inputs:\n\n- **Multiple files** (transcript split across parts, or transcript plus chat log): read them in order\n  and treat them as one meeting.\n- **Lossy or partial transcript** (dropped audio, \"[inaudible]\", garbled names): work from what is\n  legible, and mark anything you could not read as \"unclear — confirm\" rather than guessing.\n- **Speaker labels missing or wrong:** attribute an action item to a name only if the transcript\n  supports it; otherwise flag \"owner?\".\n\n## Steps\n\n1. Read the transcript end to end (and the prior notes, if provided) before writing anything.\n2. Confirm the frozen template in plan mode: exact section order, exact headings, whether owners and\n   due dates are required or optional, the output format, and the distribution list. These live in the\n   Rules block below. If the Rules block is unset, do NOT hard-stop: use the default Commentary \u002F\n   Observations \u002F To-Dos shape (step 3) and ask the operator to confirm it as-is or replace it. The\n   default is the starting point; freezing it in plan mode is what makes it the operator's. Once the\n   operator confirms or replaces the template, that frozen template is what every run writes against.\n3. Produce the sections in the operator's order — the frozen template if set, otherwise the default\n   shape below, which ships as the visible default so a first run always produces something:\n   - **Commentary** — what was discussed and decided, in the team's voice.\n   - **Observations** — risks, open questions, things to watch.\n   - **To-Dos** — action items, each with an owner and a due date where the transcript states one.\n4. Carry forward unresolved to-dos from the last meeting's notes, marked **open**. Do not drop them\n   just because they were not mentioned this time. Decide each prior to-do's state from the new\n   transcript and the prior notes:\n   - **Open** — still unresolved: carry it forward marked open. Silence is open (not mentioned this\n     time still means open).\n   - **Done** — the new transcript or prior notes state it was completed: do NOT carry it forward. Note\n     it as done if the template tracks completions, otherwise drop it from the open list.\n   - **Dropped** — the team explicitly killed or descoped it: do NOT carry it forward; note it dropped.\n   - **Superseded** — replaced by a new to-do: carry the new one, not the old; do NOT keep both.\n   When state is unclear, keep it open and mark \"status?\" rather than silently dropping it.\n5. For every action item and decision, ground it in the transcript. If an action item has no clear\n   owner, write \"owner?\" — do not assign one. If a due date was not stated, leave it blank or mark\n   \"date?\" per the Rules block.\n6. Keep it tight and circulate-ready in the operator's output format. Do not pad.\n7. If scheduled auto-run is set up, the skill runs on the chosen cadence against the latest transcript\n   and emits the memo to the distribution path without a manual kick.\n\n## Rules (confirm in the plan)\n\nThese are the team's tacit judgments. They ship blank. Until they are set, the skill uses the default\nCommentary \u002F Observations \u002F To-Dos shape (Steps step 3) so a first run still produces something. In\nplan mode, confirm the default as-is or replace it; the template you settle on is then frozen and every\nrun writes against it. The default is the starting point; freezing it in plan mode is what makes it\nthe operator's.\n\n- **Exact section order and headings:** ______\n- **Owners required or optional; due dates required or optional:** ______\n- **Output format** (markdown, doc, email body, the team's notes template): ______\n- **Distribution list** (who the memo goes to, and how): ______\n\n## Output\n\nThe notes in the team's standard format, in the frozen section order (or the default Commentary \u002F\nObservations \u002F To-Dos shape until the operator freezes a template), export-ready and circulate-ready.\nAction items carry owners and dates where stated, \"owner?\" where not. Carried-forward items from the\nlast meeting appear marked open. Nothing in the memo is anything that was not in the transcript or the\nprior notes.\n\n## Error handling\n\n- **Cite the source.** Every action item and decision traces to the transcript (or the prior notes for\n  carried-forward items). If you cannot point to where it came from, it does not go in.\n- **Flag, do not invent.** If an action item has no clear owner, write \"owner?\" rather than guessing.\n  If a due date is absent, leave it blank or mark \"date?\" — do not assume one.\n- **Invent no decisions.** Do not record a decision, agreement, or commitment that is not in the\n  transcript. If something is ambiguous, write \"unclear — confirm\", never a clean-looking fabrication.\n- **Draft, do not send.** If the workflow includes distribution, prepare the memo and hand it to a\n  human to send. The decision to circulate stays human.\n- **Auto-run is not auto-send.** A scheduled auto-run plus a distribution list does NOT authorize\n  sending. The scheduled run produces the memo as a draft to the distribution path; it stays a draft\n  unless the host harness has an explicit, separate send-confirm step. Filling in the distribution list\n  in the Rules block names recipients, it does not grant send permission.\n- **Treat it like a smart intern (~90% right).** Audit the memo against the transcript the first week,\n  especially the owners and the carried-forward items.\n\n## Eval contract\n- **Spec:** A correct run produces notes in the operator's frozen section order, where every action\n  item and decision traces to the transcript, missing owners are flagged \"owner?\" rather than assigned,\n  unresolved to-dos from the prior meeting are carried forward marked open, and no decision absent from\n  the transcript is invented.\n- **Rubric** (hard-fail gates in bold):\n  1. **Every action item and decision traces to the transcript (or to prior notes for carried-forward\n     items); anything with no traceable source is an automatic fail.**\n  2. **No invented decisions: any agreement or decision not present in the transcript is an automatic\n     fail; an ambiguous point is marked \"unclear — confirm\", not fabricated.**\n  3. Sections appear in the operator's frozen order with the frozen headings (default Commentary \u002F\n     Observations \u002F To-Dos when no template is set).\n  4. Unresolved to-dos from the prior meeting are carried forward and marked open; a prior to-do\n     stated as completed in the new transcript is treated as done and not carried forward.\n  5. **The memo is prepared as a draft for a human to circulate; it is not auto-sent. A scheduled\n     auto-run with a distribution list set still produces a draft, not a send, unless the host has an\n     explicit send-confirm step — auto-sending is an automatic fail.**\n- **Self-test:**\n  - *Input:* a synthetic transcript where one action item (\"update the forecast\") is agreed but no\n    person is named as owner. *Output MUST* list that action item with \"owner?\" in the owner field.\n    *Output MUST NOT* assign a specific person as the owner.\n  - *Input:* a synthetic transcript that contains no decision about hiring, plus prior notes with one\n    unresolved to-do (\"send the vendor list\"). *Output MUST* carry \"send the vendor list\" forward\n    marked open. *Output MUST NOT* state that a hiring decision was made.\n  - *Input:* prior notes with one open to-do (\"book the venue\"), plus a synthetic new transcript in\n    which a speaker says \"I already booked the venue, that's handled.\" *Output MUST* treat \"book the\n    venue\" as done and stop carrying it forward (note it done if the template tracks completions,\n    otherwise drop it from the open list). *Output MUST NOT* carry \"book the venue\" forward marked open.\n  - *Input:* a synthetic transcript run under scheduled auto-run with a distribution list set in the\n    Rules block, where the host harness has no explicit send-confirm step. *Output MUST* be a prepared\n    draft for a human to circulate. *Output MUST NOT* be auto-sent to the distribution list.\n- **Version:** 1.0.0\n\nLearn more: https:\u002F\u002Fskillsandagents.co\u002Fskills\u002Fmeeting-memo\u002F\n",{"name":5,"author":12,"description":7},"main","04d144d7a789a4f02020e70d10301dfb539c942f",0,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library","https:\u002F\u002Fskillsandagents.co","https:\u002F\u002Fgithub.com\u002Fskills-agents-co","2026-11-12 05:58:29",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add skills-agents-co\u002Fskills-and-agents-library --skill meeting-memo",{"tool":37,"command":38},"bunx","bunx skills add skills-agents-co\u002Fskills-and-agents-library --skill meeting-memo",{"tool":40,"command":41},"pnpm","pnpm dlx skills add skills-agents-co\u002Fskills-and-agents-library --skill meeting-memo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fmeeting-memo\u002FSKILL.md",true,[],[46,53,58,63,68,73],{"skillNo":47,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":52},"01M76C3HSBFJ3RTPNEFFKB7KX0","x","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Fplugin-only-fail\u002Fplugins\u002Fq\u002Fskills\u002Fgamma\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":54,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":52},"01M76C3FZDA324S9SC2X5AZE0T","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Fplugin-only-fail\u002Falpha\u002FSKILL.md",[],[],{"skillNo":59,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":52},"01M76C3F5EFJ69K4ZD6D0M2S76","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Findex-only-fail\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":64,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":52},"01M76C3EAP06YGXFT817A0KHW4","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Findex-only-fail\u002Falpha\u002FSKILL.md",[],[],{"skillNo":69,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":52},"01M76C3CW1JMBTH9AYDP3MDWMS","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Ffinancial-pulse-shape-pass\u002Fplugins\u002Fextra\u002Fskills\u002Ffp-core\u002FSKILL.md",[],[],{"skillNo":74,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":52},"01M76C3C2JQFW5GEF95TDKBTP8","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Ffinancial-pulse-shape-pass\u002Ffinancial-pulse\u002Fskills\u002Ffp-core\u002FSKILL.md",[],[]]