Individual skill

driver-incident-investigation

Investigate a commercial vehicle incident so the record is defensible and the cause is actually found — evidence secured in the first hours, the preventability decision made on stated criteria, and corrective action aimed at the system rather than the driver. Use when asked to investigate a vehicle accident, run a post-accident review, decide whether a collision was preventable, or write an incident report for a fleet. Produces the evidence checklist, the sequence reconstruction, the preventability determination with reasoning, the contributing-factor analysis, and the corrective actions. Not legal advice; involve your insurer and counsel early.

plugins/pm-fleet/skills/driver-incident-investigation/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Driver Incident Investigation

The first four hours decide whether an incident can ever be properly investigated — telematics overwritten, the scene cleared, memories consolidated into a story. This gets the evidence secured first, then separates what happened from who was involved, and makes the preventability call against written criteria rather than instinct, because that decision drives insurance, discipline, and whether anyone learns anything.

## What This Skill Produces

- **The evidence checklist** — what to secure immediately, and what is lost if you wait
- **A sequence reconstruction** — what happened, in order, from evidence rather than recollection
- **The preventability determination** — decided against stated criteria, with the reasoning recorded
- **Contributing-factor analysis** — driver, vehicle, route, scheduling, training, and supervision
- **Corrective actions** — aimed at whichever of those factors actually contributed
- **The notification checklist** — insurer, regulator, and internal reporting, with their deadlines

## Required Inputs
Back to top