Prior Art Scout
n1m21n/Infinite
Find publicly documented solutions (peer repos, GitHub, forums) to bugs, platform quirks, dependency gotchas or architectural patterns, respecting the copyleft discussions-only rule.
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…
Install Hours Of Service Check
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hours-of-service-check .claude/skills/hours-of-service-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .claude/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hours-of-service-check .agents/skills/hours-of-service-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .agents/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hours-of-service-check .cursor/skills/hours-of-service-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .cursor/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/hours-of-service-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hours-of-service-check .gemini/skills/hours-of-service-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .gemini/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hours-of-service-check .github/skills/hours-of-service-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .github/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hours-of-service-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hours-of-service-check .opencode/skills/hours-of-service-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hours-of-service-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hours-of-service-check into .opencode/skills/hours-of-service-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hours-of-service-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hours-of-service-check- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 772 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 7 steps: Establish which rules actually apply.… → Run the mechanical checks first. Driving… → Then look for falsification signatures.… → …
- Asked to audit hours of service
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Find the… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hours Of Service Check is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Regulatory compliance and Root cause analysis. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to audit hours of service
- Review driver logs
- Check tachograph
- Prepare for an hours compliance review
Example prompts
- “/hours-of-service-check”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Establish which rules actually apply. Limits, break requirements, and exemptions differ by jurisdiction, vehicle class, and operation…
- Run the mechanical checks first. Driving time, duty time, breaks, and rest periods against the limits. This is the list an inspector…
- Then look for falsification signatures. Unassigned driving time, edits that convert driving to on-duty-not-driving, personal conveyance…
- Read the edit trail. Who made each change, when, and whether the annotation explains it. Unexplained edits by a non-driver are the finding…
- Map violations to runs. If the same lane produces violations across different drivers, the lane is the problem.
- Test whether the schedule is legally achievable. Distance, speed limits, mandatory breaks, and realistic loading and detention time. Many…
- Separate the actions. Driver coaching where the driver chose; scheduling change where the run was impossible. Conflating them fixes neither.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hours Of Service Check loads about 1.6k tokens when it runs. Until then it costs about 168 tokens; SKILL.md has 772 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 772 words, ~1,642 tokens.
Download SKILL.mdSave it as
.claude/skills/hours-of-service-check/SKILL.md (or your agent's skills folder).- name
- hours-of-service-check
- description
- 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.
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
Ask for these if not provided:
- 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
Framework: Find the Violations, Then Find the Schedule That Caused Them
- Establish which rules actually apply. Limits, break requirements, and exemptions differ by jurisdiction, vehicle class, and operation type. Auditing against the wrong ruleset is worse than not auditing.
- Run the mechanical checks first. Driving time, duty time, breaks, and rest periods against the limits. This is the list an inspector generates.
- Then look for falsification signatures. Unassigned driving time, edits that convert driving to on-duty-not-driving, personal conveyance used implausibly, and off-duty periods during which the vehicle moved.
- Read the edit trail. Who made each change, when, and whether the annotation explains it. Unexplained edits by a non-driver are the finding that escalates an audit.
- Map violations to runs. If the same lane produces violations across different drivers, the lane is the problem.
- Test whether the schedule is legally achievable. Distance, speed limits, mandatory breaks, and realistic loading and detention time. Many are not, and that is a management finding.
- Separate the actions. Driver coaching where the driver chose; scheduling change where the run was impossible. Conflating them fixes neither.
Output Format
Show full SKILL.md (350 more words)Show less
Hours compliance audit: [period] · [scope] · [auditor]
Ruleset applied: [jurisdiction, regulation, vehicle class, exemptions relied on] · Verified against: [source, date]
Violation summary
| Type | Count | Drivers affected | Severity | Trend vs last period |
|---|---|---|---|---|
| Driving time exceeded | ||||
| Insufficient break | ||||
| Insufficient daily rest | ||||
| Duty time exceeded | ||||
| Missing/incomplete record |
Falsification indicators
| Indicator | Instances | Drivers | Assessment |
|---|---|---|---|
| Unassigned driving time | |||
| Edits reclassifying driving | |||
| Implausible personal conveyance | |||
| Vehicle movement during off-duty |
Edit trail: [edits by non-drivers: count] · [unannotated edits: count] · [notable examples]
Root cause by run
| Run/lane | Violations | Legally achievable as scheduled? | Why not |
|---|
Actions
- Driver-level: [driver — issue — action — owner — due]
- Systemic: [scheduling/dispatch/detention change — owner — due]
Audit trail: period reviewed [dates] · records examined [n] · reviewed by [name] · date [when] · findings issued to [who]
Hours-of-service rules, limits, break requirements, record-keeping duties and exemptions are set by regulation and differ substantially by jurisdiction and operation type. Verify every limit against the current applicable regulation before relying on any finding, and take specialist advice where enforcement action is possible.
Quality Checks
- 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
Anti-Patterns
- 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.
- No audit trail. An audit you cannot evidence did not happen.
- Treating detention as unavoidable. It is a schedulable, negotiable cost driving real violations.
Example Trigger Phrases
- "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?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/hours-of-service-check of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Hours Of Service Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hours Of Service Check this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Prior Art Scoutn1m21n/Infinite | 271 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| AWS Cloudformationaws/agent-toolkit-for-aws | 2.8k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Mdr 745 Specialistdavila7/claude-code-templates | 33k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Dependency Managementaiskillstore/marketplace | 433 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| PR Compliance Checkaztfmod/terraform-provider-azurecaf | 188 | — | ~362 | Automated safety check: Pass | MIT |
Similar skills
- Official
AWS Cloudformation
aws/agent-toolkit-for-aws
Authors, validates, and troubleshoots AWS CloudFormation templates.
Mdr 745 Specialist
davila7/claude-code-templates
EU MDR 2017/745 regulation specialist and consultant for medical device requirement management.
Dependency Management
aiskillstore/marketplace
Dependency management specialist. An agent skill from aiskillstore/marketplace.
PR Compliance Check
aztfmod/terraform-provider-azurecaf
Validate a pull request against the project's contribution checklist.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Hours Of Service Check
What does Hours Of Service Check do?
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…. Hours Of Service Check is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Hours Of Service Check?
Hours Of Service Check fits situations like: asked to audit hours of service; review driver logs; check tachograph; prepare for an hours compliance review.
How do I install Hours Of Service Check in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a claude-code`. Or copy the skill folder (skills/hours-of-service-check in mohitagw15856/pm-claude-skills) into .claude/skills/hours-of-service-check in your project. Claude Code loads it when a task matches its description.
How do I install Hours Of Service Check in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a codex`. Or copy the skill folder (skills/hours-of-service-check in mohitagw15856/pm-claude-skills) into .agents/skills/hours-of-service-check in your project. Codex loads it when a task matches its description.
Can I use Hours Of Service Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill hours-of-service-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hours-of-service-check, .gemini/skills/hours-of-service-check, .github/skills/hours-of-service-check and .opencode/skills/hours-of-service-check in your project.
What does Hours Of Service Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Hours Of Service Check is instructions for the agent only.
Does Hours Of Service Check access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hours Of Service Check safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hours Of Service Check use?
Hours Of Service Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hours Of Service Check use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hours Of Service Check?
Skills that share tags, products or a category with Hours Of Service Check: Prior Art Scout (n1m21n/Infinite, 271 stars), AWS Cloudformation (aws/agent-toolkit-for-aws, 2.8k stars), Mdr 745 Specialist (davila7/claude-code-templates, 33k stars) and Dependency Management (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hours Of Service Check?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.