Audit driver hours records for the violations that actually get cited — the falsification patterns, the edit trails, and the scheduling that makes compliance impossible — and fix the causes rather than the logs. Use when asked to audit hours of service, review driver logs, check tachograph or ELD records, prepare for an hours compliance review, or reduce hours violations. Produces the violation summary by type and severity, the falsification-pattern review, the scheduling root-cause analysis, the driver-level and systemic actions, and the audit trail. Rules and limits are jurisdiction-specific and must be verified against current regulation.
“Audit our driver logs for the last quarter”“We keep getting hours violations on the same lane — why?”“Prepare for an hours of service compliance review”“What falsification patterns should I look for in ELD data?”“Are our scheduled runs actually legal?”
What to give it
▸The records — ELD, tachograph, or log data for the period, with edit history
▸The period and scope — how far back, which drivers, and what prompted the audit
▸The schedules — planned runs, distances, and delivery windows for the same period
▸Known disruptions — detention, breakdowns, weather, and traffic events
▸Your regulatory framework — the specific rules, limits, and exemptions that apply where you operate
✅ 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.
✓The applicable ruleset is identified and verified, including exemptions
✓Mechanical limit checks were run before pattern analysis
✓Falsification indicators were reviewed, not just limit breaches
✓The edit trail was examined for unexplained non-driver changes
✓Violations were mapped to runs to expose lane-level causes
✓Schedule achievability was tested against real driving and break time
✓Driver-level and systemic actions are recorded separately
⚠️ What it refuses to do
**Auditing against the wrong ruleset.** Everything downstream is invalid.
**Counting violations without patterns.** Misses the falsification signals that escalate an audit.
**Ignoring unassigned driving time.** One of the first things an inspector looks at.
**Coaching drivers on impossible schedules.** The violation recurs because the cause was never touched.
**Editing logs to clear findings.** Turns a compliance problem into a serious 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