
Crime Incident Report Processor
Transform unstructured crime reports into standardized, quality-checked data
What You Can Do
This skill extracts core incident data from unstructured reports, standardizes free-form text into structured fields, and flags data quality issues before database entry. You'll transform 20-30 minute manual processing into 5-8 minutes per report while reducing data entry errors by 60-80%, enabling accurate crime trend analysis and statistical reporting.
Features
automatically pulls date, time, location, offense type, and victim/suspect details from narrative text
converts officer descriptions into consistent, structured field entries using taxonomy alignment
identifies missing required fields, inconsistencies, and data gaps before submission
validates against UCR, NIBRS, and local offense classification codes
creates supervisor-ready case summaries from raw dispatch and field notes
handles multiple reports simultaneously for high-volume intake scenarios
ensures uniform formatting across precincts and reporting units
Example Output
Input: Unstructured officer narrative: "Responded to 245 Main St around 11:30pm. Victim states unknown suspect entered through rear window and took laptop and cash. No injuries. Suspect fled scene before arrival. Witness saw red sedan leave."
Output:
INCIDENT SUMMARY
Report Status: Ready for Review
Incident Number: [AUTO-GENERATED]
Date/Time: [Date] 23:30 hours
Location: 245 Main Street, [District]
Offense Type: Burglary - Residential (UCR: 220)
Victim: [Name], Age: [Pending]
Suspect: Unknown, vehicle: Red sedan
Property Loss: Laptop (est. $800), Cash (est. $200)
Data Quality: 2 ALERTS - Victim age missing, Suspect description incomplete
Narrative: [Standardized summary for database]
Recommended Action: Request supplemental victim statement for complete demographics
What's Included
- SKILL.md instruction file with processor configuration and quality standards:
- Incident Data Extraction Template: structured form mapping for all required fields
- UCR/NIBRS Classification Checklist: quick-reference guide for offense categorization
- Quality Assurance Rubric: data completeness standards and flagging criteria
- Batch Processing Workflow: step-by-step guide for multi-report submissions
Who It's For
- Crime analysts processing intake reports and preparing data for statistical analysis
- Police administrative staff managing database entry workflows
- Precinct supervisors standardizing reporting across units
- CompStat coordinators preparing incident data for performance metrics
- Grant writers and researchers compiling crime statistics for reports
Best For
- Converting raw police narrative reports into standardized database format
- Batch processing 5+ incident reports for consistency and speed
- Quality auditing existing reports for missing or inconsistent data
- Extracting incident summaries for executive briefings and crime mapping
- Training new analysts on standardized reporting and classification protocols







