summarize-files
Generates structured summaries of legal documents (contracts, pleadings, correspondence, transactional materials). Triggers when the user asks to summarize case files, agreements, pleadings, or any legal materials for review, onboarding, or status reporting.
Best use case
summarize-files is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates structured summaries of legal documents (contracts, pleadings, correspondence, transactional materials). Triggers when the user asks to summarize case files, agreements, pleadings, or any legal materials for review, onboarding, or status reporting.
Teams using summarize-files 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/summarize-files/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How summarize-files Compares
| Feature / Agent | summarize-files | 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?
Generates structured summaries of legal documents (contracts, pleadings, correspondence, transactional materials). Triggers when the user asks to summarize case files, agreements, pleadings, or any legal materials for review, onboarding, or status reporting.
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
# Summarize Legal Documents Produce standalone, structured summaries of one or more legal documents for professional reference. ## Quick Start 1. Receive one or more legal files (contracts, pleadings, correspondence, transactional docs). 2. Read all uploaded content exhaustively — never sample or skip sections. 3. Classify each document, extract key data, and output the summary using the template below. ## Workflow ### 1. Classify Document Type | Type | Analysis Focus | |---|---| | Contract / Agreement | Parties, obligations, terms, defined terms, reps & warranties, conditions precedent, dispute provisions | | Pleading | Causes of action, factual allegations, relief requested, procedural posture, legal authority | | Correspondence | Negotiation positions, admissions, strategic signals, communication timeline | | Transactional | Deal structure, consideration, reps & warranties, closing conditions, indemnification | ### 2. Extract Key Data From every document, capture: - Parties (full legal names, roles) - Key dates and deadlines - Monetary amounts and consideration - Claims, defenses, or obligations - Legal authority cited - Exhibits, attachments, referenced materials - Defined terms (use consistently throughout) - Ambiguities or internal conflicts ### 3. Output Summary ``` # Summary: [Document Title / Subject Matter] Date of Summary: [date] ## Overview [Type, parties, fundamental purpose — 2-3 sentences] ## Key Parties [Table or list: name, role, relationship] ## Substantive Summary [Organized by logical sections mirroring the source structure] ## Key Terms and Conditions [Dates, deadlines, amounts, obligations — use tables where appropriate] ## Notable Issues [Ambiguities, conflicts, missing information, concerns] ## Source Attribution [For multi-file summaries: which document each key fact derives from] ``` ## Pitfalls and Checks - **Completeness over brevity** — never omit material information; flag conflicts rather than resolving by assumption. - **Source attribution** — cite which document each significant fact comes from, especially across multiple files. - **Preserve precision** — retain qualifications, limitations, and conditions; use defined terms as defined in the source. - **Proportional length** — target 70-90% reduction while retaining all material information. - **No legal conclusions** — summarize positions as presented; do not evaluate merits or predict outcomes. - **Readability** — bold party names and key terms; use tables for claims, obligations, or chronological events.
Related Skills
creating-teaching-files
Curates and annotates imaging cases for educational purposes with clinical correlation. Use when creating teaching files, annotating educational cases, or building case libraries.
skill-name
Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.
writing-surgical-consultation-notes
Creates structured surgical consultation responses with assessment and surgical candidacy determination. Use when responding to surgical consults, evaluating surgical candidates, or documenting surgical recommendations.
writing-operative-reports
Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or recording intraoperative findings.
writing-irb-submissions
Creates IRB submission packages with protocol summaries, consent forms, and risk-benefit analysis. Use when submitting to IRB, preparing ethics applications, or writing consent documents.
writing-grant-applications-research
Structures NIH/foundation grant applications with specific aims, significance, and innovation sections. Use when writing research grants, preparing NIH applications, or structuring grant proposals.
writing-admission-orders
Generates structured admission order sets with diagnosis-specific protocols and safety checks. Use when admitting patients, creating admission orders, or setting up inpatient care plans.
validating-new-laboratory-tests
Structures test validation with precision, accuracy, linearity, and reference range establishment. Use when validating new assays, documenting method comparisons, or establishing reference ranges.
validating-clinical-data-quality
Structures data quality assessment with completeness, accuracy, and consistency validation. Use when auditing clinical data, assessing data quality, or validating data integrity.
triaging-emergency-presentations
Applies ESI triage methodology to assign acuity levels based on presenting complaints, vital signs, and resource needs. Use when triaging ED patients, assigning acuity scores, or prioritizing emergency cases.
tracking-treatment-response
Monitors treatment response using imaging criteria, biomarkers, and clinical assessment with documentation. Use when assessing treatment response, documenting disease status, or tracking progression.
tracking-incidental-findings
Manages incidental finding follow-up using ACR White Paper recommendations. Use when tracking incidentalomas, scheduling follow-up imaging, or managing unexpected findings.