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

Litigation Support Summary

ASecurity

Generates structured management summaries of active commercial litigation matters. Covers case overview, procedural posture, strategy, deadlines, discovery status, budget, and risk analysis. Use when preparing case status reports, onboarding stakeholders to active litigation, or conducting periodic case reviews.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

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

Installs into .claude/skills of the current project.

Are you the author of Litigation Support Summary?

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

Security grade badge for Litigation Support Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-litigation-support-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-litigation-support-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: litigation-support-summary
title: Litigation Support Summary
description: Generates structured management summaries of active commercial litigation matters. Covers case overview, procedural posture, strategy, deadlines, discovery status, budget, and risk analysis. Use when preparing case status reports, onboarding stakeholders to active litigation, or conducting periodic case reviews.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/litigation-support-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Litigation Support Summary

Synthesizes case materials into a structured management document (5-10 pages) for legal teams and clients to track progress on active litigation.

## Quick Start

1. Gather inputs: pleadings, docket sheet, court orders, discovery materials, scheduling orders
2. Follow the six-section output structure below
3. Apply the quality checks before delivering

## Required Inputs

- **Case file**: pleadings, court orders, docket sheet, case caption/number, presiding judge
- **Discovery materials**: requests, responses, production logs, deposition transcripts
- **Scheduling orders**: court-imposed deadlines, trial date, expert disclosure dates
- **Correspondence** (if available): strategic memos, client communications
- **Budget/staffing** (if available): litigation budget, team assignments

## Output Structure

### 1. Case Overview & Procedural Posture

| Field | Content |
|-------|---------|
| Caption & Docket | Full case caption, docket number |
| Court & Judge | Court, jurisdiction, presiding judge |
| Parties | All parties with roles |
| Claims & Defenses | Each cause of action/counterclaim with status |
| Procedural Stage | Pleadings / discovery / pre-trial / trial |
| Significant Rulings | Key motions, hearings, orders |

### 2. Strategy & Theory of Case

- Primary legal theories and key factual arguments
- Desired outcome (damages, injunctive relief, dismissal, etc.)
- Strategy evolution based on discovery/rulings/new facts
- Candid strengths/weaknesses for both sides:

| Factor | Our Position | Opposing Position |
|--------|-------------|-------------------|
| Strongest argument | | |
| Key vulnerability | | |
| Critical unresolved issue | | |

- ADR/settlement posture: demand/offer history, mediation prospects

### 3. Timeline & Critical Deadlines

Chronological table covering discovery cutoffs, expert disclosures, dispositive motion deadlines, pretrial conferences, trial date, and internal targets.

| Date | Event/Deadline | Status | Action Required |
|------|---------------|--------|-----------------|
| _past_ | Event | Complete | -- |
| _upcoming_ | Deadline | Pending | Owner + prep needed |

Flag deadlines requiring immediate attention.

### 4. Discovery Status & Key Evidence

**Written discovery** (interrogatories, doc requests, RFAs): track served, received, outstanding, disputes.

**Depositions**: witness, date, status (completed/scheduled/needed), key testimony.

**Critical evidence**: most significant documents/testimony and relevance to case theory.

**Open issues**: privilege disputes, protective orders, Daubert challenges, outstanding productions.

### 5. Resource Allocation & Budget

Track by category (attorney fees, experts, e-discovery, court reporters, travel): budget, spent, projected remaining. Include team assignments and resource constraints.

Omit if no budget data available; note the gap and recommend gathering it.

### 6. Risks, Opportunities & Recommendations

- **Risks**: adverse outcome exposure (liability + damages range), cost escalation triggers, reputational concerns
- **Opportunities**: favorable developments, settlement leverage, dispositive motion prospects
- **Recommendations**: numbered, actionable next steps with priority (High/Medium/Low) and owner

## Quality Checks

- Cite specific documents by name and page/paragraph when asserting facts
- Distinguish established facts, disputed facts, and legal contentions
- Provide candid assessments, not advocacy; flag information gaps
- Use accessible language while maintaining legal precision; define terms of art on first use
- Note the summary date; frame as a living document
- Mark as attorney-client privileged / work product as appropriate

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', ...

698461 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 →