skills/legal/preservation-letter/SKILL.md
Drafts litigation hold and document preservation letters under FRCP 37(e) and state equivalents. Covers custodian identification, ESI scope, hold implementation, and spoliation warnings. Use when sending preservation notices, litigation hold letters, spoliation notices, or evidence preservation demands.
npx skillsauth add casemark/skills preservation-letterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Drafts a formal preservation notice establishing the opposing party's duty to preserve evidence, tailored to the matter's custodians, data sources, and time period.
Gather before drafting:
Format as formal business correspondence: letterhead, date, recipient block (name/title/org/address), re-line with matter description.
| Section | Content | |---|---| | Opening Notice | Counsel, client, dispute nature. If filed: caption, court, docket. If pre-suit: state client reasonably anticipates litigation. Cite FRCP 37(e) or state equivalent. | | Matter Description | Factual context sufficient for recipient to identify custodians and sources. Do not disclose litigation strategy. | | Preservation Scope | Categorized instructions per scope table below | | Implementation Instructions | Litigation hold procedures per checklist below | | Spoliation Consequences | Legal consequences of non-compliance | | Response Requirements | Written acknowledgment deadline (5–10 business days), hold confirmation, contact info | | Closing | Formal closing, signature block with bar admissions |
Include only categories applicable to the dispute:
| Category | Examples | |---|---| | Paper | Contracts, memoranda, notes, financials, invoices, drafts | | Electronic comms | Email, texts, IMs, social media, voicemails — all platforms/devices including personal if used for business | | ESI | Documents, spreadsheets, databases, presentations, calendars — native format with metadata intact | | Cloud/storage | Cloud services, shared drives, backups, archived data, servers, mobile devices | | Physical | Products, equipment, machinery, vehicles (if applicable) | | Audio/visual | Recordings, photos, videos, surveillance footage |
Key emphasis: metadata must be preserved intact; no format conversions; personal devices/accounts included if used for business.
Instruct recipient to:
Address with appropriate firmness:
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.