police-report-summary
Summarizes police reports and incident documentation into structured, source-attributed legal work product. Extracts incident details, chronological narrative, involved parties, evidence, and officer conclusions. Flags discrepancies, Brady material, procedural issues, and exculpatory evidence. Use when summarizing police reports, arrest reports, officer narratives, or law enforcement documentation for criminal defense, personal injury, civil rights, or insurance litigation.
Best use case
police-report-summary is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Summarizes police reports and incident documentation into structured, source-attributed legal work product. Extracts incident details, chronological narrative, involved parties, evidence, and officer conclusions. Flags discrepancies, Brady material, procedural issues, and exculpatory evidence. Use when summarizing police reports, arrest reports, officer narratives, or law enforcement documentation for criminal defense, personal injury, civil rights, or insurance litigation.
Teams using police-report-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/police-report-summary/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How police-report-summary Compares
| Feature / Agent | police-report-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?
Summarizes police reports and incident documentation into structured, source-attributed legal work product. Extracts incident details, chronological narrative, involved parties, evidence, and officer conclusions. Flags discrepancies, Brady material, procedural issues, and exculpatory evidence. Use when summarizing police reports, arrest reports, officer narratives, or law enforcement documentation for criminal defense, personal injury, civil rights, or insurance litigation.
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
# Police Report Summary Transforms police reports into structured, source-attributed summaries for rapid case assessment. Covers incident reports, arrest reports, supplemental reports, and officer narratives. ## Quick Start 1. Gather all police report documents and related records (dispatch logs, booking records, evidence logs) 2. Produce the output sections below in order 3. Source-attribute every factual assertion with page number and document name 4. Run the checks in "Pitfalls" before delivering ## Output Structure ### 1. Executive Summary Two to three sentences: incident type, date/location, key parties, outcome (arrest, citation, report only). ### 2. Incident Details | Field | Detail | |---|---| | Report/Case No. | | | Date/Time | | | Location | | | Reporting Officer(s) | Name, badge no. | | Offense/Incident Type | | | Disposition | Arrest / citation / open / cleared | ### 3. Involved Parties Per person: | Field | Detail | |---|---| | Name / DOB | | | Role | Suspect / victim / witness / reporting party | | Contact Info | As documented | | Injuries | If any | | Statements | Key quotes with page refs | ### 4. Chronological Narrative - Reconstruct timeline from all reports, attributed by source and page - Use exact timestamps where available - Distinguish: officer observations, dispatch records, witness accounts, suspect statements ### 5. Evidence & Observations | Item | Description | Chain of Custody Notes | Page Ref | |---|---|---|---| Include physical evidence, photos/video, and test results. ### 6. Officer Conclusions Summarize officer opinions, probable cause statements, and recommended charges. Label as officer conclusions, not established facts. ### 7. Flags & Issues - **Discrepancies** — contradictions within or between reports - **Missing information** — documentation gaps, unexplained time lapses - **Procedural issues** — Miranda, consent to search, chain of custody, warrant problems - **Brady/exculpatory material** — evidence or statements favoring the defense or contradicting the prosecution's theory ## Pitfalls - **Source-attribute everything** — page numbers and document names for every assertion - **Preserve exact quotes** when language is legally significant - **Fact vs. opinion** — clearly separate officer observations, officer conclusions, and third-party accounts - **Cross-reference** multiple reports to surface variations and contradictions - **Include all identifiers** — badge numbers, report numbers, case numbers, CAD numbers - **Do not editorialize** — flag issues without arguing conclusions - **Completeness over brevity** — include all material facts to reduce need to re-review originals --- **Key changes from original:** - **Removed `tags`** — not part of the Agent Skills spec (only `name` and `description` are valid frontmatter fields) - **Tightened description** — still includes what/when trigger guidance, stays under 1024 chars - **Added Quick Start** — 4-step workflow checklist for immediate orientation - **Folded Prerequisites into Quick Start** — step 1 covers document gathering without a separate section - **Condensed output templates** — removed redundant table row examples, trimmed prose around each section - **Renamed "Guidelines" to "Pitfalls"** — aligns with the best-practices body structure (pitfalls/checks) - **Reduced from 85 to ~72 lines** — tighter token footprint while preserving all domain-critical content
Related Skills
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.
reporting-ultrasound-studies
Structures ultrasound interpretation with measurement protocols and ACR guidelines. Use when reading ultrasound exams, documenting sonographic findings, or creating US reports.
reporting-nuclear-medicine-studies
Structures nuclear medicine and PET/CT interpretation with SUV measurement and staging correlation. Use when reading nuclear medicine studies, interpreting PET findings, or documenting radiotracer uptake.
reporting-mri-studies
Structures MRI interpretation with sequence-specific analysis and standardized reporting. Use when reading MRI studies, creating MRI reports, or analyzing multisequence findings.
reporting-ct-scans
Structures CT scan interpretation by body region with standardized measurement and comparison techniques. Use when interpreting CT studies, creating CT reports, or documenting cross-sectional findings.
reporting-chest-radiographs
Structures systematic chest X-ray interpretation with standardized reporting and critical findings communication. Use when reading chest X-rays, creating radiology reports, or documenting CXR findings.
managing-quality-reporting
Structures CMS quality reporting (MIPS, HEDIS, CQMs) with measure specification and data validation. Use when reporting quality measures, managing MIPS submissions, or validating quality data.
managing-adverse-event-reporting-research
Documents research adverse events with causality assessment and regulatory reporting timelines. Use when reporting research AEs, assessing causality, or managing safety reporting.
witness-summary
Generates structured summaries of witness statements for litigation, extracting chronological narratives, key facts, credibility indicators, and evidentiary value. Use when summarizing depositions, declarations, affidavits, or witness testimony during discovery, pre-trial, or trial preparation.
viability-conflict-check-report
Drafts a pre-filing litigation intake memo combining conflict screening, legal/procedural viability, and economic triage for an accept-or-decline decision. Trigger when the user requests matter acceptance review, conflict-check analysis, pre-suit intake triage, referral screening, or conflict-waiver evaluation—signaled by phrases like "new matter evaluation," "decline/accept decision," "conflict check," or "pre-filing assessment."
verdict-judgment-summary
Produces structured post-trial verdict and judgment analysis memoranda for commercial litigation. Triggers when summarizing a jury verdict, bench trial decision, post-trial motion assessment, or appellate viability review. Covers liability determinations, damages breakdowns, critical rulings, and post-trial strategy.
urban-planning-summary
Summarizes legal issues in urban development projects covering zoning, land use disputes, and environmental compliance. Generates structured briefings for municipalities, developers, and legal counsel. Use when reviewing zoning ordinances, land use applications, environmental impact statements, or comprehensive plans before development or planning decisions.