skills/legal/deposition-preparation/SKILL.md
Produces a comprehensive deposition preparation package for taking or defending depositions in U.S. civil litigation. Use this skill whenever the user mentions deposition prep, depo outlines, witness examination planning, deposition strategy, cross-examination preparation, 30(b)(6) witness prep, expert deposition planning, impeachment materials, or asks for help preparing to take or defend any deposition. Also trigger when the user references FRCP 30, deposition notices, deposition exhibit strategy, witness profiling for depositions, or asks about deposition time allocation. Even if the user just says "I have a depo next week" or "help me prep for questioning this witness," use this skill.
npx skillsauth add casemark/skills deposition-preparationInstall 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.
Depositions are one of the highest-leverage moments in U.S. civil litigation. Fewer than one percent of cases reach a jury, making the deposition the functional equivalent of trial. Testimony becomes a permanent evidentiary artifact that drives summary judgment, settlement posture, expert framing, trial examination, and impeachment. When prep is done poorly, the record is incomplete, admissions are missed, privilege is waived, and the client gets locked into avoidable testimony.
This skill produces a deposition preparation package a litigation team can actually use at the table—not just a question list, but a strategic plan tied to elements and defenses, a time allocation, exhibit integration, impeachment scripts, and (when defending) an ethics-safe witness prep agenda.
The primary grounding is FRCP 26 and 30, with supporting guidance from FRE 612, 613, 702, 803, and 901. For detailed legal standards, read references/legal-standards.md. For jurisdiction-specific adaptations, read references/jurisdiction-adaptations.md.
Ask every time unless the user says "use defaults" or "just draft." Gather:
If the user doesn't respond, apply and clearly label these defaults: taking deposition; objectives of discovery and impeachment setup; seven hours; hybrid topical-chronological format.
Request these materials—they substantially improve quality:
If materials are missing, flag them explicitly. Proceed with labeled assumptions rather than stalling, but list "Open Items / Needed Inputs" for attorney follow-up.
Deposition outlines fail when they're topic lists untethered to burdens and elements. Every substantive topic must serve a purpose: establishing a prima facie element, supporting an affirmative defense, or attacking credibility.
Extract or infer claims, defenses, and disputed issues from the pleadings. If pleadings aren't available, create a provisional issue map with [ASSUMED] markers.
| Issue/Element | What We Need to Prove/Disprove | What This Witness Can Establish | Best Documents/Prior Statements | Target Admission/Lock Point | |---|---|---|---|---|
Example: In a negligence case where "notice" is an element, the lock point might be: "You received the inspection report (Ex. 12) on March 3 and understood it described the hazard."
Do not invent evidence. Use placeholders and flag them for attorney verification when the record is unknown.
The issue map also supports proportionality under FRCP 26(b)(1)—you can justify time spent by showing its link to claims, defenses, and the importance of the issues.
Compile: role and tenure; relationship to key actors; likely motivation or bias; prior statements and testimony; personal knowledge vs. hearsay vs. learned knowledge (critical for 30(b)(6) designees); all documents authored by, received by, or mentioning the witness.
Include an "anticipated demeanor and risk" paragraph:
Match structure to witness type and litigation objective:
For detailed witness-type adaptations (30(b)(6), expert, apex, defending), read references/witness-types.md.
The outline must be easy to execute under time pressure and easy for later users (SJ drafter, trial examiner) to mine for usable testimony.
| Topic | Est. Time | Priority (1–5) | Notes | |---|---|---|---|
Total should approximate the controlling limit. Federal default is 7 hours under FRCP 30(d)(1). Whether breaks count against time varies by stipulation and court order—confirm with the attorney.
Preliminary Section (~15 min)
Substantive Modules — for each topic, use the funnel technique:
Jumping to the locking-in phase too early is a common and costly mistake. Leading immediately suggests the answer and may prevent discovering a more damaging fact the witness would have volunteered.
FWD Boxing-In (Critical for SJ Prep)
This is the most critical tool for summary judgment preparation. Exhaust the witness's memory so they cannot "remember" new facts at trial:
Failing to ask the catch-all question is one of the most common errors—without it, the witness can appear at trial with a "refreshed memory" and impeachment is significantly weakened.
Conclusion Section (~15 min) — completeness check, additional witnesses/documents identification, truthfulness confirmation, reservation of rights if needed.
| Topic | Exhibit | When to Use | Purpose | Foundation Questions | Impeachment Hook | |---|---|---|---|---|---|
For every major exhibit, prepare a Foundation Script. Example:
"I'm handing you what's been marked as Exhibit 4. Do you recognize it? It's an email from you to Sarah Smith dated January 10, correct? You wrote this in the ordinary course of your job, right? Looking at the second paragraph, you wrote [quote]. What did you mean by that?"
Include foundation for authentication (FRE 901) and, where applicable, business records exception (FRE 803(6)).
Flag FRE 612 implications when documents refresh recollection—the adverse party may be entitled to production.
Prompt for non-traditional exhibits that often prove decisive: calendars, metadata, system logs, training records, ticketing systems, version histories, collaboration platform records.
| Topic | Prior Statement | Source/Citation | Expected Current Testimony | Contradiction | Approach | |---|---|---|---|---|---|
Use the Commit → Credit → Confront method:
If exact citations (page, line, paragraph) aren't available, insert placeholders and mark for attorney verification. Reference FRE 613 requirements for prior inconsistent statements.
Output a two-lane deliverable by default, plus a defending pack when appropriate.
The one-pager is not optional—it's the execution instrument. Opposing counsel benefits when the examining attorney can't find the next move.
For defending-specific details, read references/witness-types.md (defending section).
At the very top of every output, before any substantive content, include:
This front matter is a critical anti-hallucination guardrail: it tells the attorney exactly what was assumed and what must be verified.
After delivering the initial package, ask:
If the user doesn't answer, recommend the next best refinement based on stated objectives and proceed if authorized.
Before finalizing, run through the self-audit checklist in references/quality-checklist.md. The critical checks:
references/legal-standards.mdRead these when you need deeper guidance on specific areas:
references/legal-standards.md — FRCP/FRE rules, ethics of witness preparation, privilege, anti-hallucination guardrails for legal authorities, malpractice risk areasreferences/witness-types.md — Detailed adaptations for defending depositions, 30(b)(6) corporate reps, expert witnesses, and apex witnessesreferences/jurisdiction-adaptations.md — State-specific variations (CA, TX, NY), time limits, objection practice, expert standardsreferences/quality-checklist.md — Full self-audit checklist for the final packagedevelopment
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.