[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718C084REZXW4HWZYHT7WJZ":3,"skill-same:01M718C084REZXW4HWZYHT7WJZ":66},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M718C084REZXW4HWZYHT7WJZ","ai-tool-handoff",null,"Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. Use when user says \"send to Luminance\", \"bulk review\", \"AI extraction\", or when diligence-issue-extraction hits a high-volume category.","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",9977,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fai-tool-handoff\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ai tool handoff","handoff","tool","user","legal","it","issue","corporate","plugins","config","high","output","review","when","use","send","for","trust","volume","bulk","2026-11-10 10:12:30",false,"---\nname: ai-tool-handoff\ndescription: >\n  Detects when Luminance, Kira, or a similar bulk-review tool is in use,\n  hands off the high-volume clause extraction to it, and QAs its output\n  per the trust level in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. Use when user says \"send to Luminance\",\n  \"bulk review\", \"AI extraction\", or when diligence-issue-extraction hits\n  a high-volume category.\n---\n\n# AI Tool Handoff\n\n## Matter context\n\n**Matter context.** Check `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗` (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: \"Which matter is this for? Run `\u002Fcorporate-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nLuminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.\n\nThis skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.\n\n**Before you hand off:** try `tabular-review` first (`\u002Fcorporate-legal:tabular-review`). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance\u002FKira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.\n\n## Load context\n\n`~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → AI-assisted review:\n- Tool in use (Luminance \u002F Kira \u002F none)\n- What it's used for (which clause types)\n- Trust level (use as-is \u002F spot-check \u002F full re-review)\n- Handoff process (who loads, who QAs)\n\nIf `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.\n\n## When to hand off\n\nHand off when all of:\n- Category has >50 documents (below that, faster to just read them)\n- Extraction target is a clause type the tool is good at (CoC, assignment, exclusivity, MFN, termination, auto-renewal)\n- Documents are reasonably uniform (all customer contracts on similar paper — not a mix of contracts, letters, and board minutes)\n\nDon't hand off:\n- Bespoke or heavily negotiated documents\n- Side letters and amendments (context-dependent, tools miss the interaction with the main agreement)\n- Anything where the question is \"what does this mean for the deal\" not \"does this clause exist\"\n\n## The handoff\n\n### Step 1: Prepare the batch\n\n- Identify documents for the batch (from VDR inventory)\n- Specify extraction targets per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (which clause types)\n- Note the materiality threshold so tool output can be filtered\n\n### Step 2: Load (or instruct the loader)\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — who loads. If it's you, generate the load instructions. If it's someone else, generate the request:\n\n```markdown\n## [Tool] Load Request — [Deal code] — [Category]\n\n**Documents:** [N] docs from VDR folder [path]\n**Load to:** [Tool workspace\u002Fmatter]\n**Extraction targets:**\n- Change of control \u002F assignment\n- Exclusivity\n- [etc. per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\n**Filter output:** Flag only where extraction target is present — no need for \"no CoC clause found\" for every doc.\n\n**Return by:** [date]\n```\n\n### Step 3: QA the output\n\nWhen the tool returns results, apply the trust level:\n\n**\"Use as-is\":** Ingest directly into diligence findings. (Only if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says this — it's rare.)\n\n**\"Spot-check X%\":** Randomly sample X% of flagged documents. For each, read the actual clause and compare to the tool's extraction. If error rate is low, accept the batch. If errors found, widen the sample.\n\n**\"Full human review of flagged\":** Tool narrows the universe (500 docs → 80 with CoC clauses). Human reads all 80. Tool saved the time of reading the 420 clean ones.\n\n### Step 4: Judgment layer\n\nThe tool found the clauses. Now apply judgment:\n\nFor each flagged CoC provision: is it actually triggered by this deal?\n- Stock sale vs. asset sale vs. merger — different triggers\n- \"Change of control\" defined how in the contract — majority ownership? board control? something else?\n- Is there a carve-out for this type of transaction?\n\nThis is the part the tool can't do. Output goes to diligence findings in house format.\n\n## Output\n\n> The QA summary below is derived from VDR documents that are privileged, confidential, or both. It inherits the sources' privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Store with the matter's privileged files.\n\n```markdown\n## AI Tool Handoff Summary — [Category]\n\n**Tool:** [Luminance \u002F Kira]\n**Documents processed:** [N]\n**Extraction targets:** [clause types]\n\n### QA\n\n**Trust level:** [per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n**Sample size:** [N] docs spot-checked\n**Error rate:** [X]% — [Accepted \u002F Widened sample \u002F Full re-review triggered]\n\n### Results\n\n| Clause type | Docs flagged | After judgment layer | Material |\n|---|---|---|---|\n| Change of control | [N] | [N actually triggered by deal structure] | [N above threshold] |\n| Assignment | [N] | [N] | [N] |\n\n**→ [N] findings added to diligence issues**\n**→ [N] consents added to closing checklist**\n```\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- It doesn't run Luminance or Kira — it manages the handoff and QA. A human (or the tool's own interface) runs the extraction.\n- It doesn't replace the tool's output with its own judgment entirely — if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says spot-check 10%, check 10%, not 100%.\n- It doesn't decide the trust level — that's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`, set at cold-start based on the team's experience with the tool.\n","# AI Tool Handoff\n\n## Matter context\n\n**Matter context.** Check `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗` (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: \"Which matter is this for? Run `\u002Fcorporate-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nLuminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.\n\nThis skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.\n\n**Before you hand off:** try `tabular-review` first (`\u002Fcorporate-legal:tabular-review`). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance\u002FKira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.\n\n## Load context\n\n`~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → AI-assisted review:\n- Tool in use (Luminance \u002F Kira \u002F none)\n- What it's used for (which clause types)\n- Trust level (use as-is \u002F spot-check \u002F full re-review)\n- Handoff process (who loads, who QAs)\n\nIf `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.\n\n## When to hand off\n\nHand off when all of:\n- Category has >50 documents (below that, faster to just read them)\n- Extraction target is a clause type the tool is good at (CoC, assignment, exclusivity, MFN, termination, auto-renewal)\n- Documents are reasonably uniform (all customer contracts on similar paper — not a mix of contracts, letters, and board minutes)\n\nDon't hand off:\n- Bespoke or heavily negotiated documents\n- Side letters and amendments (context-dependent, tools miss the interaction with the main agreement)\n- Anything where the question is \"what does this mean for the deal\" not \"does this clause exist\"\n\n## The handoff\n\n### Step 1: Prepare the batch\n\n- Identify documents for the batch (from VDR inventory)\n- Specify extraction targets per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (which clause types)\n- Note the materiality threshold so tool output can be filtered\n\n### Step 2: Load (or instruct the loader)\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — who loads. If it's you, generate the load instructions. If it's someone else, generate the request:\n\n```markdown\n## [Tool] Load Request — [Deal code] — [Category]\n\n**Documents:** [N] docs from VDR folder [path]\n**Load to:** [Tool workspace\u002Fmatter]\n**Extraction targets:**\n- Change of control \u002F assignment\n- Exclusivity\n- [etc. per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\n**Filter output:** Flag only where extraction target is present — no need for \"no CoC clause found\" for every doc.\n\n**Return by:** [date]\n```\n\n### Step 3: QA the output\n\nWhen the tool returns results, apply the trust level:\n\n**\"Use as-is\":** Ingest directly into diligence findings. (Only if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says this — it's rare.)\n\n**\"Spot-check X%\":** Randomly sample X% of flagged documents. For each, read the actual clause and compare to the tool's extraction. If error rate is low, accept the batch. If errors found, widen the sample.\n\n**\"Full human review of flagged\":** Tool narrows the universe (500 docs → 80 with CoC clauses). Human reads all 80. Tool saved the time of reading the 420 clean ones.\n\n### Step 4: Judgment layer\n\nThe tool found the clauses. Now apply judgment:\n\nFor each flagged CoC provision: is it actually triggered by this deal?\n- Stock sale vs. asset sale vs. merger — different triggers\n- \"Change of control\" defined how in the contract — majority ownership? board control? something else?\n- Is there a carve-out for this type of transaction?\n\nThis is the part the tool can't do. Output goes to diligence findings in house format.\n\n## Output\n\n> The QA summary below is derived from VDR documents that are privileged, confidential, or both. It inherits the sources' privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Store with the matter's privileged files.\n\n```markdown\n## AI Tool Handoff Summary — [Category]\n\n**Tool:** [Luminance \u002F Kira]\n**Documents processed:** [N]\n**Extraction targets:** [clause types]\n\n### QA\n\n**Trust level:** [per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n**Sample size:** [N] docs spot-checked\n**Error rate:** [X]% — [Accepted \u002F Widened sample \u002F Full re-review triggered]\n\n### Results\n\n| Clause type | Docs flagged | After judgment layer | Material |\n|---|---|---|---|\n| Change of control | [N] | [N actually triggered by deal structure] | [N above threshold] |\n| Assignment | [N] | [N] | [N] |\n\n**→ [N] findings added to diligence issues**\n**→ [N] consents added to closing checklist**\n```\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- It doesn't run Luminance or Kira — it manages the handoff and QA. A human (or the tool's own interface) runs the extraction.\n- It doesn't replace the tool's output with its own judgment entirely — if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says spot-check 10%, check 10%, not 100%.\n- It doesn't decide the trust level — that's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`, set at cold-start based on the team's experience with the tool.\n",{"name":5,"description":7},"main","4a6c651889c97cc9140580363c73e0eb17379c2b","corporate-legal\u002Fskills\u002Fai-tool-handoff",1959,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-08 22:42:37",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill ai-tool-handoff",{"tool":58,"command":59},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill ai-tool-handoff",{"tool":61,"command":62},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill ai-tool-handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fai-tool-handoff\u002FSKILL.md",true,[],[67,96,117,136,157,169],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":39},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,80,81,82,83,84,85,86,35,87,88,89,33,90,32,91,92,93,94,95],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","scheduled","check","last","update","report","regulatory",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":39},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[103,104,85,35,105,106,107,33,108,32,109,110,31,111,112,113,114,115,95,116],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","draft","id","gap","mark","first","direct",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":39},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[85,103,124,125,32,126,127,79,128,80,129,130,131,132,33,133,113,134,135,95],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the","name",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":39},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[143,144,125,145,146,147,88,33,32,126,148,149,150,151,152,153,154,155,24,156],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","context",{"skillNo":158,"name":110,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[110,112,113,163,152,164,165,166,167,33,168,32,22],"risk","tracker","remediation","status","open","accept",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":180,"publishedAt":39},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[113,181,182,183,85,103,34,167,184,185,186,187,110,188,189,190,191,164,165,192],"gap surfacer","shared","tracks","confirmation","aging","false","comments","with","work","slack","via","surfaces"]