Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legal_hold fields in _log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "legal-hold" 技能: 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/legal-hold/SKILL.md 2. 保存为 ~/.claude/skills/legal-hold/SKILL.md 3. 装好后重载技能,告诉我可以用了
--status (no slug): read _log.yaml, produce portfolio-wide hold report.~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md + log row.~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → privilege markings, hold template pointer, escalation norms.--issue: capture scope, custodians, date range, systems. Draft legal-hold-v1.docx. Update legal_hold fields. Append history entry. Set next_refresh (default +6mo).--refresh: capture scope/custodian changes. Draft next version. Update last_refresh + next_refresh. Flag departed custodians.--release: capture release date, retention instruction. Draft release notice. Set released: field.A legal hold is the most mechanical high-stakes document in-house counsel writes. The notice itself is templated. The failure modes are operational: issued too late, scoped too narrowly, never refreshed, never released. This skill owns all four phases: issue → refresh → (release) → track.
The portfolio already flags missing holds; this skill writes them.
Preservation duties vary materially by forum. Federal common law (via Zubulake / Residential Funding / Rule 37(e)) differs from state practice; states differ from each other on trigger timing, scope, sanctions, and spoliation remedies; regulatory preservation obligations overlay civil rules in some matters (SEC Rule 17a-4, HIPAA, etc.). The trigger, scope, and sanctions exposure cited in the draft are a starting-point read for the forum named in the matter — confirm with counsel before issuing, refreshing, or releasing.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — log row (legal_hold fields + status)~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — matter context (counterparty, facts, key custodians from internal_owners)~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md — house style for litigation hold template pointer, privilege marking, escalation normsConflicts gate — unbypassable. Before issuing, refreshing, or releasing a hold, check _log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace is set up. I won't issue, refresh, or release a legal hold on a matter that hasn't been intaken — the conflicts check is the gate, and a hold issued against an unmanaged matter has no_log.yamlrow to tracklast_refresh/next_refresh/releasedagainst."
Do not proceed on an unintaken matter. Intake is what runs conflicts and writes the _log.yaml row the --refresh / --release / --status flags operate against.
The command takes a flag: --issue | --refresh | --release | --status. Default (no flag) → prompt.
--issue — first issuanceRequired when legal_hold.issued == false and the matter is active or reasonably anticipated.
Before issuing the hold to custodians (the consequential act): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:
Issuing a legal hold has legal consequences — the scope, custodian list, and timing create the preservation record the company will be judged on if spoliation is argued later. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
…
Draft a DMCA takedown notice, triage one you received, or draft a §512(g) counter-notice. Use when asserting copyright through a §512(c)(3) takedown with the fair-use and perjury gates, when an incoming takedown needs triage into comply / counter / engage / ignore options, or when drafting a §512(g)(3) counter-notice with the consent-to-federal-jurisdiction gate.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material. Use when the user says "depo prep for [witness]", "build a depo outline", or "prepare for [name]'s deposition".
Manage matter workspaces — create, list, switch, close, or detach the active matter. Use in multi-client private practice to keep one client's context separate from another, or when a substantive skill needs to know which matter it's working in.