Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Deposition Summary Narrative

ASecurity

Transforms deposition transcripts into topic-organized narrative memoranda with page-line citations, flagged admissions, contradictions, and credibility issues. Use when summarizing depositions, condensing transcripts for trial prep, or building case strategy during discovery or pre-trial phases.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgit

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill deposition-summary-narrative --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Deposition Summary Narrative?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Deposition Summary Narrative
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-deposition-summary-narrative/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-deposition-summary-narrative)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: deposition-summary-narrative
title: Deposition Summary — Narrative
description: Transforms deposition transcripts into topic-organized narrative memoranda with page-line citations, flagged admissions, contradictions, and credibility issues. Use when summarizing depositions, condensing transcripts for trial prep, or building case strategy during discovery or pre-trial phases.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/deposition-summary-narrative
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
tags: [summarization, summary]
---

# Deposition Summary — Narrative

Synthesizes a deposition transcript into a strategic narrative memorandum with embedded citations, flagged admissions, and credibility analysis.

## Prerequisites

1. **Deposition transcript** — full text with page and line numbers
2. **Case caption and docket number**
3. **Witness role** — plaintiff, defendant, fact witness, expert, or 30(b)(6) representative
4. **Attendee list** — attorneys and represented parties (preferred)

## Quick Start

1. Collect transcript and case identifiers
2. Identify witness role and key topics from transcript
3. Generate output sections in order: Header → Executive Overview → Narrative Body → Exhibit Log → Privilege & Objection Notes
4. Embed `(page:line–line)` citations after every material assertion
5. Flag admissions, contradictions, and memory gaps throughout

## Output Sections

### 1. Header Block

- Case caption (style of cause, court, docket number)
- Deponent name and litigation role
- Date, location, attorneys present with affiliations
- Privilege notice: "Prepared at the direction of counsel. Attorney Work Product — Privileged and Confidential."

### 2. Executive Overview (1–2 paragraphs)

Cover key topics, most significant admissions, credibility concerns, and impact on case theory.

### 3. Narrative Body

Organize by **topic, not Q&A order**. Typical sections: Background & Qualifications, Events Leading to Incident, The Incident, Damages & Injuries, Medical Treatment, Employment & Financial Impact. Adjust to fit case type.

Per section:
- Write flowing prose — never reproduce Q&A format
- Cite immediately after each assertion: `(78:3–15)`
- Flag admissions: *"Significantly, the witness acknowledged..."*
- Flag contradictions: *"This conflicts with the affidavit stating..."*
- Flag memory gaps: *"Witness claimed no recollection of X despite prior specificity about Y (167:12–168:3)."*
- Note demeanor shifts or evasiveness inline

### 4. Exhibit Log

| Exhibit No. | Description | Witness Response |
|---|---|---|
| Ex. 1 | Document type / date | Authenticated / Denied / No recognition / Contradicted |

### 5. Privilege & Objection Notes

- Instructions not to answer (question, objecting counsel, basis)
- Privilege assertions (attorney-client, work product, FRE 408)
- Material objections on form, foundation, or scope

## Pitfalls and Checks

- **Always cite**: never paraphrase a critical admission without `(page:line–line)`
- **Length target**: ~25–33% of transcript length; completeness over brevity
- **Accuracy**: do not characterize beyond what the transcript supports; summary must be defensible to opposing counsel
- **Work product header**: repeat on every page with case name and deponent
- **Follow-up queries**: cite both summary location and underlying transcript page/line
- **Jurisdiction**: follows US federal and state civil litigation conventions

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →