Crime Incident Report Standardization
Extract & standardize crime incident data into UCR-compliant reports
What You Can Do
Convert raw incident descriptions into standardized administrative crime reports that meet state UCR requirements and federal database specifications. Claude extracts key data elements (offense type, location, victim/suspect details, circumstances), validates them against coding standards, flags missing or inconsistent information, and generates audit documentation showing all standardization decisions. This eliminates manual reformatting, reduces data entry errors, and accelerates report processing while maintaining compliance documentation.
Features
Extracts critical data elements (offense codes, locations, dates, parties involved) from unstructured incident descriptions
Cross-checks extracted data against Uniform Crime Reporting standards to ensure coding accuracy and completeness
Automatically populates standardized report templates with extracted and validated information
Identifies missing required fields, inconsistencies, or ambiguous narratives that need human review
Documents all extraction decisions and standardization actions for compliance and quality assurance
Adapts standardization rules to state-specific UCR requirements and departmental formatting standards
Handles multiple incident reports sequentially with consistent output formatting
Example Output
Input Narrative: "Officer responded to 423 Oak St around 11:30pm. Store owner reported merchandise missing from shelves estimated $2,400 value. No signs of forced entry. Suspect described as male, black jacket, fled scene before arrival."
Generated Standardized Report:
- Offense Code: 23D (Shoplifting)
- Location: 423 Oak Street, Precinct 4
- Date/Time: [Current Date] 23:30 hours
- Property Value: $2,400
- Suspect Description: Male, wearing black jacket, fled on foot
- Entry Method: Unknown/No forced entry observed
- UCR Compliance Status: ✓ Complete (all required fields populated)
- Audit Note: Offense code inferred from merchandise loss + no forced entry; recommend officer clarification on suspect direction of flight
Input Narrative: "Hit and run on Maple Ave near intersection with 5th. Blue sedan, license partial JKL. Victim transported to Metro Hospital. Witness says vehicle heading east."
Generated Standardized Report:
- Offense Code: 26A (Hit and Run - Injury)
- Location: Maple Ave & 5th Street, Precinct 2
- Vehicle Description: Blue sedan, partial plate JKL***
- Victim Status: Transport to Metro Hospital (injury reported)
- Direction of Flight: Eastbound
- UCR Compliance Status: ⚠ Incomplete (victim identity missing, hospital info pending)
- Audit Note: Requires follow-up on victim name/age for UCR demographic field; partial plate flagged for BOLO circulation
What's Included
- SKILL.md instruction file with complete standardization framework:
- UCR coding reference: Standard offense codes and required field mappings
- Report template: Standardized incident report structure (markdown/JSON formats)
- Data extraction checklist: Critical elements to identify in narratives
- Audit trail template: Documentation format for compliance records
Who It's For
- Crime analysts — Administrative professionals standardizing incident reports for state/federal submissions
- Records management specialists — Converting legacy case files into compliant electronic formats
- Police administrative staff — Processing incoming patrol officer narratives into standardized formats
- Compliance officers — Preparing crime statistics submissions and audit documentation
- Multi-precinct supervisors — Harmonizing reporting formats across jurisdictions
Best For
- Processing incoming incident reports with narrative-only submissions from patrol officers
- Converting legacy case files into standardized UCR-compliant electronic formats
- Preparing crime statistics submissions for state databases and federal reporting requirements
- Clearing backlog of unstructured historical reports requiring standardization
- Validating that all critical UCR elements are present before database submission
You might also like
You can rapidly analyze disparate incident intelligence—surveillance observations, suspect history, behavioral indicators, and site conditions—to produce comprehensive risk profiles that guide tactical decision-making. The skill generates operationally prescriptive assessments that clearly identify threat level, required assets, officer safety considerations, and contingency planning, helping you determine whether standard patrol or tactical units should handle apprehension, and ensuring warrant service and containment operations are informed by documented threat justification.
by geemal2004
You can orchestrate recovery operations spanning months or years by coordinating multiple agencies, tracking resource deployment, and assessing evolving community needs. Claude helps you document recovery priorities, identify unmet needs by sector (housing, debris, utilities, mental health), and generate compliance-ready status reports that keep FEMA, state emergency managers, and elected officials informed. This skill bridges the gap between emergency response and sustained recovery by managing complexity across jurisdictions without losing sight of individual survivor needs.
by geemal2004
You can conduct structured fire code violation assessments that transform raw inspection data into enforceable compliance documentation. The skill maps violations to specific code sections, stratifies risk from immediate threats to administrative issues, and generates notice-of-violation orders with clear corrective action timelines and appeal-resistant reasoning chains that hold up under administrative hearings and legal challenge.
by geemal2004
You can create defensible chain-of-custody documentation that proves digital evidence remained unchanged and legally handled from acquisition through court presentation. This skill guides you through systematic logging of every custody transfer, access event, storage condition, and handler—building an unbroken narrative that satisfies legal standards and withstands adversarial scrutiny. By using structured protocols and Claude verification, you eliminate documentation gaps that could render evidence inadmissible.
by geemal2004
You can convert raw DNA laboratory data, mixture interpretations, and statistical findings into structured, defensible forensic reports aligned with SWGDAM guidelines and legal standards. The skill helps you organize complex genetic evidence across multiple data streams—profiles, CODIS matches, population statistics, and mixture resolutions—into coherent case narratives that maintain scientific precision while remaining accessible for expert testimony. You'll reduce report preparation time by 40-60% while improving consistency and legal defensibility across DNA cases.
by geemal2004
You can organize complex trace evidence cases from evidence intake through expert report generation. The framework guides you through meticulous documentation, comparative microscopy protocols, interpretation of transfer mechanisms, statistical significance assessment, and preparation of expert testimony materials. This ensures your findings are scientifically defensible and properly contextualized for criminal proceedings.
by geemal2004
You can organize and analyze complex fire investigation data including physical evidence, witness testimony, environmental conditions, and building systems information to identify fire origin and probable cause. Claude helps you cross-reference evidence against NFPA 921 guidelines, synthesize large documentation volumes, and build defensible timelines—all while you maintain investigator authority and scene expertise. The skill supports both administrative findings and legal proceedings with methodical documentation.
by geemal2004
This skill systematically validates chain-of-custody records for digital forensic evidence against federal, state, and local legal standards. You input your CoC documentation and the skill identifies gaps, inconsistencies, and procedural violations that could compromise evidence admissibility, then generates defensible narratives explaining how evidence remained uncontaminated throughout collection, storage, and analysis.
by geemal2004