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

ASecurity

Generates topic-based deposition summaries for commercial litigation with exhibit cross-referencing. Produces a two-column table (page:line | neutral summary) with embedded exhibit citations. Use when summarizing depositions, creating deposition digests, indexing exhibits, or preparing witness testimony summaries during discovery.

15 stars
0 votes
0 copies
1 views
Added 6/7/2026
ai-agentsgitapi

Works with

api

Security Analysis

A100/100

Scanned 6/7/2026

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

Installs into .claude/skills of the current project.

Are you the author of Deposition Summary?

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

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

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
title: Deposition Summary with Key Document Index
description: Generates topic-based deposition summaries for commercial litigation with exhibit cross-referencing. Produces a two-column table (page:line | neutral summary) with embedded exhibit citations. Use when summarizing depositions, creating deposition digests, indexing exhibits, or preparing witness testimony summaries during discovery.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/deposition-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Deposition Summary with Key Document Index

Transforms a deposition transcript into a topic-based summary table with integrated exhibit cross-references for rapid navigation between testimony and documentary evidence.

## Prerequisites

- Complete deposition transcript with page and line numbering
- Exhibit list and files referenced or marked during deposition
- Case context: party names, key contract sections, claims at issue

## Workflow

### 1. Review Transcript

Read the full transcript and identify:
- Natural topic breaks (explicit subject changes and thematic shifts)
- Every exhibit reference — formal ("Exhibit 3") and informal ("the email we just reviewed")
- Key admissions, contradictions, evasive answers, and authentication testimony

### 2. Extract Topics

For each topic, capture:

| Element | Requirement |
|---|---|
| Topic heading | Specific — "Witness Knowledge of Payment Default Under §4.2" not "Payment Issues" |
| Page:line range | Start and end of testimony on that topic |
| Summary | 2-3 sentences, neutral, no legal conclusions |
| Exhibits referenced | Exhibit number + how witness characterized/authenticated it |
| Notable moments | Admissions, contradictions, refusals to answer |

### 3. Build Exhibit Index

Create a master exhibit cross-reference table:

| Exhibit | Description | Transcript Refs (pg:ln) | Witness Characterization |
|---|---|---|---|
| Ex. 1 | [doc type] | 45:3-47:12, 102:8-103:1 | [how witness described it] |

### 4. Assemble Summary Table

Primary deliverable — two-column table:

```
| Transcript Cite | Topic & Summary |
|-----------------|-----------------|
| pp. 12:4-18:22  | **Formation of the Supply Agreement**
|                 | [2-3 sentence neutral summary]. See Ex. 3
|                 | (Supply Agreement, discussed at 14:8-15:2).
|                 | Notable: Witness admitted not reading §4.2
|                 | before signing (15:18-22). |
```

Within each summary cell:
- Embed exhibit references discussed during that testimony
- Cite specific page:line for key admissions
- Use hierarchical headings for major topics vs. subtopics

### 5. Output

Produce both:
- **DOCX** — formatted table with hyperlinks to exhibits and transcript locations
- **PDF** — preserved hyperlinks, full-text searchable, locked for filing

## Key Rules

- **Neutral tone only** — summarize what the witness said, not what it means for the case
- **Specificity over brevity** — "Witness denied receiving the October 14 demand letter" not "Witness denied receiving correspondence"
- **Organize by substance, not questioner** — consolidate redirect and direct testimony on the same topic under one heading
- **Capture authentication testimony** — note when witness identifies, authenticates, or disputes a document
- **Flag evasive responses** — mark non-responsive answers, memory claims, and qualified answers

## Quality Checklist

- [ ] Every exhibit mentioned in testimony appears in summary and exhibit index
- [ ] No exhibits referenced that weren't actually discussed
- [ ] All page:line citations verified against transcript
- [ ] Summaries reflect actual testimony — no interpretation or legal conclusions
- [ ] Topic headings specific enough for at-a-glance navigation
- [ ] No privileged communications or work product included
- [ ] Hyperlinks resolve to correct targets

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 →