driver-fatigue-management

Compute FMCSA and EU HOS compliance flags from real driver duty logs.

1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill driver-fatigue-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: driver-fatigue-management
Source: https://github.com/ashley-eyekyam/hse-leadership-skills/tree/main/skills/driver-fatigue-management
Command: npx skills add https://github.com/ashley-eyekyam/hse-leadership-skills --skill driver-fatigue-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Generic AI produces generic, regulator-rejectable driver fatigue paperwork: vague controls, uncomputed hours-of-service (HOS) claims, no de-identification of sensitive driver medical data, and "stay alert" briefings treated as primary controls instead of schedule/roster redesign.

Core Features & Use Cases

  • Deterministic HOS Compliance: Computes FMCSA 49 CFR 395 and EU 561/2006 compliance flags from real driver duty logs, never narrates pass/fail results, and keeps them strictly separate from the advisory fatigue index.
  • Roster-First Control Ranking: Leads all assessments with schedule/roster redesign and Fatigue Risk Management System (FRMS) built-in rest, flags "stay alert" briefings or in-cab fatigue gadgets as lower-order administrative/engineering backstops, never the headline control.
  • Highest-Tier Data Protection: Automatically pseudonymizes driver names, CDL/license numbers, DOT medical/OSA data, and suppresses small fatigue-event cells to protect sensitive occupational health information.
  • Use Case: Use this for fleet-specific driver fatigue assessments, HOS compliance checks against real duty logs, FRMS design for long-haul, night-trunk, or passenger transport fleets, and transport roster reviews across US, EU, UK, and Indian jurisdictions.

Quick Start

Use the driver-fatigue-management skill to assess your named fleet's driver fatigue compliance by providing the operation details, jurisdiction, and real driver duty log when prompted.

Frequently Asked Questions about driver-fatigue-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check hours of service compliance from driver duty logs?▼

Hours of service compliance is checked by computing deterministic pass/fail compliance flags from real driver duty logs against FMCSA 49 CFR 395 and EU 561/2006 regulations, keeping results separate from advisory fatigue indexes.

What is a Fatigue Risk Management System and how does roster redesign control driver fatigue?▼

A Fatigue Risk Management System (FRMS) controls driver fatigue by leading with schedule and roster redesign, treating stay-alert briefings and in-cab gadgets as lower-order administrative backstops rather than primary controls.

Can I de-identify driver medical and license data in fatigue compliance reports?▼

Driver medical and license data is de-identified by automatically pseudonymizing driver names, CDL numbers, and DOT medical records, while suppressing small fatigue-event cells to protect sensitive occupational health information.

Does this driver fatigue assessment tool support EU, UK, and Indian transport jurisdictions?▼

Driver fatigue assessment supports transport roster reviews across US, EU, UK, and Indian jurisdictions, applying multi-day cycle gap discipline and hierarchy-of-controls-aligned control ranking with named action owners.

Why does generic safety paperwork get rejected by transport regulators?▼

Generic safety paperwork is rejected by regulators because it contains vague controls, uncomputed hours-of-service claims, no de-identification of medical data, and treats stay-alert briefings as primary controls instead of roster redesign.

What do I need to generate an FRMS design for a long-haul fleet?▼

To generate an FRMS design for a long-haul fleet, you need to provide the specific operation details, target jurisdiction, and real driver duty logs to enforce strict multi-day cycle gap discipline and compliant roster redesign.