class-action-summary
Produces structured U.S. class action lawsuit summaries covering claims, class definition, Rule 23 analysis, procedural history, and outcomes. Use when summarizing class actions, class certification rulings, MDL proceedings, or settlement approvals for litigation evaluation, due diligence, or compliance monitoring.
Best use case
class-action-summary is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Produces structured U.S. class action lawsuit summaries covering claims, class definition, Rule 23 analysis, procedural history, and outcomes. Use when summarizing class actions, class certification rulings, MDL proceedings, or settlement approvals for litigation evaluation, due diligence, or compliance monitoring.
Teams using class-action-summary should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/class-action-summary/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How class-action-summary Compares
| Feature / Agent | class-action-summary | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Produces structured U.S. class action lawsuit summaries covering claims, class definition, Rule 23 analysis, procedural history, and outcomes. Use when summarizing class actions, class certification rulings, MDL proceedings, or settlement approvals for litigation evaluation, due diligence, or compliance monitoring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Class Action Lawsuit Summary
Produce a neutral, citation-ready summary of a U.S. class action from filing through resolution or current posture.
## Required Inputs
1. Operative complaint (and amendments).
2. Docket report with key dates and ECF numbers.
3. Orders on motions to dismiss, class certification, summary judgment, trial.
4. Settlement/approval materials or verdict documents.
5. MDL transfer/coordination orders if applicable.
## Workflow
1. Extract metadata into the caption block.
2. Write a 3–4 sentence executive summary.
3. Complete each section per the table below with record citations.
4. Run certification and resolution checklists.
5. Add significance note if there is a published opinion or industry impact.
## Caption Block
```
Case Caption:
Court:
Docket No.:
Filed:
Judge(s):
Jurisdiction/Venue:
MDL/JPML (if any):
Parties (Plaintiffs/Defendants):
Status (pending/settled/tried/appeal):
```
## Sections
| Section | Content |
|---|---|
| Claims and Allegations | Causes of action; statutes cited; alleged misconduct and timeframe; class period; damages theory; key defenses resolved |
| Class Definition and Certification | Proposed/certified class definitions; membership criteria; geographic/temporal limits; subclasses; estimated size; Rule 23(a) findings; Rule 23(b) basis ((b)(1)/(b)(2)/(b)(3)); certification granted/denied/decertified with reasons |
| Procedural History | Filing; removal/transfer; major motion rulings; discovery milestones; certification briefing and order date; Rule 23(f) appeals; MDL coordination; trial or settlement milestones |
| Resolution / Outcomes | Settlement amount and fund structure; claims process/deadlines; allocation; fees/costs/service awards; non-monetary relief; approval dates/objections; verdict/damages; post-trial motions/appeals; current posture if pending |
| Significance | Published opinions; precedential holdings; industry impact (include only if applicable) |
## Certification Checklist
- [ ] Operative class definition text and class period
- [ ] Rule 23(a): numerosity, commonality, typicality, adequacy
- [ ] Rule 23(b) basis and relief type (injunctive vs damages)
- [ ] Subclasses and rationale
- [ ] If denied/decertified: court's reasoning (predominance, ascertainability, typicality)
## Resolution Checklist
- [ ] Settlement amount; reversionary or cy pres terms
- [ ] Allocation formula and claims rate
- [ ] Attorneys' fees, costs, service awards
- [ ] Injunctive/programmatic relief and compliance monitoring
- [ ] Preliminary and final approval dates; opt-out and objection counts
## Citation Format
Use record-specific citations: document title, ECF number, date, pin cite.
```
("Order Granting Class Certification", ECF No. 123, at 7-10 (2024-05-12))
```
## Pitfalls
- Distinguish allegations from adjudicated facts — use "alleged" or "purported" unless admitted or adjudicated.
- Prefer operative complaint and final orders; flag inconsistencies across versions.
- State "Not stated in record" for missing facts — never infer.
- Note whether the case is federal Rule 23 or a state analog; mark `[VERIFY]` if unclear.
- Omit sealed or protected information; note confidentiality limits.
- Highlight interlocutory appeals and their disposition.