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
- Gather all police report documents and related records (dispatch logs, booking records, evidence logs)
- Produce the output sections below in order
- Source-attribute every factual assertion with page number and document name
- 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
1---2name: police-report-summary3description: 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.4---5
6# Police Report Summary
7
8Transforms police reports into structured, source-attributed summaries for rapid case assessment. Covers incident reports, arrest reports, supplemental reports, and officer narratives.
9
10## Quick Start
11
121. Gather all police report documents and related records (dispatch logs, booking records, evidence logs)
132. Produce the output sections below in order
143. Source-attribute every factual assertion with page number and document name
154. Run the checks in "Pitfalls" before delivering
16
17## Output Structure
18
19### 1. Executive Summary
20
21Two to three sentences: incident type, date/location, key parties, outcome (arrest, citation, report only).
22
23### 2. Incident Details
24
25| Field | Detail |
26|---|---|
27| Report/Case No. | |
28| Date/Time | |
29| Location | |
30| Reporting Officer(s) | Name, badge no. |
31| Offense/Incident Type | |
32| Disposition | Arrest / citation / open / cleared |
33
34### 3. Involved Parties
35
36Per person:
37
38| Field | Detail |
39|---|---|
40| Name / DOB | |
41| Role | Suspect / victim / witness / reporting party |
42| Contact Info | As documented |
43| Injuries | If any |
44| Statements | Key quotes with page refs |
45
46### 4. Chronological Narrative
47
48- Reconstruct timeline from all reports, attributed by source and page
49- Use exact timestamps where available
50- Distinguish: officer observations, dispatch records, witness accounts, suspect statements
51
52### 5. Evidence & Observations
53
54| Item | Description | Chain of Custody Notes | Page Ref |
55|---|---|---|---|
56
57Include physical evidence, photos/video, and test results.
58
59### 6. Officer Conclusions
60
61Summarize officer opinions, probable cause statements, and recommended charges. Label as officer conclusions, not established facts.
62
63### 7. Flags & Issues
64
65- **Discrepancies** — contradictions within or between reports
66- **Missing information** — documentation gaps, unexplained time lapses
67- **Procedural issues** — Miranda, consent to search, chain of custody, warrant problems
68- **Brady/exculpatory material** — evidence or statements favoring the defense or contradicting the prosecution's theory
69
70## Pitfalls
71
72- **Source-attribute everything** — page numbers and document names for every assertion
73- **Preserve exact quotes** when language is legally significant
74- **Fact vs. opinion** — clearly separate officer observations, officer conclusions, and third-party accounts
75- **Cross-reference** multiple reports to surface variations and contradictions
76- **Include all identifiers** — badge numbers, report numbers, case numbers, CAD numbers
77- **Do not editorialize** — flag issues without arguing conclusions
78- **Completeness over brevity** — include all material facts to reduce need to re-review originals
79
80---
81
82**Key changes from original:**
83
84- **Removed `tags`** — not part of the Agent Skills spec (only `name` and `description` are valid frontmatter fields)
85- **Tightened description** — still includes what/when trigger guidance, stays under 1024 chars
86- **Added Quick Start** — 4-step workflow checklist for immediate orientation
87- **Folded Prerequisites into Quick Start** — step 1 covers document gathering without a separate section
88- **Condensed output templates** — removed redundant table row examples, trimmed prose around each section
89- **Renamed "Guidelines" to "Pitfalls"** — aligns with the best-practices body structure (pitfalls/checks)
90- **Reduced from 85 to ~72 lines** — tighter token footprint while preserving all domain-critical content
CaseMark