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

Discovery Summary

ASecurity

Generates structured, citeable summaries of discovery documents (interrogatories, RFPs, RFAs, depositions, productions). Extracts admissions, inconsistencies, evidentiary gaps, and objections with precise source citations. Use when summarizing discovery responses, preparing for depositions, identifying discovery gaps, or building trial preparation materials.

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

Security Analysis

A100/100

Scanned 6/7/2026

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

Installs into .claude/skills of the current project.

Are you the author of Discovery Summary?

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

Security grade badge for Discovery Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-discovery-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-discovery-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: discovery-summary
title: Discovery Document Summarization
description: Generates structured, citeable summaries of discovery documents (interrogatories, RFPs, RFAs, depositions, productions). Extracts admissions, inconsistencies, evidentiary gaps, and objections with precise source citations. Use when summarizing discovery responses, preparing for depositions, identifying discovery gaps, or building trial preparation materials.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/discovery-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Discovery Document Summarization

Produces a structured summary of discovery materials with precise citations for trial preparation and case strategy. Applies regardless of which side the user represents.

## Prerequisites

- **Discovery documents** — interrogatory responses, RFP responses, RFA answers, deposition transcripts, produced documents
- **Case context** — claims, defenses, key issues, parties
- **Citation sources** — Bates ranges, response numbers, or transcript page:line references

## Quick Start

1. Identify discovery types present in the materials
2. Produce the four-part output structure below
3. Cite every factual assertion to a specific source

## Output Structure

### 1. Executive Overview

3–5 paragraph narrative covering:

- Significant admissions or revelations
- Key documents or testimony
- Inconsistencies across responses
- Notable refusals, evasions, or privilege assertions
- Critical evidentiary gaps

### 2. Discovery Breakdown

Organize by discovery type or by claim/issue — whichever better serves the matter.

Per section, include a header block:

| Field | Detail |
|---|---|
| Discovery Type | Interrogatories / RFP / RFA / Deposition |
| Requesting Party | {name} |
| Responding Party | {name} |
| Date(s) | {response date(s)} |

Then summarize:

- **Admissions** — quote or paraphrase with exact citation
- **Produced documents** — description, Bates range, relevance (1–2 sentences)
- **Objections** — type and whether it blocked material disclosure
- **Evasive/incomplete responses** — what specifically was avoided

### 3. Cross-Reference Analysis

| Topic/Fact | Source A (cite) | Source B (cite) | Consistent? | Notes |
|---|---|---|---|---|
| {fact} | {cite} | {cite} | Yes/No | {discrepancy detail} |

### 4. Outstanding Discovery Issues

- [ ] Incomplete responses requiring follow-up (list by response number)
- [ ] Objections warranting meet-and-confer or motion to compel
- [ ] New custodians or document sources identified in testimony
- [ ] Areas where supplemental requests are warranted
- [ ] Privilege log deficiencies

## Pitfalls and Checks

- **Cite everything** — every assertion needs a response number, Bates stamp, or page:line
- **Stay objective** — no legal conclusions; flag apparent evasion but let attorneys draw conclusions
- **Sufficient detail** — attorneys should be able to work from the summary without pulling underlying documents for routine tasks
- **Flag patterns** — systematic objection strategies, coordinated non-responses, recurring privilege claims
- **Navigation** — include a table of contents when materials span 3+ discovery categories or 10+ responses

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 →