$ loading_
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.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "deal-team-summary" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/corporate-legal/skills/deal-team-summary/SKILL.md 2. 保存为 ~/.claude/skills/deal-team-summary/SKILL.md 3. 装好后重载技能，告诉我可以用了
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 /corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
The 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.
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md → Deal team briefing (cadence, format, what the business reads)~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/deal-context.md → deal lead, timelinePer ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md — what the business reads vs. what's for the file. Default tiers:
| Audience | Gets | Doesn't get |
|---|---|---|
| Board / exec sponsor | Top 3-5 material issues, price/structure impact, decision items | Category detail, green findings, process |
| Deal lead | All reds, all yellows, progress, decision items, next steps | Green finding detail |
| Working team | Everything — full findings, status by category, gaps | Nothing withheld |
Ask which tier if not obvious.
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
> 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.
# [Deal code] — Diligence Brief — [date]
**Status:** [On track / Issues identified / Material findings]
**Coverage:** [X]% of VDR reviewed
## Material findings
[3-5 max. One paragraph each. What it is, why it matters to the deal, what
we're doing about it.]
## Decisions needed
- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]
— [who decides] — [by when]
## Since last brief
[What changed. New findings, findings resolved, coverage progress.]
Same as above plus:
## All open issues by category
### 🔴 Red
[Finding title + one-line — link to full finding for detail]
### 🟡 Yellow
[same]
## Progress
| Category | Docs reviewed | Coverage | Reds | Yellows | Status |
|---|---|---|---|---|---|
| [name] | [N/M] | [%] | [N] | [N] | [Complete / In progress / Blocked] |
## Gaps and follow-ups
- [Supplemental request items outstanding]
- [Questions to management]
## Next 72 hours
[What's getting reviewed, what briefings are scheduled]
Full finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.
If this is a recurring brief (per ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md cadence), lead with what changed:
Deal leads care more about movement than state. "Still 12 yellows" is less useful than "2 new yellows, 3 resolved."
…
Ask questions against an open investigation log — what witnesses said, where accounts conflict, what gaps exist, what the strongest evidence is on each issue. Use when the attorney needs to query the investigation record without re-reading every entry.
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your governance positions; flag training-on-data, liability, model changes, and AI policy consistency. Use when user says "review this AI agreement", "check OpenAI terms", "what did we agree to with [vendor]", "vendor sent an AI addendum", "is this AI contract okay", or attaches vendor AI terms.
Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, and draft the ask. Use when the user says "who needs to approve this", "escalate this", "does this need GC sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent counsel review. This skill never concludes a product is clear to launch.