skills/legal/deposition-impeachment-builder/SKILL.md
Drafts deposition-ready impeachment sequences using the Commit–Credit–Confront (CCC) method. Use this skill when the user mentions impeachment preparation, prior inconsistent statements, Commit-Credit-Confront, CCC method, deposition cross-examination, FRE 613, witness contradictions, impeachment scripts, prior testimony conflicts, or asks for help building impeachment sequences. Also trigger when the user references creating transcript clips for summary judgment, preparing confrontation questions, or analyzing contradictions between deposition testimony and prior documents. Even if the user just says "this witness changed their story" or "build me an impeachment sequence," use this skill.
npx skillsauth add casemark/skills deposition-impeachment-builderInstall 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.
Impeachment at deposition is the highest-skill questioning technique in civil litigation — and the most commonly botched. Attorneys either confront too early (before locking the witness in), skip the credit phase (weakening the contradiction's impact), or ask open-ended follow-ups after confrontation (giving the witness an escape). A poorly executed impeachment is worse than none at all, because it educates the witness and inoculates them for trial.
This skill produces a controlled Commit–Credit–Confront script, a deployment memo with timing recommendations, and a checklist of missing information — grounded in FRE 613, FRE 801(d)(1)(A)/(d)(2), and FRCP 30 guardrails.
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: federal court; impeachment-only use; conservative confrontation variant; deposition (not trial).
If any required input is missing, pause and ask targeted follow-up questions. Never fabricate quotes, dates, page numbers, or document attributes.
Before drafting, tie the contradiction to a claim element, defense element, damages component, or credibility theme in one sentence. If you cannot, flag the impeachment as a candidate for trial cross-examination rather than deposition use.
Goal: Eliminate every escape hatch before the witness knows a contradiction is coming.
Rules:
Template pattern:
"Just so I understand: you [core proposition], correct?"
"You're not saying [narrowing qualifier]—you're saying [absolute proposition], right?"
"You're certain about that? No doubt in your mind?"
"And [close remaining escape route], correct?"
Establish reliability and adoption of the prior statement. Tailor foundation to prior statement type:
| Statement Type | Credit Focus | Key Questions | |---|---|---| | Prior deposition/hearing testimony | Oath, counsel present, opportunity to correct errata | "You were under oath?" / "Your lawyer was present?" / "You reviewed and didn't change this testimony?" | | Signed declaration / verified response | Signature, review, penalty of perjury | "You read this before signing?" / "You swore the contents were true?" | | Email / text authored by witness | Account ownership, routine practice, contemporaneity, recipients, intent to rely | "That's your email address?" / "You sent this in the ordinary course?" / "You intended [recipient] to rely on it as accurate?" | | Email / doc drafted by others, adopted by witness | Review, approval, transmission authority | "You reviewed this before it was sent?" / "You authorized it to go out?" | | Interrogatory response | Witness's role in preparation, verification, accuracy steps | "Did you review the draft?" / "You signed the verification?" | | Corporate record / third-party doc | Receipt, reliance, notice — flag: may not constitute witness's "statement"; different evidentiary posture | "You were copied?" / "You relied on it?" |
Credit containment: If witness tries to devalue the prior statement mid-Credit ("I was confused"):
"You wouldn't give false testimony just because you were [tired/confused], right?"
Disciplined rhythm — do not deviate:
[PAGE:LINE] placeholder if pin-cite unavailable| Variant | Language | Use When | |---|---|---| | Conservative | "So your testimony today is different from what you said under oath on [DATE], correct?" | Preserving the record; avoiding overreach | | Aggressive | "Which is accurate — your [email/deposition] from [DATE], or your testimony today?" | Witness is a party; full contradiction is binary |
Containment follow-ups (if witness evades):
Include:
Timing decision table:
| Objective | Timing | Rationale | |---|---|---| | Discovery roadmap | Early | Forces witness to explain, surfaces documents/witnesses | | Trial-quality clip | Bank | Starker after multiple aligned denials; avoids educating witness | | Settlement signal | Mid-deposition | Demonstrates narrative instability without full rehearsal | | Rapid-fire credibility destruction | Series at end | Effective for witnesses with multiple contradictions |
List all [PLACEHOLDERS] requiring attorney completion before use:
[PAGE:LINE] — pin-cite for prior statement[EXHIBIT NO.] — exhibit identifier[DATE] — any unconfirmed dateAfter delivering the initial impeachment package, ask:
If the user doesn't answer, recommend the conservative variant and proceed if authorized.
Before finalizing, verify:
Evidentiary rules — federal defaults (flag state variations):
State-specific flags:
| Jurisdiction | Key Rule | |---|---| | California | EC § 770 — judge may exclude extrinsic evidence unless witness given opportunity to explain; EC § 780 — credibility factors | | New York | CPLR 4514 — stricter limits on unsworn/unwritten prior statements | | Common law (Browne v. Dunn) | Must "put the case" to the witness — confront explicitly before relying in closing | | Arbitration | AAA/JAMS rules and scheduling order govern; treat as separate regime |
Professional responsibility:
Anti-hallucination (non-negotiable):
[PLACEHOLDER — VERIFY BEFORE USE][VERIFY]Attorney review required before use in any proceeding. This skill is attorney work product, not legal advice.
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.