[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X3HAA604JEY91P8GQ2BQFG":3,"skill-same:01M6X3HAA604JEY91P8GQ2BQFG":109},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6X3HAA604JEY91P8GQ2BQFG","gap-report",null,"After the criteria check has run, lists every piece of evidence still missing from a prior-auth packet and presents the packet as a draft for review. Use when the user says \"what's still missing before we submit this auth\", \"what does the payer still need from us\", \"assemble the submission packet for review\", \"give me the outstanding items on this request\". Do NOT use to check whether the patient meets the payer's criteria or why a request would be pushed back - use criteria-extract instead; do NOT use to locate documents in the chart - use evidence-match instead; do NOT use for general Word reports or documents - use docx instead; do NOT use on a claim the payer already denied - use the denials-appeals-response plugin instead. Never submits, files or uploads anything.","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\u002Fprior-auth-assist\u002Fgap-report\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"gap","gap report","report","reports","when","submit","chart","patient","me","claim","back","files","docx","never","assemble","healthcare","analysis","documents","auth","review","2026-11-10 10:12:30",false,"---\nname: gap-report\ndescription: \"After the criteria check has run, lists every piece of evidence still missing from a prior-auth packet and presents the packet as a draft for review. Use when the user says \\\"what's still missing before we submit this auth\\\", \\\"what does the payer still need from us\\\", \\\"assemble the submission packet for review\\\", \\\"give me the outstanding items on this request\\\". Do NOT use to check whether the patient meets the payer's criteria or why a request would be pushed back - use criteria-extract instead; do NOT use to locate documents in the chart - use evidence-match instead; do NOT use for general Word reports or documents - use docx instead; do NOT use on a claim the payer already denied - use the denials-appeals-response plugin instead. Never submits, files or uploads anything.\"\nlicense: MIT\nmetadata: {version: \"1.0.3\", author: Microsoft Healthcare & Life Sciences Skills, category: analysis, domain: \"Prior Authorisation\", action_level: \"L1\", risk: \"high\", icon: DocumentQuestionMark}\n---\n# Gap Report\n## Purpose\nGive the coordinator an explicit, actionable missing-evidence list and the draft packet, after criteria-extract has run.\n\n## When to Use\n- As the last skill in the chain on every run - including when gaps is empty, to confirm the all-clear explicitly.\n- Standalone asks once a criteria_result exists: \"what's outstanding\", \"what do we still owe the plan\", \"assemble the packet for review\".\n\n## When NOT to Use\n- criteria-extract has not run (there is no criteria_result), or the user asks whether the patient meets the criteria or why the plan would push back - use criteria-extract instead.\n- The user wants the evidence found rather than the gap named - use evidence-match instead.\n- The user wants the justification written - use necessity-draft instead.\n- The user wants a general Word report or document - use docx instead.\n- The payer already denied the claim - use the denials-appeals-response plugin instead.\n- The user wants the packet sent, filed or uploaded to a payer portal - that action does not exist in this package and the request is declined.\n\n## Inputs\n`criteria_result.gaps` (id, text, evidence_key, reason, clause citation); `criteria_result.criteria_met`;\n`criteria_result.determination`; `necessity_narrative`; `packet`; `escalations`.\n\n## Workflow\n1. Read `criteria_result.gaps`, `criteria_result.determination` and `packet` from the contract produced by the engine (tool: `python3 base\u002Fscripts\u002Fcriteria_engine.py --question \u003Ccontract.json> --policy config\u002Fpayer-policy-library.json --out \u003Ccontract.out.json>`, run by criteria-extract).\n2. For every entry in gaps, write one table row: criterion id, policy clause, evidence_key, reason, and the evidence needed, restated from the criterion `text` in the policy library.\n3. If gaps is empty, state explicitly that all required criteria are evidenced and cited - never leave the all-clear implicit.\n4. If determination is out_of_scope, report that no checklist could be assembled and carry the payer-relations escalation forward instead of an empty all-clear.\n5. List met criteria with their citations, then every escalation word for word.\n6. Present the packet block exactly as the engine wrote it - status draft, submitted false.\n\n## Output Format\nA markdown table, one row per gap:\n`| # | Criterion | Clause | evidence_key | Reason | Evidence needed |`\nor the line `All required criteria are evidenced and cited (\u003Cn> of \u003Cn>).`; then `Met:` bullets with citations;\nthen `Escalations:` bullets; then the `packet` JSON exactly as on the contract. The first line always states\n`Not ready - \u003Copen_gaps> open gap(s)` or `No open gaps`; this is never an approval.\n\n## Example\n```\nNot ready - 1 open gap. This is a draft for review, not an approval or denial.\n| # | Criterion | Clause | evidence_key | Reason | Evidence needed |\n| 1 | conservative_therapy_6wk | RAD-7.2 | conservative_therapy_6wk | no_evidence | Documented >=6 weeks conservative therapy (PT and\u002For NSAIDs) with no improvement, cited with note, date and quote |\nMet: no_red_flags, exam_findings - Spine clinic intake note, 2026-09-12\npacket: {\"status\": \"draft\", \"submitted\": false, \"determination\": \"packet_assembled_gaps\", \"clause\": \"RAD-7.2\", \"criteria_met_count\": 2, \"open_gaps\": 1}\n```\n\n## Grounding requirements\nEvery listed gap matches an entry in `criteria_result.gaps` verbatim - nothing is added or summarised out. The\n\"evidence needed\" column restates the criterion text from the policy library; it never names an invented document,\ndeadline, payer instruction or readiness percentage. Counts (open_gaps, criteria_met_count) are read from the\nengine, never recounted by the model.\n\n## Guardrails\n- Action level L1 (draft only): assembles a packet for human review; L2 submit\u002Ffile\u002Fupload actions are not available in this package.\n- Never omit a gap to make the packet look cleaner.\n- Never soften a gap list into \"basically ready\" - the specific evidence_key and clause are always named.\n- Never report a gap as resolved because someone says the document will arrive later.\n- Never change packet.status from draft or packet.submitted from false (prior-auth-rules.md #5).\n- Never present the packet as an approval, denial or clearance, whatever the determination value (prior-auth-rules.md #2).\n\n## Error Handling\n- If criteria_result is missing: stop and hand back to criteria-extract; do not build a gap list by reading the policy yourself.\n- If determination is out_of_scope: report it as such with the payer-relations escalation (prior-auth-rules.md #7), not as an empty all-clear.\n- If a remaining gap needs a document: route it to the prior-auth coordinator role in `config\u002Fescalation-contacts.json`; if that contact is still `[TO CONFIGURE: ...]`, say so rather than naming anyone.\n- If the user asks to upload or submit: decline, and keep the packet as a draft.\n","# Gap Report\n## Purpose\nGive the coordinator an explicit, actionable missing-evidence list and the draft packet, after criteria-extract has run.\n\n## When to Use\n- As the last skill in the chain on every run - including when gaps is empty, to confirm the all-clear explicitly.\n- Standalone asks once a criteria_result exists: \"what's outstanding\", \"what do we still owe the plan\", \"assemble the packet for review\".\n\n## When NOT to Use\n- criteria-extract has not run (there is no criteria_result), or the user asks whether the patient meets the criteria or why the plan would push back - use criteria-extract instead.\n- The user wants the evidence found rather than the gap named - use evidence-match instead.\n- The user wants the justification written - use necessity-draft instead.\n- The user wants a general Word report or document - use docx instead.\n- The payer already denied the claim - use the denials-appeals-response plugin instead.\n- The user wants the packet sent, filed or uploaded to a payer portal - that action does not exist in this package and the request is declined.\n\n## Inputs\n`criteria_result.gaps` (id, text, evidence_key, reason, clause citation); `criteria_result.criteria_met`;\n`criteria_result.determination`; `necessity_narrative`; `packet`; `escalations`.\n\n## Workflow\n1. Read `criteria_result.gaps`, `criteria_result.determination` and `packet` from the contract produced by the engine (tool: `python3 base\u002Fscripts\u002Fcriteria_engine.py --question \u003Ccontract.json> --policy config\u002Fpayer-policy-library.json --out \u003Ccontract.out.json>`, run by criteria-extract).\n2. For every entry in gaps, write one table row: criterion id, policy clause, evidence_key, reason, and the evidence needed, restated from the criterion `text` in the policy library.\n3. If gaps is empty, state explicitly that all required criteria are evidenced and cited - never leave the all-clear implicit.\n4. If determination is out_of_scope, report that no checklist could be assembled and carry the payer-relations escalation forward instead of an empty all-clear.\n5. List met criteria with their citations, then every escalation word for word.\n6. Present the packet block exactly as the engine wrote it - status draft, submitted false.\n\n## Output Format\nA markdown table, one row per gap:\n`| # | Criterion | Clause | evidence_key | Reason | Evidence needed |`\nor the line `All required criteria are evidenced and cited (\u003Cn> of \u003Cn>).`; then `Met:` bullets with citations;\nthen `Escalations:` bullets; then the `packet` JSON exactly as on the contract. The first line always states\n`Not ready - \u003Copen_gaps> open gap(s)` or `No open gaps`; this is never an approval.\n\n## Example\n```\nNot ready - 1 open gap. This is a draft for review, not an approval or denial.\n| # | Criterion | Clause | evidence_key | Reason | Evidence needed |\n| 1 | conservative_therapy_6wk | RAD-7.2 | conservative_therapy_6wk | no_evidence | Documented >=6 weeks conservative therapy (PT and\u002For NSAIDs) with no improvement, cited with note, date and quote |\nMet: no_red_flags, exam_findings - Spine clinic intake note, 2026-09-12\npacket: {\"status\": \"draft\", \"submitted\": false, \"determination\": \"packet_assembled_gaps\", \"clause\": \"RAD-7.2\", \"criteria_met_count\": 2, \"open_gaps\": 1}\n```\n\n## Grounding requirements\nEvery listed gap matches an entry in `criteria_result.gaps` verbatim - nothing is added or summarised out. The\n\"evidence needed\" column restates the criterion text from the policy library; it never names an invented document,\ndeadline, payer instruction or readiness percentage. Counts (open_gaps, criteria_met_count) are read from the\nengine, never recounted by the model.\n\n## Guardrails\n- Action level L1 (draft only): assembles a packet for human review; L2 submit\u002Ffile\u002Fupload actions are not available in this package.\n- Never omit a gap to make the packet look cleaner.\n- Never soften a gap list into \"basically ready\" - the specific evidence_key and clause are always named.\n- Never report a gap as resolved because someone says the document will arrive later.\n- Never change packet.status from draft or packet.submitted from false (prior-auth-rules.md #5).\n- Never present the packet as an approval, denial or clearance, whatever the determination value (prior-auth-rules.md #2).\n\n## Error Handling\n- If criteria_result is missing: stop and hand back to criteria-extract; do not build a gap list by reading the policy yourself.\n- If determination is out_of_scope: report it as such with the payer-relations escalation (prior-auth-rules.md #7), not as an empty all-clear.\n- If a remaining gap needs a document: route it to the prior-auth coordinator role in `config\u002Fescalation-contacts.json`; if that contact is still `[TO CONFIGURE: ...]`, say so rather than naming anyone.\n- If the user asks to upload or submit: decline, and keep the packet as a draft.\n",{"name":5,"license":15,"metadata":55,"description":7},{"icon":56,"risk":57,"author":58,"domain":59,"version":60,"category":46,"action_level":61},"DocumentQuestionMark","high","Microsoft Healthcare & Life Sciences Skills","Prior Authorisation","1.0.3","L1","main","c739e95c35d12a999691ab076c3d4c3095bf8192","submissions\u002Fprior-auth-assist\u002Fgap-report",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill gap-report",{"tool":77,"command":78},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill gap-report",{"tool":80,"command":81},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill gap-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002FSKILL.md",true,[85,91,95,101,105],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"base\u002Fcontracts\u002Fhls.prior-auth-assist.v1.json","REFERENCE","参考文档",9740,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002Fbase\u002Fcontracts\u002Fhls.prior-auth-assist.v1.json",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"base\u002Freferences\u002Fprior-auth-rules.md",7131,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002Fbase\u002Freferences\u002Fprior-auth-rules.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"base\u002Fscripts\u002Fcriteria_engine.py","SCRIPT","脚本",10132,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002Fbase\u002Fscripts\u002Fcriteria_engine.py",{"path":102,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":103,"sourceHtmlUrl":104},"config\u002Fescalation-contacts.json",598,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002Fconfig\u002Fescalation-contacts.json",{"path":106,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":107,"sourceHtmlUrl":108},"config\u002Fpayer-policy-library.json",800,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fprior-auth-assist\u002Fgap-report\u002Fconfig\u002Fpayer-policy-library.json",[110,137,162,188,206,222],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":50},"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",[],[118,119,120,121,122,123,124,125,34,126,127,128,129,130,131,132,133,134,135,136],"decision","map","decision map","stakeholder and decision map","reviews","infer","performance","decide","team","next","customer","how","sequences","do","for","records","missing","single","assess",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":50},"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",[],[145,146,147,148,149,150,151,152,34,153,154,46,126,155,156,157,158,159,160,161],"progress","sales progress update","update","sales","weekly","project","up","meeting prep","updates","done","create","catch","work","change","digest","my","manager",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":174,"publishedAt":50},"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",[169,170,173],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":171,"categoryName":172,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},[44,175,176,42,177,45,43,178,179,180,181,151,182,183,184,185,186,47,34,187],"submission assemble","submission","sources","pptx","guardrail","loading","filing","clean","slide decks","open","only","writing","reviewer",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":50},"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",[],[196,197,198,199,177,45,43,200,179,151,185,119,37,201,34,202,46,203,204,205],"source ingest","source","ingest","SET","definition","database","number","lock","text","transition",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":50},"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",[213],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[215,216,217,42,218,45,219,43,179,124,220,185,119,186,47,34,46,33,221,157],"plan","section plan","section","ready","which","word documents","structure",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":50},"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",[],[230,217,231,45,43,179,151,232,185,119,186,34,202,233,38,234,235,236,237,238],"section draft","draft","clinical","notes","human","at","write","drafts","life"]