Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    fmcsa eld hos auditor

    1

    Audit commercial driver ELD logs for FMCSA Hours of Service (HOS) violations using deterministic Python scripts.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    fmcsa eld hos auditor

    fmcsa eld hos auditor

    Example session with this skill installed

    Audit the driver logs in data/driver_logs_july_12.json and check for any 11-hour driving or 14-hour window violations.

    • Read your context and instructions
    • Compiled the fmcsa eld hos

    I have audited the duty status logs for driver D-304. The analysis was performed using the deterministic HOS engine to check against 49 CFR Part 395 regulations.

    HOS Audit Results: Driver D-304

    MetricValueLimitStatus
    Driving Time11.5h11.0hVIOLATION
    Duty Window13.5h14.0hCOMPLIANT
    Driving Since Break6.0h8.0hCOMPLIANT
    10-Hour Resets1N/ADETECTED
    Total On-Duty12.25hN/AINFO

    Violation Details

    11-Hour Rule: Driver exceeded the maximum driving limit by 0.5 hours. The violation occurred during the final segment starting at 16:30.

    • 30-Minute Break: Compliant. Driver took a 30-minute OFF status segment after 6.0 hours of driving.

    Next steps

    1. Review the log annotations for "Adverse Driving Conditions" which may justify the extra 30 minutes of driving.
    2. Export this audit summary to the driver safety file for the current period.
    3. Schedule a coaching session to review the 11-hour daily driving limit with the driver.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual auditing of commercial motor vehicle logs for HOS compliance is slow and prone to calculation errors. This skill automates the detection of federal violations by parsing driver duty status logs against 49 CFR Part 395 standards.

    What it does

    • 11-Hour limit check verifies drivers do not exceed the maximum allowable driving time within a single duty period.
    • 14-Hour window audit monitors the consecutive elapsed on-duty window starting from the end of a 10-hour reset.
    • Break enforcement identifies missing or late 30-minute mandatory rest breaks after 8 cumulative hours of driving.
    • Reset detection validates 10-hour consecutive off-duty or sleeper-berth periods required to restart the duty clock.
    • Status parsing handles standard ELD transitions including Off Duty, Sleeper Berth, Driving, and On Duty Not Driving.

    How it works

    1. Log Ingestion reads ELD data from CSV or JSON files containing driver IDs, timestamps, and status codes.
    2. Audit Execution runs the deterministic Python audit engine to process the duty status timeline.
    3. Violation Analysis captures peak clock values and flags specific regulatory breaches.
    4. Report Generation outputs a structured summary of compliance status and total hours logged.

    Frameworks & tools

    Uses Python 3.9+ for deterministic calculations. Compatible with standard ELD data formats (CSV/JSON) following FMCSA logging conventions.

    Why this beats prompting it yourself

    LLMs struggle with the precise arithmetic required for cumulative time windows and consecutive reset periods. This skill uses a local script to ensure 100% deterministic compliance checks that match DOT statutory requirements.

    Use cases

    • Audit driver logs for 11-hour driving or 14-hour window violations.
    • Verify mandatory 30-minute rest breaks were taken as required.
    • Confirm 10-hour resets were fully completed before a new shift started.
    • Batch process fleet-wide ELD data for safety compliance reporting.

    Known Limitations

    Supports property-carrying regulations only. Does not handle passenger-carrying limits or complex split sleeper berth (8/2 or 7/3) exceptions.

    Limited to property-carrying 49 CFR Part 395 regulations. No support for passenger-carrying limits or complex split sleeper berth exceptions. Requires logs in CSV or JSON format.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    Unlike LLM-based tools that can make calculation errors, this skill uses a deterministic Python engine to ensure 100% accuracy in time tracking, which is critical for DOT legal compliance.

    The skill is optimized for standard CSV or JSON files that follow FMCSA logging conventions, including timestamps, driver IDs, and duty status codes (OFF, SB, D, ON).

    It currently supports federal property-carrying regulations (49 CFR Part 395); please note that passenger-carrying rules and complex split sleeper berth exceptions are not currently supported.

    You will receive the deterministic Python audit engine, documentation on data schema requirements, and an integration guide for connecting the skill to your existing AI agent or workflow.

    The skill is designed as a standalone Python-based module (3.9+) that can be easily integrated into any AI agent framework or automation platform that supports script execution.

    Yes, the engine is designed for high-performance batch processing, allowing you to audit logs for an entire fleet simultaneously for safety compliance reporting.