[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X33XSFHW9AX53JJSTCGRWR":3,"skill-same:01M6X33XSFHW9AX53JJSTCGRWR":74},{"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":19,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6X33XSFHW9AX53JJSTCGRWR","forecast-review-prep",null,"Builds a one-page pre-read for an upcoming forecast review, business review, or operating review by pulling the calendar event, recent email and chat discussion, attendee roles, and last cycle's open items into a structured brief. Use when the user asks to \"prep me for the forecast review\", \"build the pre-read for the QBR\", \"brief me for the business review\", \"get me ready for the operating review\", or \"what is still open from last cycle\". Do NOT use for anticipating specific questions (use stakeholder-qa-prep), building the forecast itself, or general meeting prep.","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\u002Ffinance-for-cowork\u002Fskills\u002Fforecast-review-prep\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffinance-for-cowork\u002Fskills\u002Fforecast-review-prep\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"forecast review","review","prep","forecast review prep","forecast","qa","meeting prep","open","general","qbr","cycle","event","page","for","email","get","ready","do","brief","operating","2026-11-10 10:12:30",false,"---\r\nname: \"forecast-review-prep\"\r\ndescription: >-\r\n  Builds a one-page pre-read for an upcoming forecast review, business review,\r\n  or operating review by pulling the calendar event, recent email and chat\r\n  discussion, attendee roles, and last cycle's open items into a structured\r\n  brief. Use when the user asks to \"prep me for the forecast review\", \"build the\r\n  pre-read for the QBR\", \"brief me for the business review\", \"get me ready for\r\n  the operating review\", or \"what is still open from last cycle\". Do NOT use for\r\n  anticipating specific questions (use stakeholder-qa-prep), building the\r\n  forecast itself, or general meeting prep.\r\nmetadata:\r\n  icon: ChartMultiple\r\nlicense: MIT\r\n---\r\n\r\n# Forecast \u002F Business Review Prep\r\n\r\nA single-screen brief for an upcoming review: what it is, who's in the room, what they'll likely\r\nfocus on, the numbers to have ready, and what's still open from last cycle.\r\n\r\n## When NOT to Use\r\n\r\n- **General meeting prep for any meeting type** → outside this skill's scope\r\n- **Building the forecast or model itself** → spreadsheet or BI work, do that first\r\n- **Anticipating and pre-answering specific questions** → use `stakeholder-qa-prep`\r\n- **1:1 prep** → outside this skill's scope\r\n\r\n## Related Skills\r\n\r\nHand off rather than overlap:\r\n\r\n- Anticipating and pre-answering questions — use stakeholder-qa-prep instead.\r\n- A slide-format prep pack — use pptx instead.\r\n- Writing the variance narrative itself — use variance-commentary instead.\r\n- Close-cycle status — use close-status-digest instead.\r\n- General meeting prep of any type — outside this skill's scope.\r\n\r\n## Workflow\r\n\r\n### 1. Find the meeting\r\n\r\n`outlook_calendar-ListCalendarView` from now through the next seven days, matched on the subject\r\nkeywords the user used. If they named it exactly, use that. If several candidates remain, list\r\nthem with `core-AskUserQuestion` — never guess between two plausible reviews.\r\n\r\nCapture subject, start time in the user's local time zone, organizer, and attendees.\r\n\r\n### 2. Identify the senior attendee\r\n\r\nScan the attendee list and resolve unfamiliar names with `me_profile-GetUserDetails` or\r\n`me_profile-SearchPeople` to surface role and team. The most senior person in the room is\r\neffectively who the user is preparing for — anchor the focus areas around them.\r\n\r\nNever infer seniority from a name or email pattern; resolve it from the directory or leave it\r\nunstated.\r\n\r\n### 3. Gather context — run these in parallel\r\n\r\n- `m365_search-SearchM365` with `sources=[\"email\",\"teams\"]` on the meeting subject and its key\r\n  metrics, last 14 days\r\n- `m365_search-SearchM365` with `sources=[\"files\"]` for pre-read documents referenced in those\r\n  threads\r\n- `outlook-ListMessages` filtered to the senior attendee, last 7 days\r\n- If the meeting recurs, find the prior occurrence with `outlook_calendar-ListEvents` and pull its\r\n  follow-up thread for open action items\r\n\r\n### 4. Draft the brief\r\n\r\nFixed structure, capped at roughly one screen:\r\n\r\n- **Meeting** — subject, time, organizer, attendees with roles\r\n- **Likely focus** — what's top of mind based on retrieved discussion\r\n- **Key numbers to know** — only figures found in retrieved context\r\n- **Questions to anticipate** — 3-5 the senior attendee is likely to raise\r\n- **Open items from last cycle** — outstanding follow-ups with owners\r\n- **Materials** — bracketed links to documents found, e.g. `[file_1]`\r\n\r\n## Output Format\r\n\r\nInline markdown. Write a file only if the user asks for one.\r\n\r\n## When Things Fail\r\n\r\n- **No matching meeting found** — say so and ask for the meeting name; do not brief on a guessed event.\r\n- **Attendee lookup fails** — list the attendee without a role rather than inferring seniority.\r\n- **Search returns nothing** — deliver the brief with the sections you have and state plainly that no recent discussion was found. An empty \"Likely focus\" is a valid answer.\r\n- **Prior occurrence missing** — omit the open-items section and say the prior cycle wasn't found.\r\n- **A tool errors** — retry once, then continue and disclose the gap in plain language.\r\n\r\n### Example output\r\n\r\n```text\r\nMeeting    Q3 Business Review - Thu 14 May, 9:00-10:00 PT\r\n           Organizer: J. Alvarez - 7 attendees\r\n           Most senior: M. Chen (VP Finance)\r\n\r\nLikely focus   Renewal timing and the services margin dip flagged twice\r\n               in last week's thread\r\n\r\nKey numbers    Revenue $42.1M vs $40.3M plan (+4.5%)\r\n               Services margin 61% vs 64% prior quarter\r\n               Pipeline coverage [Verify before review]\r\n\r\nAnticipate     1. Is the renewal pull-forward timing or run-rate?\r\n               2. What recovers the 300bps of services margin?\r\n               3. Does coverage support next quarter's number?\r\n\r\nOpen items     Pricing exception policy - due from last cycle, still open\r\n```\r\n\r\n## Guardrails\r\n\r\n- **Never invent a metric.** If a number isn't in retrieved context, write `[Verify before\r\n  review]` rather than supplying a plausible figure. A brief with visible gaps is useful; a brief\r\n  with invented numbers is dangerous in front of an executive.\r\n- If no relevant context surfaces, say so honestly — do not pad with generic preparation advice.\r\n- For meetings marked private or confidential, surface the time block only, not subject details.\r\n- Surface disagreements between attendees' recent positions rather than smoothing them over.\r\n- Never evaluate an individual's performance, even by implication.\r\n- If the brief would run past one screen, cut the least decision-relevant section rather than truncating mid-list.\r\n- Never infer a person's role, seniority, or reporting line from their name or email address.\r\n- Confirm before writing any file — the default is inline.\r\n","# Forecast \u002F Business Review Prep\r\n\r\nA single-screen brief for an upcoming review: what it is, who's in the room, what they'll likely\r\nfocus on, the numbers to have ready, and what's still open from last cycle.\r\n\r\n## When NOT to Use\r\n\r\n- **General meeting prep for any meeting type** → outside this skill's scope\r\n- **Building the forecast or model itself** → spreadsheet or BI work, do that first\r\n- **Anticipating and pre-answering specific questions** → use `stakeholder-qa-prep`\r\n- **1:1 prep** → outside this skill's scope\r\n\r\n## Related Skills\r\n\r\nHand off rather than overlap:\r\n\r\n- Anticipating and pre-answering questions — use stakeholder-qa-prep instead.\r\n- A slide-format prep pack — use pptx instead.\r\n- Writing the variance narrative itself — use variance-commentary instead.\r\n- Close-cycle status — use close-status-digest instead.\r\n- General meeting prep of any type — outside this skill's scope.\r\n\r\n## Workflow\r\n\r\n### 1. Find the meeting\r\n\r\n`outlook_calendar-ListCalendarView` from now through the next seven days, matched on the subject\r\nkeywords the user used. If they named it exactly, use that. If several candidates remain, list\r\nthem with `core-AskUserQuestion` — never guess between two plausible reviews.\r\n\r\nCapture subject, start time in the user's local time zone, organizer, and attendees.\r\n\r\n### 2. Identify the senior attendee\r\n\r\nScan the attendee list and resolve unfamiliar names with `me_profile-GetUserDetails` or\r\n`me_profile-SearchPeople` to surface role and team. The most senior person in the room is\r\neffectively who the user is preparing for — anchor the focus areas around them.\r\n\r\nNever infer seniority from a name or email pattern; resolve it from the directory or leave it\r\nunstated.\r\n\r\n### 3. Gather context — run these in parallel\r\n\r\n- `m365_search-SearchM365` with `sources=[\"email\",\"teams\"]` on the meeting subject and its key\r\n  metrics, last 14 days\r\n- `m365_search-SearchM365` with `sources=[\"files\"]` for pre-read documents referenced in those\r\n  threads\r\n- `outlook-ListMessages` filtered to the senior attendee, last 7 days\r\n- If the meeting recurs, find the prior occurrence with `outlook_calendar-ListEvents` and pull its\r\n  follow-up thread for open action items\r\n\r\n### 4. Draft the brief\r\n\r\nFixed structure, capped at roughly one screen:\r\n\r\n- **Meeting** — subject, time, organizer, attendees with roles\r\n- **Likely focus** — what's top of mind based on retrieved discussion\r\n- **Key numbers to know** — only figures found in retrieved context\r\n- **Questions to anticipate** — 3-5 the senior attendee is likely to raise\r\n- **Open items from last cycle** — outstanding follow-ups with owners\r\n- **Materials** — bracketed links to documents found, e.g. `[file_1]`\r\n\r\n## Output Format\r\n\r\nInline markdown. Write a file only if the user asks for one.\r\n\r\n## When Things Fail\r\n\r\n- **No matching meeting found** — say so and ask for the meeting name; do not brief on a guessed event.\r\n- **Attendee lookup fails** — list the attendee without a role rather than inferring seniority.\r\n- **Search returns nothing** — deliver the brief with the sections you have and state plainly that no recent discussion was found. An empty \"Likely focus\" is a valid answer.\r\n- **Prior occurrence missing** — omit the open-items section and say the prior cycle wasn't found.\r\n- **A tool errors** — retry once, then continue and disclose the gap in plain language.\r\n\r\n### Example output\r\n\r\n```text\r\nMeeting    Q3 Business Review - Thu 14 May, 9:00-10:00 PT\r\n           Organizer: J. Alvarez - 7 attendees\r\n           Most senior: M. Chen (VP Finance)\r\n\r\nLikely focus   Renewal timing and the services margin dip flagged twice\r\n               in last week's thread\r\n\r\nKey numbers    Revenue $42.1M vs $40.3M plan (+4.5%)\r\n               Services margin 61% vs 64% prior quarter\r\n               Pipeline coverage [Verify before review]\r\n\r\nAnticipate     1. Is the renewal pull-forward timing or run-rate?\r\n               2. What recovers the 300bps of services margin?\r\n               3. Does coverage support next quarter's number?\r\n\r\nOpen items     Pricing exception policy - due from last cycle, still open\r\n```\r\n\r\n## Guardrails\r\n\r\n- **Never invent a metric.** If a number isn't in retrieved context, write `[Verify before\r\n  review]` rather than supplying a plausible figure. A brief with visible gaps is useful; a brief\r\n  with invented numbers is dangerous in front of an executive.\r\n- If no relevant context surfaces, say so honestly — do not pad with generic preparation advice.\r\n- For meetings marked private or confidential, surface the time block only, not subject details.\r\n- Surface disagreements between attendees' recent positions rather than smoothing them over.\r\n- Never evaluate an individual's performance, even by implication.\r\n- If the brief would run past one screen, cut the least decision-relevant section rather than truncating mid-list.\r\n- Never infer a person's role, seniority, or reporting line from their name or email address.\r\n- Confirm before writing any file — the default is inline.\r\n",{"name":5,"license":15,"metadata":45,"description":7},{"icon":46},"ChartMultiple","main","1de89ad8c68145c4968681ec6f224c3217b0e1f8","submissions\u002Ffinance-for-cowork\u002Fskills\u002Fforecast-review-prep",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill forecast-review-prep",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill forecast-review-prep",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill forecast-review-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffinance-for-cowork\u002Fskills\u002Fforecast-review-prep\u002FSKILL.md",true,[70],{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":16},"LICENSE","许可证",1141,[75,101,126,164,183,199],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":40},"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",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,37,33,97,98,99,100],"decision","map","decision map","stakeholder and decision map","reviews","infer","performance","decide","when","team","next","customer","how","sequences","records","missing","single","assess",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":40},"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",[],[109,110,111,112,113,114,115,26,91,116,117,118,92,119,120,121,122,123,124,125],"progress","sales progress update","update","sales","weekly","project","up","updates","done","analysis","create","catch","work","change","digest","my","manager",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":146,"publishedAt":40},"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",[133,138,141],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":139,"categoryName":140,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[147,148,149,150,151,152,153,154,155,156,157,115,158,159,27,160,161,162,91,163],"assemble","submission assemble","submission","docx","sources","healthcare","never","pptx","guardrail","loading","filing","clean","slide decks","only","writing","documents","reviewer",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":40},"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",[],[172,173,174,175,151,152,153,176,155,115,160,84,177,178,91,179,118,180,181,182],"source ingest","source","ingest","SET","definition","patient","database","number","lock","text","transition",{"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":191,"publishedAt":40},"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",[190],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},[192,193,194,150,36,152,195,153,155,89,196,160,84,161,162,91,118,197,198,121],"plan","section plan","section","which","word documents","reports","structure",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":40},"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",[],[207,194,208,152,153,155,115,209,160,84,161,91,179,210,211,212,213,214,215,216],"section draft","draft","clinical","notes","me","human","at","write","drafts","life"]