Menu

Individual skill

hours-of-service-check

0upvotes

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.

plugins/pm-fleet/skills/hours-of-service-check/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 Hours Compliance Check

Hours violations are almost never a driver deciding to break the rules. They are a run that could not be done legally, a dispatcher who did not check, or a detention delay nobody planned for. This audits the records for what an inspector would find, then goes after the scheduling that produced it — because retraining a driver on a schedule that remains impossible produces the same violation next month.

## What This Skill Produces

- **A violation summary** — by type, severity, driver, and pattern, in the terms an inspector uses
- **Falsification-pattern review** — the signatures that draw scrutiny: unassigned driving, implausible edits, and off-duty time that does not match the vehicle's movement
- **Edit-trail analysis** — who changed what, when, and whether the annotations justify it
- **Scheduling root-cause analysis** — which runs are not legally achievable as planned
- **Actions at both levels** — driver-specific and systemic, kept separate
- **The audit trail** — what was reviewed, by whom, and what was done, which is what a review actually examines

## Required Inputs
Back to top