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.
“Investigate a collision involving one of our trucks”“Was this accident preventable?”“What evidence do I need to secure after an incident?”“Write a post-accident investigation report”“Our driver had an accident — what do I do first?”
What to give it
▸The incident — date, time, location, vehicle, driver, and what is known so far
▸Available evidence — telematics, dashcam, ELD or tachograph, maintenance records, and photographs
▸The driver's account — taken early, separately, and without leading
▸The context — the schedule that day, hours worked, route, weather, load, and any time pressure
▸Your framework — the company's preventability criteria and reporting obligations in your jurisdiction
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Perishable evidence was secured before interviews
✓The driver's account was taken early, alone, and recorded verbatim
✓The sequence is built from data, with the account used to explain it
✓Preventability cites the written criteria and records the reasoning
✓Systemic factors — scheduling, fatigue, maintenance, training — were examined
✓Corrective actions address the factors actually found
✓Notification deadlines were identified and met
⚠️ What it refuses to do
**Interviewing before preserving footage.** The evidence overwrites while you talk.
**Asking the driver whose fault it was.** Produces a defensive account and contaminates the record.
**A preventability verdict with no recorded reasoning.** Indefensible on challenge.
**Stopping at driver error.** The schedule, the fault report nobody actioned, and the training gap all disappear.
**Retraining as the default corrective action.** It is the cheapest action and rarely the right one.
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp