$ loading_
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.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "escalation-flagger" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/commercial-legal/skills/escalation-flagger/SKILL.md 2. 保存为 ~/.claude/skills/escalation-flagger/SKILL.md 3. 装好后重载技能，告诉我可以用了
Names the approver for a contract issue per the ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md escalation matrix and drafts the message so you're not writing "hey got a sec" at 5pm.
Load ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md → Escalation section. If missing, say so — the practice profile needs editing.
Characterize the issue: dollar threshold / term deviation / automatic trigger / business decision.
Match to matrix, name the approver. Be specific — a person or role, not "legal leadership."
Draft the ask per the template below: what the contract says, what playbook says, options with recommendation, decision-by date.
Do not send. Draft it, show it, let the lawyer send.
/commercial-legal:escalation-flagger
The Acme MSA has uncapped liability — who approves and what do I say?
/commercial-legal:escalation-flagger
Reference: acme-review-memo.md
Issue: §8.2 indemnity carveouts
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 /commercial-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/commercial-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Every contracts team has an escalation matrix, written or not. This skill reads the written one (in ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md), matches a contract issue against it, names the approver, and drafts the ask so the lawyer isn't writing "hey do you have a sec" messages at 5pm.
Which side? Before matching to the matrix, determine which side the company is on for the contract whose issue is being escalated. Usually obvious: if the counterparty is a vendor/supplier providing goods or services, you're purchasing-side. If the counterparty is a customer buying your product/service, you're sales-side. If it's not obvious, ask. Read the matching playbook section (### Sales-side playbook or ### Purchasing-side playbook) to evaluate whether the term is inside fallbacks or triggers an automatic escalation — a term that's fine on one side can be a hard-no on the other. Note which side in the drafted ask so the approver knows which playbook was applied.
Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md → ## Escalation. If it's missing or vague, say so — the cold-start interview should have captured this, and if it didn't, the practice profile needs editing.
Expected structure:
| Can approve | Threshold | Escalates to | Via |
|---|---|---|---|
| Paralegal | Standard terms, <$50K | Counsel | Slack |
| Counsel | Non-standard but within fallbacks, <$500K | GC | Slack or email |
| GC | Everything else | CFO/Board | Meeting |
Plus automatic escalation triggers — things that escalate regardless of dollar value. Typically: unlimited liability, IP assignment, anything on the "never accept" lists.
What's being escalated?
…
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
Review an offer letter and any restrictive covenants — jurisdiction check included. Substantive rules (covenant enforceability, pay-transparency, salary-history limits, exemption criteria) are researched per hire, not stored. Use when the user says "review this offer", "can we use a non-compete here", "check this offer letter", "hiring in [state]", or attaches an offer.
Draft an audience-specific summary from the privileged investigation memo — HR, leadership, or outside counsel versions. Use when an investigation memo needs to be communicated to an audience that should not see the full privileged work product.
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
Read VDR documents and extract issues per house categories and materiality thresholds, producing findings in house memo format. Use when user says "review the data room", "extract issues from [folder]", "diligence review", "what's in the VDR", or points at VDR documents.