incident-report-summary

Generates structured, litigation-ready summaries from police reports, crash reports, workplace incident reports, or investigative documents. Extracts parties, narratives, citations, witnesses, contributing factors, and visual documentation into a standardized format. Use when summarizing an incident report for case assessment, discovery planning, or liability evaluation; trigger keywords: police report, accident report, crash report, incident summary, report summary, investigative report.

11 stars

Best use case

incident-report-summary is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Generates structured, litigation-ready summaries from police reports, crash reports, workplace incident reports, or investigative documents. Extracts parties, narratives, citations, witnesses, contributing factors, and visual documentation into a standardized format. Use when summarizing an incident report for case assessment, discovery planning, or liability evaluation; trigger keywords: police report, accident report, crash report, incident summary, report summary, investigative report.

Teams using incident-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

$curl -o ~/.claude/skills/incident-report-summary/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/legal/incident-report-summary/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/incident-report-summary/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How incident-report-summary Compares

Feature / Agentincident-report-summaryStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Generates structured, litigation-ready summaries from police reports, crash reports, workplace incident reports, or investigative documents. Extracts parties, narratives, citations, witnesses, contributing factors, and visual documentation into a standardized format. Use when summarizing an incident report for case assessment, discovery planning, or liability evaluation; trigger keywords: police report, accident report, crash report, incident summary, report summary, investigative report.

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.

Related Guides

SKILL.md Source

# Incident Report Summary

Extracts a structured, self-sufficient summary from a police or incident report so an attorney can assess facts, parties, and issues without the original document.

## Prerequisites

1. Source report (police, crash, workplace, or investigative document).
2. All attachments — supplements, witness forms, diagrams, photos.
3. Matter identifier — case name or number.

## Quick Start

1. Identify report type and adapt extraction fields accordingly (e.g., skip vehicle info for workplace incidents).
2. Extract each section below in order.
3. Flag every gap, contradiction, or ambiguity.
4. Verify every fact traces to specific source language — no inference.

## Output Sections

Produce sections in the order listed.

### 1. Header

| Field | Extract |
|---|---|
| Report/Case Number | Official identifier |
| Incident Date/Time | Include time zone if available |
| Report Filed Date | If different from incident date |
| Location | Full address, intersection, or mile marker |
| Agency | Name, officer/investigator, badge number |
| Report Type | Collision, criminal, workplace, etc. |

### 2. Parties Involved

Per party, extract:

- **Role** — Driver / Passenger / Pedestrian / Victim / Suspect / Reporting Party / Employee
- **Name** — full legal name
- **DOB / Age**
- **Address**, **Contact** (phone, email)
- **ID** — license number + state, or employee ID
- **Vehicle** (if applicable) — year, make, model, color, VIN, plate
- **Insurance** (if applicable) — carrier, policy number
- **Injuries noted** — as described in report

### 3. Narrative Summary

Provide two versions:

- **Complete narrative** — preserve the officer/investigator's full account.
- **Key facts extract** — legally significant facts only:
  - Fault admissions
  - Impairment / recklessness / distraction observations
  - Physical evidence (skid marks, distances, measurements)
  - Injury descriptions
  - Safety equipment use or non-use
  - Environmental conditions

Flag ambiguities, contradictions, and temporal gaps.

### 4. Citations / Charges

| Person Cited | Statute/Code | Description | Issued At Scene? | Court Date | Penalty |
|---|---|---|---|---|---|

### 5. Witnesses

Per witness:

| Field | Detail |
|---|---|
| Name | Full name |
| Contact | Phone, address, email |
| Relationship | Independent or party-related |
| Location at incident | Position and facing direction |
| Statement summary | Key observations in their words |

- Preserve direct quotes verbatim (excited utterances / hearsay exceptions).
- Flag witnesses identified but not interviewed.
- Flag references to unidentified potential witnesses.

### 6. Contributing Factors

| Category | Examples | Evidence Source |
|---|---|---|
| Environmental | Weather, lighting, road surface, visibility | Physical evidence / narrative |
| Human | Speed, inattention, impairment, fatigue | Witness / admission / observation |
| Equipment | Mechanical failure, defects | Inspection / narrative |
| Systemic | Training gaps, hazardous conditions | Report findings |

Flag factors suggesting:
- **Third-party liability** — road design defects, product defects, employer violations
- **Affirmative defenses** — comparative negligence, assumption of risk, intervening cause

### 7. Visual Documentation

Describe each diagram, sketch, or photo:

- **Collision diagrams** — road layout, lanes, traffic controls, vehicle positions (pre/during/post), point of impact, final rest, measurements.
- **Photos** — subject, perspective, visible damage/injuries, evidence markers.
- Note information in visuals absent from the narrative.

### 8. Gaps and Follow-Up

- [ ] Missing party contact information
- [ ] Uninterviewed or unidentified witnesses
- [ ] Narrative contradictions needing deposition clarification
- [ ] Missing supplemental reports referenced but not attached
- [ ] Unclear measurements or diagram elements
- [ ] Pending lab results, toxicology, or reconstruction reports

## Checks

- Every fact must trace to specific source language — no inference or speculation.
- Distinguish officer's direct observations from relayed information.
- Use consistent date (MM/DD/YYYY) and time format throughout.
- Adapt fields to report type — omit inapplicable sections.
- Protect PII not relevant to liability or damages.
- Use [VERIFY] on any uncertain extraction.

Related Skills

writing-operative-reports

11
from CaseMark/skills

Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or recording intraoperative findings.

tracking-incidental-findings

11
from CaseMark/skills

Manages incidental finding follow-up using ACR White Paper recommendations. Use when tracking incidentalomas, scheduling follow-up imaging, or managing unexpected findings.

reporting-ultrasound-studies

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

Documents research adverse events with causality assessment and regulatory reporting timelines. Use when reporting research AEs, assessing causality, or managing safety reporting.

witness-summary

11
from CaseMark/skills

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

11
from CaseMark/skills

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

11
from CaseMark/skills

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.