[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69A7KBF5QDFA7ZWW9C4JR3N":3,"skill-same:01M69A7KBF5QDFA7ZWW9C4JR3N":69},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M69A7KBF5QDFA7ZWW9C4JR3N","pattern-radar",null,"Scan the user's recent Microsoft 365 signals (emails, active chats\u002Fchannels, calendar subjects) to surface recurring patterns worth productizing — either as a blog post (the user explains the same thing repeatedly) or as an automation (the user does the same multi-step task repeatedly). Use when the user asks \"what should I write about?\", \"what could I automate?\", \"find patterns in my work\", or invokes \"\u002Fpattern-radar\".","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\u002Fpattern-radar\u002FSKILL.md",[],[19,20,9],"pattern radar","automation","2026-11-10 10:12:30",false,"---\nname: pattern-radar\ndescription: Scan the user's recent Microsoft 365 signals (emails, active chats\u002Fchannels, calendar subjects) to surface recurring patterns worth productizing — either as a blog post (the user explains the same thing repeatedly) or as an automation (the user does the same multi-step task repeatedly). Use when the user asks \"what should I write about?\", \"what could I automate?\", \"find patterns in my work\", or invokes \"\u002Fpattern-radar\".\n---\n\n# Pattern Radar\n\nFind recurring patterns in the user's recent work signals that could be turned\ninto leverage — a **blog post** (the user keeps explaining the same thing) or an\n**automation** (the user keeps doing the same manual, multi-step task). Give\nblog and automation candidates equal weight; bias toward automation candidates,\nsince offloading repetitive work is usually the bigger win.\n\nDefault lookback window: **the last 7 days** from the current date\u002Ftime. Treat\nthe provided current datetime as authoritative — never reason from training-data\ndates.\n\n> **Tool names.** This skill refers to Microsoft 365 tools as `m365_*`. If your\n> host exposes them under different names, map them to the equivalent capability.\n\n## Inputs — collect breadth, not depth\n\n1. **Email** — list Inbox and Sent from the last 7 days (subjects + first-line\n   previews only; do not open bodies). **Pay special attention to Sent items**:\n   they reveal the user's own repeated outbound actions (forwards, intros, status\n   pings, FYIs, \"looping in X\" handoffs, RSVPs, reschedules).\n2. **Active chats** — list recent chats; for each chat the user has posted in\n   over the last ~30 days, fetch the last 7 days of messages. Strip @-mention\n   noise.\n3. **Active channels** — for channels the user has posted in over the last ~30\n   days, fetch the last 7 days of messages. Skip silent channels.\n4. **Calendar** — list events from the last 7 days (**subjects only** — no\n   bodies, no attendee lists). Look for repeated reschedules, repeated tentative\n   responses, recurring conflict patterns, and meeting-prep cadences.\n\n## Clustering — what counts as a pattern\n\nA signal qualifies only if it appears **≥3 times across ≥2 distinct people \u002F\nchats \u002F customers \u002F threads \u002F events** in the window. Be ruthless — one-offs are\nnoise.\n\n**Blog cluster types**\n\n- **Repeated explanation** — the user answers the same question or explains the\n  same concept to 3+ different people. → blog candidate.\n- **Recurring FAQ** — the same question shows up in 3+ chats\u002Fchannels from\n  different askers. → blog \u002F FAQ candidate.\n\n**Automation cluster types (cast a wide net)**\n\n- **Repeated multi-step manual task** — the same sequence of clicks \u002F drafts \u002F\n  file moves \u002F API calls, repeatedly. → automation candidate.\n- **Repeated handoff \u002F triage** — forwarding, \"looping in\", or intro'ing the\n  same kinds of items to the same people 3+ times. → auto-route by rule or\n  classifier.\n- **Repeated status pings \u002F FYIs** — the same kind of update to the same audience\n  on a cadence. → scheduled digest.\n- **Repeated meeting reschedules** for the same root cause. → auto-propose\n  alternates.\n- **Repeated RSVPs \u002F tentative responses** to recurring meetings with consistent\n  reasoning. → auto-respond by rule.\n- **Repeated meeting prep** — gathering the same context before recurring\n  meetings. → pre-meeting brief.\n- **Repeated doc\u002Fwiki updates** — manually appending the same kind of content on\n  a cadence. → scheduled ingest.\n- **Repeated approvals \u002F sign-offs** of the same class of request. → rule-based\n  pre-screen.\n- **Repeated file\u002Fdata shuttling** — move\u002Frename\u002Freformat between systems. →\n  pipeline.\n- **Repeated drafting** — near-identical emails\u002Fmessages (welcome notes,\n  onboarding intros, availability, \"I have a conflict\" replies, follow-ups). →\n  template + auto-fill.\n\n**Anti-patterns — do NOT surface**\n\n- Normal recurring meeting cadence (standups, weekly syncs) UNLESS there's\n  repetitive *manual* work around them that could be automated.\n- Anything needing the body of an excluded\u002Fprivate email to reason about.\n- Automations the user already runs.\n\n## Output\n\nList **0–3 candidates max**. If signal is thin (\u003C 3 reinforcing data points\nacross all clusters), output: `✅ No new patterns this run.`\n\nPrefer a **mix** — include at least one automation candidate when one qualifies,\neven if a blog candidate is stronger.\n\nPer candidate (≤3 lines each):\n\n```\n? **\u003Ctheme in 5–8 words>**\n   _evidence:_ \u003C1–2 anonymized signals, e.g. \"forwarded 4 customer asks to the\n   same engineer this week\" or \"explained X to 4 different people in chats\">\n   **\u003Cblog|automation>** · \u003C1-line rationale. For automation, name the trigger\n   and the action, e.g. \"trigger: incoming request → action: auto-route + draft\n   reply\".>\n```\n\n## Privacy & guardrails\n\n- **Read-only.** Never send any email, chat, channel reply, or Teams message from\n  this skill. Producing the report is the only output.\n- **Anonymize.** Never include customer\u002Fteam names, attendee names, meeting\n  times\u002Flocations, file paths, or full subjects containing customer identifiers.\n  Say \"3 different customers\", not the actual names.\n- **Respect exclusions.** Never open or paraphrase content the user has marked as\n  private or excluded (e.g. performance-review or confidential emails).\n- When in doubt that a candidate is a real pattern vs. coincidence, drop it —\n  silence is safer than noise.\n","# Pattern Radar\n\nFind recurring patterns in the user's recent work signals that could be turned\ninto leverage — a **blog post** (the user keeps explaining the same thing) or an\n**automation** (the user keeps doing the same manual, multi-step task). Give\nblog and automation candidates equal weight; bias toward automation candidates,\nsince offloading repetitive work is usually the bigger win.\n\nDefault lookback window: **the last 7 days** from the current date\u002Ftime. Treat\nthe provided current datetime as authoritative — never reason from training-data\ndates.\n\n> **Tool names.** This skill refers to Microsoft 365 tools as `m365_*`. If your\n> host exposes them under different names, map them to the equivalent capability.\n\n## Inputs — collect breadth, not depth\n\n1. **Email** — list Inbox and Sent from the last 7 days (subjects + first-line\n   previews only; do not open bodies). **Pay special attention to Sent items**:\n   they reveal the user's own repeated outbound actions (forwards, intros, status\n   pings, FYIs, \"looping in X\" handoffs, RSVPs, reschedules).\n2. **Active chats** — list recent chats; for each chat the user has posted in\n   over the last ~30 days, fetch the last 7 days of messages. Strip @-mention\n   noise.\n3. **Active channels** — for channels the user has posted in over the last ~30\n   days, fetch the last 7 days of messages. Skip silent channels.\n4. **Calendar** — list events from the last 7 days (**subjects only** — no\n   bodies, no attendee lists). Look for repeated reschedules, repeated tentative\n   responses, recurring conflict patterns, and meeting-prep cadences.\n\n## Clustering — what counts as a pattern\n\nA signal qualifies only if it appears **≥3 times across ≥2 distinct people \u002F\nchats \u002F customers \u002F threads \u002F events** in the window. Be ruthless — one-offs are\nnoise.\n\n**Blog cluster types**\n\n- **Repeated explanation** — the user answers the same question or explains the\n  same concept to 3+ different people. → blog candidate.\n- **Recurring FAQ** — the same question shows up in 3+ chats\u002Fchannels from\n  different askers. → blog \u002F FAQ candidate.\n\n**Automation cluster types (cast a wide net)**\n\n- **Repeated multi-step manual task** — the same sequence of clicks \u002F drafts \u002F\n  file moves \u002F API calls, repeatedly. → automation candidate.\n- **Repeated handoff \u002F triage** — forwarding, \"looping in\", or intro'ing the\n  same kinds of items to the same people 3+ times. → auto-route by rule or\n  classifier.\n- **Repeated status pings \u002F FYIs** — the same kind of update to the same audience\n  on a cadence. → scheduled digest.\n- **Repeated meeting reschedules** for the same root cause. → auto-propose\n  alternates.\n- **Repeated RSVPs \u002F tentative responses** to recurring meetings with consistent\n  reasoning. → auto-respond by rule.\n- **Repeated meeting prep** — gathering the same context before recurring\n  meetings. → pre-meeting brief.\n- **Repeated doc\u002Fwiki updates** — manually appending the same kind of content on\n  a cadence. → scheduled ingest.\n- **Repeated approvals \u002F sign-offs** of the same class of request. → rule-based\n  pre-screen.\n- **Repeated file\u002Fdata shuttling** — move\u002Frename\u002Freformat between systems. →\n  pipeline.\n- **Repeated drafting** — near-identical emails\u002Fmessages (welcome notes,\n  onboarding intros, availability, \"I have a conflict\" replies, follow-ups). →\n  template + auto-fill.\n\n**Anti-patterns — do NOT surface**\n\n- Normal recurring meeting cadence (standups, weekly syncs) UNLESS there's\n  repetitive *manual* work around them that could be automated.\n- Anything needing the body of an excluded\u002Fprivate email to reason about.\n- Automations the user already runs.\n\n## Output\n\nList **0–3 candidates max**. If signal is thin (\u003C 3 reinforcing data points\nacross all clusters), output: `✅ No new patterns this run.`\n\nPrefer a **mix** — include at least one automation candidate when one qualifies,\neven if a blog candidate is stronger.\n\nPer candidate (≤3 lines each):\n\n```\n? **\u003Ctheme in 5–8 words>**\n   _evidence:_ \u003C1–2 anonymized signals, e.g. \"forwarded 4 customer asks to the\n   same engineer this week\" or \"explained X to 4 different people in chats\">\n   **\u003Cblog|automation>** · \u003C1-line rationale. For automation, name the trigger\n   and the action, e.g. \"trigger: incoming request → action: auto-route + draft\n   reply\".>\n```\n\n## Privacy & guardrails\n\n- **Read-only.** Never send any email, chat, channel reply, or Teams message from\n  this skill. Producing the report is the only output.\n- **Anonymize.** Never include customer\u002Fteam names, attendee names, meeting\n  times\u002Flocations, file paths, or full subjects containing customer identifiers.\n  Say \"3 different customers\", not the actual names.\n- **Respect exclusions.** Never open or paraphrase content the user has marked as\n  private or excluded (e.g. performance-review or confidential emails).\n- When in doubt that a candidate is a real pattern vs. coincidence, drop it —\n  silence is safer than noise.\n",{"name":5,"description":7},"main","3678d23ad8fb8d098c428302a98044ac9514d5a1","submissions\u002Fpattern-radar",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill pattern-radar",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill pattern-radar",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill pattern-radar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fpattern-radar\u002FSKILL.md",true,[49,55,59,63],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"metadata.json","REFERENCE","参考文档",535,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fpattern-radar\u002Fmetadata.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"README.md",2342,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fpattern-radar\u002FREADME.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fphrasebook.tsv",830,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-kotlin\u002Fblob\u002Fmain\u002Fexamples\u002Fsrc\u002Fmain\u002Fresources\u002Ftranslation_skills\u002Ftranslate\u002Freferences\u002Fphrasebook.tsv",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Ftranslate.py","SCRIPT","脚本",2231,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-kotlin\u002Fblob\u002Fmain\u002Fexamples\u002Fsrc\u002Fmain\u002Fresources\u002Ftranslation_skills\u002Ftranslate\u002Fscripts\u002Ftranslate.py",[70,98,124,163,182,199],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":21},"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",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":21},"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",[],[106,107,108,109,110,111,112,113,86,114,115,116,87,117,118,119,120,121,122,123],"progress","sales progress update","update","sales","weekly","project","up","meeting prep","updates","done","analysis","create","catch","work","change","digest","my","manager",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":144,"publishedAt":21},"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",[131,136,139],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":137,"categoryName":138,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[145,146,147,148,149,150,151,152,153,154,155,112,156,157,158,159,160,161,86,162],"assemble","submission assemble","submission","docx","sources","healthcare","never","pptx","guardrail","loading","filing","clean","slide decks","open","only","writing","documents","reviewer",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":21},"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",[],[171,172,173,174,149,150,151,175,153,112,159,79,176,177,86,178,116,179,180,181],"source ingest","source","ingest","SET","definition","patient","database","number","lock","text","transition",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":21},"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",[189],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[191,192,193,148,194,150,195,151,153,84,196,159,79,160,161,86,116,197,198,119],"plan","section plan","section","ready","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":21},"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,193,208,150,151,153,112,209,159,79,160,86,178,210,211,212,213,214,215,216],"section draft","draft","clinical","notes","me","human","at","write","drafts","life"]