Install
$ agentstack add skill-x3allamerican-skills-acc-non-recordable-crash-documentation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Non-Recordable Crash Documentation
Not every crash is DOT-recordable. But you should document all crashes — many implications come from non-recordable events.
What's NOT recordable (per § 390.5)
- Crash with no injuries AND no fatality AND vehicles drove away (no tow-away)
- Crash with property damage only (damage was repaired without towing)
- Crash where driver got out of vehicle, walked around, drove home
What's recordable
- Crash with injury requiring medical treatment off-scene
- Crash with fatality
- Crash with disabling damage requiring tow-away
Why document non-recordable crashes
- Insurance implications: even minor crashes affect insurance rates
- Driver pattern: 3 non-recordable crashes in a year = pattern of behavior to address
- Liability protection: documenting all events shows good faith management
- Subrogation: tracking minor crashes supports later subrogation claims
- Crash Preventability Program: even non-recordable can be filed if patterns matter
What to document
- Date + time + location
- Driver involved
- Vehicle involved
- Other party (if any)
- Police report (if filed)
- Photos
- Witness contact info
- Damage estimates
- Insurance involvement
- Preventability assessment
What NOT to include in DOT accident register
- Non-recordable crashes (they don't go in the official register)
- Mechanical breakdowns
- Driver-only "incidents" (e.g., backing into post in parking lot — but document separately)
How to track separately
- "Incident log" or "near-miss log" — informal carrier records
- Driver coaching log
- Insurance claim history
- Subrogation tracking
Insurance considerations
- Non-recordable crashes still affect commercial truck insurance rates
- Insurance carriers may consider any incident
- Pattern of incidents triggers higher renewal rates
- Compass tracks all incidents for insurance reporting
Compass tracking
- Records BOTH recordable + non-recordable
- DOT-recordable flag for register
- Separate incident log for non-recordable
- Driver coaching pattern detection
- Insurance + subrogation reference
CFR citations
- 49 CFR § 390.5
- Insurance Practice
How Compass surfaces this
Searchable in Compass Ask. Runs against carrier fleet data when invoked from the relevant tracker. Read-only; no actions without explicit user approval.
Built by X3 Compass
The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utmsource=skill&utmmedium=github&utm_campaign=acc-non-recordable-crash-documentation
X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.
This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: x3allamerican
- Source: x3allamerican/skills
- License: Apache-2.0
- Homepage: https://x3fleetsafety.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.