[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69A1HM83XJW473RFSHBQ2VS":3,"skill-same:01M69A1HM83XJW473RFSHBQ2VS":93},{"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":23,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M69A1HM83XJW473RFSHBQ2VS","acroform-writer",null,"Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include \"fill out the job application form\", \"complete the intake form for [person]\", \"populate our standard NDA template\", and \"make this ready to send \u002F non-editable\" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned\u002Fimage-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",107,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[24,25,26],"acroform writer","PDF","image","2026-11-10 10:12:30",false,"---\nname: acroform-writer\ndescription: >-\n  Use this skill whenever the user wants values written INTO an existing PDF\n  form that lives in the connected SharePoint knowledge source — filling out,\n  completing, populating, or submitting a fillable PDF (application, intake\n  sheet, contract, government form) from data they supply, a spreadsheet row,\n  or the conversation. Triggers include \"fill out the job application form\",\n  \"complete the intake form for [person]\", \"populate our standard NDA\n  template\", and \"make this ready to send \u002F non-editable\" (flatten). The\n  source form should be found via knowledge search; only ask the user to upload\n  it if knowledge search turns up nothing plausible.\n  different task), and do NOT use it on scanned\u002Fimage-only PDFs that have no\n  real fillable fields — those need OCR or manual overlay instead, which this\n  skill explicitly detects and reports rather than silently failing.\n---\n\nFill an existing PDF's real AcroForm fields with supplied data, and\noptionally lock the result read-only so it's ready to send or file without\nfurther edits. The goal is to write into the document's actual form fields —\nnever to paste text over a rendered page image, which drifts out of\nalignment the moment a layout differs even slightly from what you assumed.\n\n## Instructions\n1. **Find the source PDF via knowledge search — do not ask the user to upload it.**\n   The blank fillable form (e.g. a job application, intake sheet, or contract\n   template) lives in the connected SharePoint knowledge source, not as a user\n   upload. Let the user refer to it naturally — by form name, topic, or\n   purpose (\"the job application form\", \"our standard NDA template\") — and use\n   those cues to search knowledge for the best-matching PDF. If exactly one\n   document is a clear match, proceed with it; only ask a brief clarifying\n   question when the match is genuinely ambiguous (multiple similarly-named\n   forms, or no clear candidate).\n2. **Pull the FULL document, not retrieved chunks.** A knowledge search only\n   needs to return enough to *find* the right file — form fields and their\n   full structure can be split or omitted across retrieval chunks. Once the\n   right document is identified, fetch the complete PDF into the sandbox (the\n   SharePoint knowledge source handles this — let it pull the full file down)\n   before doing anything else. Never attempt to reconstruct or fill a form\n   from a partial\u002Fchunked view of it.\n3. **Collect the values to fill.** These come from the conversation, an\n   attached spreadsheet row, or a connector record — collect them into a flat\n   `{field_name: value}` JSON object. Do not guess field names at this stage;\n   that happens against the PDF's real fields in the next step.\n4. **Always list fields first.** Run:\n   ```\n   python scripts\u002Ffill_form.py list \u003Cdownloaded_form.pdf>\n   ```\n   This prints every real form field (name, type, current value, and — for\n   checkboxes\u002Fradios\u002Fdropdowns — the valid states or options). Use this output\n   to map the data you collected in step 3 onto the PDF's actual field names.\n   **If this reports no fields found (exit code 1), stop** — the PDF has no\n   real AcroForm (commonly a scanned or flattened document already). Tell the\n   user this form isn't fillable this way and don't attempt to fake it by\n   drawing text over the page.\n5. **Match data to fields carefully.**\n   - Checkboxes\u002Fradio buttons must be set to one of the exact `states` values\n     reported in step 4 (typically `\u002FYes` and `\u002FOff`), not `true`\u002F`false`.\n   - Dropdown\u002Fchoice fields must use one of the reported `options` values\n     verbatim.\n   - If a value you were given doesn't obviously map to any listed field, do\n     not force it into the closest-sounding one — leave it out and flag it to\n     the user rather than guessing.\n6. **Fill (and lock read-only, if the result should be final):**\n   ```\n   python scripts\u002Ffill_form.py fill \u003Cdownloaded_form.pdf> \u003Cdata.json> \u003Coutput.pdf> [--flatten]\n   ```\n   Add `--flatten` whenever the output is meant to be a finished, submission-\n   ready document (the common case) so the fields are marked read-only and\n   most viewers treat it as no longer editable. This is a best-effort lock,\n   not true flattening — the AcroForm and field definitions still exist in\n   the file, and a viewer that ignores the read-only flag could still edit\n   them. Leave `--flatten` off if the user explicitly wants to keep the\n   fields freely editable for further changes later.\n7. **Check the JSON result the script prints.** It reports `fields_filled` and\n   any `unmatched_fields` — data keys that didn't correspond to a real field.\n   Always surface unmatched fields to the user by name; never fill silently\n   and claim full completion if something was dropped.\n8. **Hand back the file with a short, honest recap:** which form (and, if\n   relevant, where it was sourced from in knowledge), how many fields were\n   filled, whether it was flattened, and any fields left blank or unmatched.\n   Do not paste the filled values back into the chat as a table — the file is\n   the deliverable.\n\n## Guardrails\n- Never ask the user to upload the blank form — find it via knowledge search\n  first. Only fall back to asking the user directly for the file if knowledge\n  search turns up nothing plausible at all.\n- Never fill from a partially retrieved\u002Fchunked view of the form — always\n  work from the complete downloaded PDF (step 2).\n- Never draw or overlay text on a page image to fake-fill a PDF that has no\n  real form fields — detect that case (step 4) and say so plainly instead.\n- Never invent a value for a field the user didn't supply; leave it blank and\n  say so.\n- Never force a supplied value into a checkbox\u002Fradio\u002Fdropdown field using\n  anything other than that field's own reported states\u002Foptions.\n- Don't silently drop unmatched data — always report it.\n- `--flatten` is about locking the PDF read-only, not about changing any of\n  the entered values — never alter data during that step.\n\n## Tone\nPrecise and matter-of-fact. State plainly what was filled, what wasn't, and\nwhy — this skill is often used for documents with real consequences\n(applications, contracts), so avoid overstating completeness.","Fill an existing PDF's real AcroForm fields with supplied data, and\noptionally lock the result read-only so it's ready to send or file without\nfurther edits. The goal is to write into the document's actual form fields —\nnever to paste text over a rendered page image, which drifts out of\nalignment the moment a layout differs even slightly from what you assumed.\n\n## Instructions\n1. **Find the source PDF via knowledge search — do not ask the user to upload it.**\n   The blank fillable form (e.g. a job application, intake sheet, or contract\n   template) lives in the connected SharePoint knowledge source, not as a user\n   upload. Let the user refer to it naturally — by form name, topic, or\n   purpose (\"the job application form\", \"our standard NDA template\") — and use\n   those cues to search knowledge for the best-matching PDF. If exactly one\n   document is a clear match, proceed with it; only ask a brief clarifying\n   question when the match is genuinely ambiguous (multiple similarly-named\n   forms, or no clear candidate).\n2. **Pull the FULL document, not retrieved chunks.** A knowledge search only\n   needs to return enough to *find* the right file — form fields and their\n   full structure can be split or omitted across retrieval chunks. Once the\n   right document is identified, fetch the complete PDF into the sandbox (the\n   SharePoint knowledge source handles this — let it pull the full file down)\n   before doing anything else. Never attempt to reconstruct or fill a form\n   from a partial\u002Fchunked view of it.\n3. **Collect the values to fill.** These come from the conversation, an\n   attached spreadsheet row, or a connector record — collect them into a flat\n   `{field_name: value}` JSON object. Do not guess field names at this stage;\n   that happens against the PDF's real fields in the next step.\n4. **Always list fields first.** Run:\n   ```\n   python scripts\u002Ffill_form.py list \u003Cdownloaded_form.pdf>\n   ```\n   This prints every real form field (name, type, current value, and — for\n   checkboxes\u002Fradios\u002Fdropdowns — the valid states or options). Use this output\n   to map the data you collected in step 3 onto the PDF's actual field names.\n   **If this reports no fields found (exit code 1), stop** — the PDF has no\n   real AcroForm (commonly a scanned or flattened document already). Tell the\n   user this form isn't fillable this way and don't attempt to fake it by\n   drawing text over the page.\n5. **Match data to fields carefully.**\n   - Checkboxes\u002Fradio buttons must be set to one of the exact `states` values\n     reported in step 4 (typically `\u002FYes` and `\u002FOff`), not `true`\u002F`false`.\n   - Dropdown\u002Fchoice fields must use one of the reported `options` values\n     verbatim.\n   - If a value you were given doesn't obviously map to any listed field, do\n     not force it into the closest-sounding one — leave it out and flag it to\n     the user rather than guessing.\n6. **Fill (and lock read-only, if the result should be final):**\n   ```\n   python scripts\u002Ffill_form.py fill \u003Cdownloaded_form.pdf> \u003Cdata.json> \u003Coutput.pdf> [--flatten]\n   ```\n   Add `--flatten` whenever the output is meant to be a finished, submission-\n   ready document (the common case) so the fields are marked read-only and\n   most viewers treat it as no longer editable. This is a best-effort lock,\n   not true flattening — the AcroForm and field definitions still exist in\n   the file, and a viewer that ignores the read-only flag could still edit\n   them. Leave `--flatten` off if the user explicitly wants to keep the\n   fields freely editable for further changes later.\n7. **Check the JSON result the script prints.** It reports `fields_filled` and\n   any `unmatched_fields` — data keys that didn't correspond to a real field.\n   Always surface unmatched fields to the user by name; never fill silently\n   and claim full completion if something was dropped.\n8. **Hand back the file with a short, honest recap:** which form (and, if\n   relevant, where it was sourced from in knowledge), how many fields were\n   filled, whether it was flattened, and any fields left blank or unmatched.\n   Do not paste the filled values back into the chat as a table — the file is\n   the deliverable.\n\n## Guardrails\n- Never ask the user to upload the blank form — find it via knowledge search\n  first. Only fall back to asking the user directly for the file if knowledge\n  search turns up nothing plausible at all.\n- Never fill from a partially retrieved\u002Fchunked view of the form — always\n  work from the complete downloaded PDF (step 2).\n- Never draw or overlay text on a page image to fake-fill a PDF that has no\n  real form fields — detect that case (step 4) and say so plainly instead.\n- Never invent a value for a field the user didn't supply; leave it blank and\n  say so.\n- Never force a supplied value into a checkbox\u002Fradio\u002Fdropdown field using\n  anything other than that field's own reported states\u002Foptions.\n- Don't silently drop unmatched data — always report it.\n- `--flatten` is about locking the PDF read-only, not about changing any of\n  the entered values — never alter data during that step.\n\n## Tone\nPrecise and matter-of-fact. State plainly what was filled, what wasn't, and\nwhy — this skill is often used for documents with real consequences\n(applications, contracts), so avoid overstating completeness.",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Facroform-writer",120,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 09:35:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill acroform-writer",{"tool":47,"command":48},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill acroform-writer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill acroform-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002FSKILL.md",true,[55,61,67,71,75,79,83,87],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fsample_intake_form.pdf","ASSET","资产文件",7828,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002Fassets\u002Fsample_intake_form.pdf",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"metadata.json","REFERENCE","参考文档",438,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002Fmetadata.json",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"README.md",2246,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002FREADME.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Ffix-policy.md",982,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-design-audit\u002Freferences\u002Ffix-policy.md",{"path":76,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fgithub-pr-delivery.md",2215,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-design-audit\u002Freferences\u002Fgithub-pr-delivery.md",{"path":80,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Freport-format.md",1289,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-design-audit\u002Freferences\u002Freport-format.md",{"path":84,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Frubric.md",1824,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-design-audit\u002Freferences\u002Frubric.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Ffill_form.py","SCRIPT","脚本",5888,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Facroform-writer\u002Fscripts\u002Ffill_form.py",[94,122,148,183,202,219],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":27},"01M6X3P09R8SJH3QJGMTAA5N90","stakeholder-and-decision-map","Mines customer interactions to identify stakeholders, infer their likely roles and engagement, map the decision process, and highlight who or what may be missing. Use when asked to \"map a deal's buying group\", identify influential or missing stakeholders, \"assess who has gone quiet\", or \"explain how the customer will decide\". Do not use for phased engagement plans, contact sequences, choosing or drafting outreach to the single next contact, seller or team performance reviews, or contacting, scheduling, or changing records.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstakeholder-and-decision-map\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstakeholder-and-decision-map\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"decision","map","decision map","stakeholder and decision map","reviews","infer","performance","decide","when","team","next","customer","how","sequences","do","for","records","missing","single","assess",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":27},"01M6X3NRES2XSZQCH015WD4JN6","sales-progress-update","Creates or refreshes a sales progress update for a manager or team about work done, deal movement, pending outcomes, supported forecast position, and help needed. Use when asked to \"create my weekly sales update\", \"refresh my sales progress deck\", \"report my forecast position\", \"where do I stand against my quarter forecast\", or \"catch my manager up on committed deals\". Do NOT use for non-sales project updates, a since-date deal change digest, momentum or blocker analysis, meeting prep, or outreach drafting.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-progress-update\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-progress-update\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,110,138,139,140,111,141,142,143,144,145,146,147],"progress","sales progress update","update","sales","weekly","project","up","meeting prep","updates","done","analysis","create","catch","work","change","digest","my","manager",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":164,"publishedAt":27},"01M6X3MSDTB1E5H6DQAFAY41YP","submission-assemble","Put the checked CSR or 510(k) sections together in template order with a reviewer-facing open-items register, as a draft package for human sign-off. Use when the user asks \"assemble the CSR draft\", \"put the module together for review\", \"build the review package with the open items on top\", \"compile the 510(k) sections in order\" or \"package this up for the submission lead\". Do NOT use for assembling an unchecked draft - use consistency-check instead. Do NOT use for loading protocol, SAP or TLF sources - use source-ingest instead. Do NOT use for compiling general documents or slide decks - use the built-in docx or pptx skill instead. Do NOT use for filing or submitting to a regulator - use the sponsor's validated gateway, operated by a human, instead. Guardrail: draft for human approval only (L1); status is draft_clean or draft_open_items, never submitted.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsubmission-assemble\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsubmission-assemble\u002FSKILL.md",[155,156,159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[165,166,167,168,169,170,171,172,173,174,175,136,176,177,178,179,180,181,110,182],"assemble","submission assemble","submission","docx","sources","healthcare","never","pptx","guardrail","loading","filing","clean","slide decks","open","only","writing","documents","reviewer",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":27},"01M6X3MM9TVWDQ716QGNV4DS25","source-ingest","Pull every number, date and population definition out of a study's protocol, SAP, TLF tables, investigator brochure and prior approved text into one cited fact map, keyed per config\u002Ffield-dictionary.json, before any CSR or 510(k) section is written. Use when the user asks \"here's the locked TLF set and SAP, set up the CSR\", \"load the protocol and tables before we start drafting\", \"what figures do we have from the database lock?\", \"pull the disposition counts out of Table 14.1.1\" or \"ingest the IB for the 510(k)\". Do NOT use for drafting or assembling submission sections - use section-draft or submission-assemble instead. Do NOT use for reconciling a patient's medications - use the discharge-care-transition plugin instead. Guardrail: reads and cites sources only; never estimates, rounds or invents a fact.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsource-ingest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsource-ingest\u002FSKILL.md",[],[191,192,193,194,169,170,171,195,173,136,179,103,196,197,110,198,140,199,200,201],"source ingest","source","ingest","SET","definition","patient","database","number","lock","text","transition",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":27},"01M6X3M7ZH5ZNEHP56BQ74HAJR","section-plan","Work out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks \"what do we still need before we can draft the CSR?\", \"which sections are ready to start?\", \"what's blocking the performance data section?\", \"do we have everything for the synopsis?\" or \"map our tables to the E3 structure\". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining general Word documents or business reports - use the built-in docx skill instead. Only structures with a template in config are supported. Guardrail: plans only; never marks a section ready on a missing fact and never invents a structure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-plan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-plan\u002FSKILL.md",[209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,168,214,170,215,171,173,108,216,179,103,180,181,110,140,217,218,143],"plan","section plan","section","ready","which","word documents","reports","structure",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":27},"01M6X3M0V1MJNCR653ES9XGVMS","section-draft","Write or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks \"draft the Synopsis from our locked tables\", \"write up safety from Table 14.3.1\", \"give me a first pass at the discussion\", \"draft the device description for the 510(k)\" or \"tighten the wording of the Discussion section\". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use consistency-check instead. Do NOT use for appeal letters, clinical notes or discharge summaries - use the matching HLS plugin instead. Guardrail: drafts for human approval only (L1); never asserts an unsourced number or harmonises two figures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-draft\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-draft\u002FSKILL.md",[],[227,213,228,170,171,173,136,229,179,103,180,110,198,230,231,232,233,234,235,236],"section draft","draft","clinical","notes","me","human","at","write","drafts","life"]