[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X39N10195HQF56B5PBYKT8":3,"skill-same:01M6X39N10195HQF56B5PBYKT8":106},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6X39N10195HQF56B5PBYKT8","reg-change-triage",null,"Triages a new or changed regulatory instrument into a decision-ready brief covering what changed, date ladder, affected parties, obligations cited to primary source, candidate policies, gaps, and actions. Applicability is proposed with reasoning, never decided. Use when the user says \"what does this new rule mean for us\", \"triage this SR letter\", \"summarize the impact of this regulatory change\", \"when do we have to comply\", or \"which policies does this hit\". Do NOT use for enforcement actions, settlements, or consent orders (use enforcement-action-review), one policy against one rule (use policy-gap-analysis), request trackers (use exam-request-response), a vendor SOC 2 (use vendor-risk-review), workbook formatting (use built-in xlsx), or sending email (use built-in outlook-email).","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",103,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"reg change triage","triage","change","reg","ready","when","candidate","which","affected","comply","exam","impact","xlsx","never","decision","analysis","soc","brief","actions","review","2026-11-10 10:12:30",false,"---\nname: reg-change-triage\ndescription: Triages a new or changed regulatory instrument into a decision-ready brief covering what changed, date ladder, affected parties, obligations cited to primary source, candidate policies, gaps, and actions. Applicability is proposed with reasoning, never decided. Use when the user says \"what does this new rule mean for us\", \"triage this SR letter\", \"summarize the impact of this regulatory change\", \"when do we have to comply\", or \"which policies does this hit\". Do NOT use for enforcement actions, settlements, or consent orders (use enforcement-action-review), one policy against one rule (use policy-gap-analysis), request trackers (use exam-request-response), a vendor SOC 2 (use vendor-risk-review), workbook formatting (use built-in xlsx), or sending email (use built-in outlook-email).\nmetadata: {icon: DocumentSearch}\n---\n\n## Scope\n\n**Do:** identify regulatory instruments, build date ladders, extract changed obligations, propose applicability, locate candidate affected policies, build action trackers\n**Do not:** state requirements from memory, treat proposed rules as obligations, decide applicability, materiality, or compliance, claim candidate policies provide coverage, register, file, or send anything\n\n## When NOT to Use\n\n- **Clause-by-clause coverage of one policy against one rule** — use `policy-gap-analysis` instead.\n- **A published enforcement action or consent order** — use `enforcement-action-review` instead.\n- **A vendor SOC 2 or third-party controls review** — use `vendor-risk-review` instead.\n- **Formatting, charting, or restyling an existing workbook** — use `xlsx` instead.\n\n# Regulatory Change Triage Brief\n\nTurn one regulatory instrument into a brief a compliance owner can act on: what changed, by\nwhen, who it hits, and what the firm must look at.\n\n**You propose. A qualified human decides.** Applicability, materiality, and required action are\ndeterminations — see `house-rules.md` § 2.\n\n---\n\n## Read first\n\nRead these in full before step 1. They are binding; this body only summarises them.\n\n- `references\u002Fworkflow.md` — the full text of every step below, with the guardrails, source\n  resolution, and footer detail.\n- `references\u002Fhouse-rules.md` — destination gate, determination gate, authority tiers, markers,\n  footers, and § 12 data minimisation (every artifact, search, and chat reply, declines included).\n- `references\u002Freg-source-access.md` — routing, the codification gap, precision filtering, the\n  date ladder.\n- `references\u002Fdocument-extraction.md` — if the instrument was uploaded.\n- `references\u002Ftriage-outline.md` — default brief and tracker structure: the output format.\n- `references\u002Fself-check.md` — the final self-check (step 10).\n\n---\n\n## Workflow\n\n### 1. Identify the instrument precisely\n\nDetail: `workflow.md` § 1. Agency · title · document number · type · authority tier, before\nanything else.\n\n- A proposed rule is not law. Its `PROPOSED - not in force (G1)` line goes right after the whole\n  header block (title, Destination, Prepared, Status), never between them.\n- **Declines are plain:** `\u003Ccategory> withheld under data minimisation.`, with no statement of\n  what SAR confidentiality or any law requires.\n- **Never say what does not exist** (\"has not been published\", \"is not yet final\"). Say what the\n  instrument you hold is; only after a Federal Register search this session write\n  `NOT FOUND - Federal Register API has no record of a final rule for \u003CRIN> as of \u003Cdate> (Gn)`.\n- Ambiguous instrument: list the candidates and ask; never pick one silently.\n\n### 2. Retrieve it\n\nDetail: `workflow.md` § 2. Connector → direct route → browser → ask for an upload →\n`NOT RETRIEVED`, per `reg-source-access.md` § 1. Never answer from memory. Filter searches by\nagency, type, and docket.\n\n### 3. Build the date ladder\n\nDetail: `workflow.md` § 3. Published · Effective · Compliance date · Mandatory compliance date,\nplus the comment deadline: every row always shown, never collapsed. A row with no stated date\nleads with `NOT FOUND - instrument states no \u003Cwhich> date (Gn)`, then any quoted relative or\nproposed wording. Never \"n\u002Fa\"; never infer a compliance date from the effective date.\n\n### 4. Extract what changed\n\nDetail: `workflow.md` § 4. CFR part and section, prior text, new text, both quoted verbatim. Run\nthe codification check before calling codified text current; no prior text →\n`GAP — prior text not established`. While the definitions section is not retrieved, every entity\nterm in `Prior text` and `New text` quotes, preamble quotes included, reads `[covered entity]`.\n\n### 5. Derive obligations\n\nDetail: `workflow.md` § 5. One obligation per row: what must be done · who it binds · trigger or\nthreshold · the date it bites · citation · tier.\n\n- A proposed rule's obligations carry `PROPOSED - not in force`, one G-bullet naming every row.\n- Guidance is a supervisory expectation, never \"required by\". Thresholds are quoted exactly.\n- Quotes and paraphrases use `[covered entity]` while the definitions section is not retrieved.\n- `Bites on` is the DATES compliance date covering the row, with its DATES citation, or\n  `NOT FOUND - instrument states no compliance date for \u003Crow> (Gn)`. Never the effective date.\n- Capture every exemption and exclusion.\n\n### 6. Propose applicability — never decide it\n\nDetail: `workflow.md` § 6. For each obligation, propose the business lines, products, entities,\nor jurisdictions affected, with the reasoning and the text it rests on, marked\n`NOT DETERMINED — compliance owner decides`. Retrieve the coverage-defining provision first; if\nit was not retrieved, the reasoning reads exactly `none - defining provision not retrieved`. No\nhedge words. Name any missing fact (for example total assets) with its marker. State each scope\nambiguity as an open question with its decider. Never \"will require you to\".\n\n### 7. Locate candidate affected policies\n\nDetail: `workflow.md` § 7. Search M365 for policies touching each obligation: name · version ·\napproval status · approval date · location · why candidate (the topical link only). Nothing found\n→ `NOT FOUND - \u003Crepository> has no record of a policy for \u003Cobligation> (Gn)`. Each rejected document\ngets its own `GAP - scope mismatch, not a candidate` bullet. A candidate is never coverage; hand\nclause-level work to `policy-gap-analysis`.\n\n### 8. Build the action list\n\nDetail: `workflow.md` § 8. Proposed actions only: the obligation served · a suggested owner with\nits basis · the driving date · what closes it. No basis → only\n`NOT FOUND - owner not identified (Gn)`.\n\n### 9. Emit the tracker and draft handoff\n\nDetail: `workflow.md` § 9. Build the workbook with `xlsx` per `triage-outline.md`. A GRC\nconnector is read for pre-fill only; the deliverable is a draft export, and the register update\nis the human's action. No connector → `NEEDS FEED — GRC change register`.\n\n### 10. Final self-check, then count\n\n1. Save the artifact text, the chat reply (`reply.md`), and the search log (`searches.md`: one\n   `REQ | \u003Csource> | ok \u002F failed \u002F not attempted` line per request and one\n   `HIT | \u003Cquery> | \u003Cdocument> | used \u002F rejected (Gn) \u002F duplicate (Gn) \u002F set aside` line per document returned).\n2. Run `python scripts\u002Flint_deliverable.py \u003Cartifact> --reply reply.md --searches searches.md`.\n   Fix every `ERROR`, resolve every `CHECK`, and re-run until it prints `ERROR: 0`\n   (`house-rules.md` § 13).\n3. Work through every item in `references\u002Fself-check.md`, including the ones the script cannot\n   judge.\n4. Build the footer counts from the G-list and D-list last, then recount.\n\n---\n\n## Guardrails\n\nFull list: `workflow.md`, Guardrails.\n\n- Never state a requirement from memory or cite anything reached only through a snippet.\n- Never present a proposed rule as an obligation or guidance as a legal requirement.\n- Never collapse the four dates; never report codified text as current without the check.\n- Never decide applicability, materiality, or compliance; no hedge words on a determination.\n- Never fabricate a document number, docket, section, date, owner, or figure.\n- Never claim a save succeeded when it failed. Nothing is registered, filed, sent, or committed\n  in a source system.\n\n## Output footer\n\nPer `house-rules.md` § 9 and `workflow.md`, Output footer: destination · instrument and\nidentifiers · route · tier · coverage · codification check and result · policy repository searched\nand found · connectors · open items by marker type · determinations outstanding · draft export,\nno source-system update · files and save result · template used.\n\n### Example\n\n```\nInput: FinCEN proposed rule RIN 1506-ABCD; search AML policy owners.\nOutput row: Obligation 1 - PROPOSED - not in force (G1); comment deadline 2026-11-12.\nCandidate policy: AML Program Standard v4; Determination: NOT DETERMINED - compliance owner decides (D1).\nOwner: NOT FOUND - owner not identified (G2).\nNo match: NOT FOUND - Compliance\u002FPolicies has no record of a policy for O2 (G3).\nD-bullet: D1 - NOT DETERMINED - does O1 reach the firm - compliance owner decides\nHandoff: Draft register export prepared; no source-system update performed.\n```\n\n## Reference files\n\n- `references\u002Fworkflow.md` — full step text, guardrails, source resolution, footer detail.\n- `references\u002Fself-check.md` — the final self-check.\n- `references\u002Fhouse-rules.md` — gates, tiers, markers, footers, data minimisation, the lint step.\n- `references\u002Freg-source-access.md` — routing, codification gap, precision filtering, date ladder.\n- `references\u002Fdocument-extraction.md` — reading an uploaded instrument or policy.\n- `references\u002Ftriage-outline.md` — default brief structure and tracker columns.\n","## Scope\n\n**Do:** identify regulatory instruments, build date ladders, extract changed obligations, propose applicability, locate candidate affected policies, build action trackers\n**Do not:** state requirements from memory, treat proposed rules as obligations, decide applicability, materiality, or compliance, claim candidate policies provide coverage, register, file, or send anything\n\n## When NOT to Use\n\n- **Clause-by-clause coverage of one policy against one rule** — use `policy-gap-analysis` instead.\n- **A published enforcement action or consent order** — use `enforcement-action-review` instead.\n- **A vendor SOC 2 or third-party controls review** — use `vendor-risk-review` instead.\n- **Formatting, charting, or restyling an existing workbook** — use `xlsx` instead.\n\n# Regulatory Change Triage Brief\n\nTurn one regulatory instrument into a brief a compliance owner can act on: what changed, by\nwhen, who it hits, and what the firm must look at.\n\n**You propose. A qualified human decides.** Applicability, materiality, and required action are\ndeterminations — see `house-rules.md` § 2.\n\n---\n\n## Read first\n\nRead these in full before step 1. They are binding; this body only summarises them.\n\n- `references\u002Fworkflow.md` — the full text of every step below, with the guardrails, source\n  resolution, and footer detail.\n- `references\u002Fhouse-rules.md` — destination gate, determination gate, authority tiers, markers,\n  footers, and § 12 data minimisation (every artifact, search, and chat reply, declines included).\n- `references\u002Freg-source-access.md` — routing, the codification gap, precision filtering, the\n  date ladder.\n- `references\u002Fdocument-extraction.md` — if the instrument was uploaded.\n- `references\u002Ftriage-outline.md` — default brief and tracker structure: the output format.\n- `references\u002Fself-check.md` — the final self-check (step 10).\n\n---\n\n## Workflow\n\n### 1. Identify the instrument precisely\n\nDetail: `workflow.md` § 1. Agency · title · document number · type · authority tier, before\nanything else.\n\n- A proposed rule is not law. Its `PROPOSED - not in force (G1)` line goes right after the whole\n  header block (title, Destination, Prepared, Status), never between them.\n- **Declines are plain:** `\u003Ccategory> withheld under data minimisation.`, with no statement of\n  what SAR confidentiality or any law requires.\n- **Never say what does not exist** (\"has not been published\", \"is not yet final\"). Say what the\n  instrument you hold is; only after a Federal Register search this session write\n  `NOT FOUND - Federal Register API has no record of a final rule for \u003CRIN> as of \u003Cdate> (Gn)`.\n- Ambiguous instrument: list the candidates and ask; never pick one silently.\n\n### 2. Retrieve it\n\nDetail: `workflow.md` § 2. Connector → direct route → browser → ask for an upload →\n`NOT RETRIEVED`, per `reg-source-access.md` § 1. Never answer from memory. Filter searches by\nagency, type, and docket.\n\n### 3. Build the date ladder\n\nDetail: `workflow.md` § 3. Published · Effective · Compliance date · Mandatory compliance date,\nplus the comment deadline: every row always shown, never collapsed. A row with no stated date\nleads with `NOT FOUND - instrument states no \u003Cwhich> date (Gn)`, then any quoted relative or\nproposed wording. Never \"n\u002Fa\"; never infer a compliance date from the effective date.\n\n### 4. Extract what changed\n\nDetail: `workflow.md` § 4. CFR part and section, prior text, new text, both quoted verbatim. Run\nthe codification check before calling codified text current; no prior text →\n`GAP — prior text not established`. While the definitions section is not retrieved, every entity\nterm in `Prior text` and `New text` quotes, preamble quotes included, reads `[covered entity]`.\n\n### 5. Derive obligations\n\nDetail: `workflow.md` § 5. One obligation per row: what must be done · who it binds · trigger or\nthreshold · the date it bites · citation · tier.\n\n- A proposed rule's obligations carry `PROPOSED - not in force`, one G-bullet naming every row.\n- Guidance is a supervisory expectation, never \"required by\". Thresholds are quoted exactly.\n- Quotes and paraphrases use `[covered entity]` while the definitions section is not retrieved.\n- `Bites on` is the DATES compliance date covering the row, with its DATES citation, or\n  `NOT FOUND - instrument states no compliance date for \u003Crow> (Gn)`. Never the effective date.\n- Capture every exemption and exclusion.\n\n### 6. Propose applicability — never decide it\n\nDetail: `workflow.md` § 6. For each obligation, propose the business lines, products, entities,\nor jurisdictions affected, with the reasoning and the text it rests on, marked\n`NOT DETERMINED — compliance owner decides`. Retrieve the coverage-defining provision first; if\nit was not retrieved, the reasoning reads exactly `none - defining provision not retrieved`. No\nhedge words. Name any missing fact (for example total assets) with its marker. State each scope\nambiguity as an open question with its decider. Never \"will require you to\".\n\n### 7. Locate candidate affected policies\n\nDetail: `workflow.md` § 7. Search M365 for policies touching each obligation: name · version ·\napproval status · approval date · location · why candidate (the topical link only). Nothing found\n→ `NOT FOUND - \u003Crepository> has no record of a policy for \u003Cobligation> (Gn)`. Each rejected document\ngets its own `GAP - scope mismatch, not a candidate` bullet. A candidate is never coverage; hand\nclause-level work to `policy-gap-analysis`.\n\n### 8. Build the action list\n\nDetail: `workflow.md` § 8. Proposed actions only: the obligation served · a suggested owner with\nits basis · the driving date · what closes it. No basis → only\n`NOT FOUND - owner not identified (Gn)`.\n\n### 9. Emit the tracker and draft handoff\n\nDetail: `workflow.md` § 9. Build the workbook with `xlsx` per `triage-outline.md`. A GRC\nconnector is read for pre-fill only; the deliverable is a draft export, and the register update\nis the human's action. No connector → `NEEDS FEED — GRC change register`.\n\n### 10. Final self-check, then count\n\n1. Save the artifact text, the chat reply (`reply.md`), and the search log (`searches.md`: one\n   `REQ | \u003Csource> | ok \u002F failed \u002F not attempted` line per request and one\n   `HIT | \u003Cquery> | \u003Cdocument> | used \u002F rejected (Gn) \u002F duplicate (Gn) \u002F set aside` line per document returned).\n2. Run `python scripts\u002Flint_deliverable.py \u003Cartifact> --reply reply.md --searches searches.md`.\n   Fix every `ERROR`, resolve every `CHECK`, and re-run until it prints `ERROR: 0`\n   (`house-rules.md` § 13).\n3. Work through every item in `references\u002Fself-check.md`, including the ones the script cannot\n   judge.\n4. Build the footer counts from the G-list and D-list last, then recount.\n\n---\n\n## Guardrails\n\nFull list: `workflow.md`, Guardrails.\n\n- Never state a requirement from memory or cite anything reached only through a snippet.\n- Never present a proposed rule as an obligation or guidance as a legal requirement.\n- Never collapse the four dates; never report codified text as current without the check.\n- Never decide applicability, materiality, or compliance; no hedge words on a determination.\n- Never fabricate a document number, docket, section, date, owner, or figure.\n- Never claim a save succeeded when it failed. Nothing is registered, filed, sent, or committed\n  in a source system.\n\n## Output footer\n\nPer `house-rules.md` § 9 and `workflow.md`, Output footer: destination · instrument and\nidentifiers · route · tier · coverage · codification check and result · policy repository searched\nand found · connectors · open items by marker type · determinations outstanding · draft export,\nno source-system update · files and save result · template used.\n\n### Example\n\n```\nInput: FinCEN proposed rule RIN 1506-ABCD; search AML policy owners.\nOutput row: Obligation 1 - PROPOSED - not in force (G1); comment deadline 2026-11-12.\nCandidate policy: AML Program Standard v4; Determination: NOT DETERMINED - compliance owner decides (D1).\nOwner: NOT FOUND - owner not identified (G2).\nNo match: NOT FOUND - Compliance\u002FPolicies has no record of a policy for O2 (G3).\nD-bullet: D1 - NOT DETERMINED - does O1 reach the firm - compliance owner decides\nHandoff: Draft register export prepared; no source-system update performed.\n```\n\n## Reference files\n\n- `references\u002Fworkflow.md` — full step text, guardrails, source resolution, footer detail.\n- `references\u002Fself-check.md` — the final self-check.\n- `references\u002Fhouse-rules.md` — gates, tiers, markers, footers, data minimisation, the lint step.\n- `references\u002Freg-source-access.md` — routing, codification gap, precision filtering, date ladder.\n- `references\u002Fdocument-extraction.md` — reading an uploaded instrument or policy.\n- `references\u002Ftriage-outline.md` — default brief structure and tracker columns.\n",{"name":5,"metadata":49,"description":7},{"icon":50},"DocumentSearch","main","c739e95c35d12a999691ab076c3d4c3095bf8192","submissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage",118,"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-07 09:09:13",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill reg-change-triage",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill reg-change-triage",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill reg-change-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002FSKILL.md",true,[74,80,84,88,92,96,100],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdocument-extraction.md","REFERENCE","参考文档",8879,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Fdocument-extraction.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fhouse-rules.md",60807,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Fhouse-rules.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Freg-source-access.md",11537,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Freg-source-access.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fself-check.md",8541,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Fself-check.md",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Ftriage-outline.md",17186,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Ftriage-outline.md",{"path":97,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fworkflow.md",19251,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Freferences\u002Fworkflow.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Flint_deliverable.py","SCRIPT","脚本",76587,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Ffsi-risk-and-compliance\u002Freg-change-triage\u002Fscripts\u002Flint_deliverable.py",[107,132,155,190,208,222],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":44},"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\u002FSKILL.md",[],[38,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,29,131],"map","decision map","stakeholder and decision map","performance","customer","team","how","decide","do","next","infer","missing","records","assess","reviews","for","single","sequences",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":44},"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\u002FSKILL.md",[],[139,140,141,142,26,143,144,39,119,145,146,147,148,149,150,151,152,153,154,29],"update","sales","progress","sales progress update","create","meeting prep","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":172,"publishedAt":44},"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\u002FSKILL.md",[161,164,167],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":168,"categoryName":169,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[173,174,175,176,177,178,179,180,181,182,37,183,146,184,185,186,187,188,189,29],"assemble","submission","submission assemble","docx","pptx","writing","documents","healthcare","open","reviewer","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":44},"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\u002FSKILL.md",[],[197,198,199,200,201,39,180,202,37,183,146,114,203,185,187,204,205,206,207,29],"source ingest","ingest","source","database","SET","text","patient","number","lock","definition","transition",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":44},"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\u002FSKILL.md",[214],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},[216,217,218,176,178,117,179,39,180,145,37,183,28,219,220,114,185,221,31,29],"plan","section","section plan","reports","structure","word documents",{"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":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":44},"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\u002FSKILL.md",[],[229,217,230,178,231,180,232,37,183,146,233,114,234,235,236,185,237,204,238,29],"draft","section draft","notes","write","me","human","life","clinical","drafts","at"]