[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CHRZ0DMEZAZRNDWS3NJP":3,"skill-same:01M718CHRZ0DMEZAZRNDWS3NJP":64},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M718CHRZ0DMEZAZRNDWS3NJP","deal-team-summary",null,"Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says \"brief the deal team\", \"what's the state of diligence\", \"summarize findings for [audience]\", \"deal update\", or on the briefing cadence.","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",10006,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fdeal-team-summary\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"deal team summary","deal","summary","team","summarize","user","exec","at","update","exec summary","leadership","state","when","use","briefing","cadence","for","brief","2026-11-10 10:12:30",false,"---\nname: deal-team-summary\ndescription: >\n  Aggregate diligence findings into a deal team briefing at the right altitude\n  for the audience — exec summary for leadership, working summary for the team.\n  Use when user says \"brief the deal team\", \"what's the state of diligence\",\n  \"summarize findings for [audience]\", \"deal update\", or on the briefing cadence.\n---\n\n# Deal Team Summary\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\nThe deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → Deal team briefing (cadence, format, what the business reads)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md` → deal lead, timeline\n- Current findings from diligence-issue-extraction output\n\n## Audience tiers\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — what the business reads vs. what's for the file. Default tiers:\n\n| Audience | Gets | Doesn't get |\n|---|---|---|\n| **Board \u002F exec sponsor** | Top 3-5 material issues, price\u002Fstructure impact, decision items | Category detail, green findings, process |\n| **Deal lead** | All reds, all yellows, progress, decision items, next steps | Green finding detail |\n| **Working team** | Everything — full findings, status by category, gaps | Nothing withheld |\n\nAsk which tier if not obvious.\n\n## The summary\n\n### Exec tier\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> This brief aggregates privileged diligence findings and inherits the sources' privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.\n\n# [Deal code] — Diligence Brief — [date]\n\n**Status:** [On track \u002F Issues identified \u002F Material findings]\n**Coverage:** [X]% of VDR reviewed\n\n## Material findings\n\n[3-5 max. One paragraph each. What it is, why it matters to the deal, what\nwe're doing about it.]\n\n## Decisions needed\n\n- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]\n  — [who decides] — [by when]\n\n## Since last brief\n\n[What changed. New findings, findings resolved, coverage progress.]\n```\n\n### Deal lead tier\n\nSame as above plus:\n\n```markdown\n## All open issues by category\n\n### 🔴 Red\n[Finding title + one-line — link to full finding for detail]\n\n### 🟡 Yellow\n[same]\n\n## Progress\n\n| Category | Docs reviewed | Coverage | Reds | Yellows | Status |\n|---|---|---|---|---|---|\n| [name] | [N\u002FM] | [%] | [N] | [N] | [Complete \u002F In progress \u002F Blocked] |\n\n## Gaps and follow-ups\n\n- [Supplemental request items outstanding]\n- [Questions to management]\n\n## Next 72 hours\n\n[What's getting reviewed, what briefings are scheduled]\n```\n\n### Working team tier\n\nFull finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.\n\n## Deltas\n\nIf this is a recurring brief (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` cadence), lead with what changed:\n\n- New findings since last brief\n- Findings upgraded\u002Fdowngraded in severity\n- Findings resolved (consent obtained, issue clarified away)\n- Coverage movement\n\nDeal leads care more about movement than state. \"Still 12 yellows\" is less useful than \"2 new yellows, 3 resolved.\"\n\n## Handoffs\n\n- **From diligence-issue-extraction:** This skill reads the accumulated findings.\n- **To closing-checklist:** Any \"decision needed\" items that resolve into closing conditions go on the checklist.\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 make the materiality call — it reports the calls that were made at extraction time.\n- It doesn't decide what the deal team does about a finding — it surfaces the decision.\n- It doesn't distribute the brief — drafts it, human sends.\n","# Deal Team Summary\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\nThe deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → Deal team briefing (cadence, format, what the business reads)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md` → deal lead, timeline\n- Current findings from diligence-issue-extraction output\n\n## Audience tiers\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — what the business reads vs. what's for the file. Default tiers:\n\n| Audience | Gets | Doesn't get |\n|---|---|---|\n| **Board \u002F exec sponsor** | Top 3-5 material issues, price\u002Fstructure impact, decision items | Category detail, green findings, process |\n| **Deal lead** | All reds, all yellows, progress, decision items, next steps | Green finding detail |\n| **Working team** | Everything — full findings, status by category, gaps | Nothing withheld |\n\nAsk which tier if not obvious.\n\n## The summary\n\n### Exec tier\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> This brief aggregates privileged diligence findings and inherits the sources' privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.\n\n# [Deal code] — Diligence Brief — [date]\n\n**Status:** [On track \u002F Issues identified \u002F Material findings]\n**Coverage:** [X]% of VDR reviewed\n\n## Material findings\n\n[3-5 max. One paragraph each. What it is, why it matters to the deal, what\nwe're doing about it.]\n\n## Decisions needed\n\n- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]\n  — [who decides] — [by when]\n\n## Since last brief\n\n[What changed. New findings, findings resolved, coverage progress.]\n```\n\n### Deal lead tier\n\nSame as above plus:\n\n```markdown\n## All open issues by category\n\n### 🔴 Red\n[Finding title + one-line — link to full finding for detail]\n\n### 🟡 Yellow\n[same]\n\n## Progress\n\n| Category | Docs reviewed | Coverage | Reds | Yellows | Status |\n|---|---|---|---|---|---|\n| [name] | [N\u002FM] | [%] | [N] | [N] | [Complete \u002F In progress \u002F Blocked] |\n\n## Gaps and follow-ups\n\n- [Supplemental request items outstanding]\n- [Questions to management]\n\n## Next 72 hours\n\n[What's getting reviewed, what briefings are scheduled]\n```\n\n### Working team tier\n\nFull finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.\n\n## Deltas\n\nIf this is a recurring brief (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` cadence), lead with what changed:\n\n- New findings since last brief\n- Findings upgraded\u002Fdowngraded in severity\n- Findings resolved (consent obtained, issue clarified away)\n- Coverage movement\n\nDeal leads care more about movement than state. \"Still 12 yellows\" is less useful than \"2 new yellows, 3 resolved.\"\n\n## Handoffs\n\n- **From diligence-issue-extraction:** This skill reads the accumulated findings.\n- **To closing-checklist:** Any \"decision needed\" items that resolve into closing conditions go on the checklist.\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 make the materiality call — it reports the calls that were made at extraction time.\n- It doesn't decide what the deal team does about a finding — it surfaces the decision.\n- It doesn't distribute the brief — drafts it, human sends.\n",{"name":5,"description":7},"main","4a6c651889c97cc9140580363c73e0eb17379c2b","corporate-legal\u002Fskills\u002Fdeal-team-summary",1968,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 23:30:58",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill deal-team-summary",{"tool":56,"command":57},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill deal-team-summary",{"tool":59,"command":60},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill deal-team-summary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fdeal-team-summary\u002FSKILL.md",true,[],[65,93,115,134,156,168],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":37},"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",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,78,79,80,81,82,83,84,35,85,86,87,32,88,31,89,90,27,91,92],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","scheduled","check","last","report","regulatory",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":37},"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",[],[100,101,83,35,102,103,104,32,105,31,106,107,108,109,110,111,112,113,92,114],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","gap","mark","first","direct",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":37},"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",[],[83,100,122,123,31,124,125,77,126,78,127,128,129,130,32,131,111,132,133,92],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the","name",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":37},"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",[],[141,142,123,143,144,145,86,32,31,124,146,147,148,149,150,151,152,153,154,155],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":157,"name":107,"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":161,"publishedAt":37},"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",[],[107,110,111,162,150,163,164,165,166,32,167,31,24],"risk","tracker","remediation","status","open","accept",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":179,"publishedAt":37},"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[111,180,181,182,83,100,183,166,184,185,186,187,107,188,189,190,191,163,164,192],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","work","slack","via","surfaces"]