CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-trucking-compliance

Automates FMCSA compliance, DQ files, IFTA filings, and audit readiness for small US motor carriers. Use when: Build audit-ready DQ files for new and existing drivers; Calculate per-jurisdiction taxable gallons for IFTA quarterly filings; Manage DOT drug and alcohol program documentation and random testing rates.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-trucking-compliance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as a product landing page rather than an operational skill: it markets capabilities, lists use cases, and answers sales FAQs, but never instructs Claude how to build a DQ file, calculate IFTA gallons, or prepare an audit checklist. Combined with un-dated time-sensitive claims and a large fraction of marketing padding, it provides little executable value. Its one strength is clear section organization.

Suggestions

Replace the marketing sections ('Why this beats prompting it yourself', the six-question FAQ, and the paid-catalog links) with operational content: the actual DQ file checklist, an IFTA per-jurisdiction calculation procedure, and a new-entrant audit readiness checklist.

Add explicit multi-step workflows with validation checkpoints — e.g., for DQ onboarding: collect documents, run Clearinghouse query, verify Medical Examiner on the National Registry, then a final completeness check against 49 CFR 391.51 before declaring the file audit-ready.

Move the time-sensitive specifics ('verified June 2026 mandates', 'the 50 percent random drug testing rate') into a clearly labeled regulation-reference section so rates and dates can be updated without bloating the main instructions.

DimensionReasoningScore

Conciseness

The body pads heavily with non-instructional marketing: a six-entry '## Questions' FAQ, a 'Why this beats prompting it yourself' pitch, and closing product-catalog links — none of which teach Claude anything operational. It also embeds time-sensitive specifics ('verified June 2026 mandates', 'the 50 percent random drug testing rate') outside any deprecated/old-patterns section, which the guidelines say penalizes conciseness; this matches anchor 2's 'several unnecessary explanations or padded sections' rather than anchor 3's mostly-efficient content.

2 / 5

Actionability

There is no executable guidance — no commands, templates, checklists, or step-by-step procedures — yet the Example section does convey minimal concrete hints ('Receive a verified negative DOT drug test. 2. Run a full Clearinghouse query. 3. Verify the Medical Examiner is on the National Registry'). That places it at anchor 2 ('high-level hints but missing the specific steps to execute'), above anchor 1's purely abstract description and well below anchor 4's executable guidance.

2 / 5

Workflow Clarity

No instructional sequence exists; the only numbered steps appear inside a sample response rather than as steps to follow, and there are no validation checkpoints for compliance-critical batch work (DQ file assembly, IFTA filings). This matches anchor 2 ('rough sequence present but many gaps; steps poorly defined; validation absent') — the Example's ordered list keeps it above anchor 1's incoherence, but the feedback-loop cap prevents anything higher.

2 / 5

Progressive Disclosure

Sections are clearly headed and navigable (problem, what it does, use cases, limitations, example), and no bundle files exist — the body itself states 'Scripts, extension source, and templates from the original package are not in this folder', so there is nothing to reference. However, the inlined FAQ marketing content adds navigational noise, and the detailed material (DQ checklist, IFTA calculation procedure) is simply absent rather than split out, fitting anchor 3 ('some structure but could be better organized') rather than anchor 4's well-placed content.

3 / 5

Total

9

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and covers both what the skill does and when to use it, with concrete regulatory actions and a clear niche that minimizes conflict risk. Its main weakness is a 'Use when' clause phrased as imperative tasks rather than natural user trigger situations, plus a few missing colloquial synonyms (trucking, fuel tax, DOT audit, Clearinghouse). Overall a solid, above-midpoint description.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Build audit-ready DQ files for new and existing drivers', 'Calculate per-jurisdiction taxable gallons for IFTA quarterly filings', 'Manage DOT drug and alcohol program documentation') but 'Automates FMCSA compliance' and 'audit readiness' remain umbrella terms, leaving minor coverage gaps (e.g., expiration tracking from the body is absent). It exceeds anchor 3 (only 1-2 concrete actions) but does not reach anchor 5's comprehensiveness.

4 / 5

Completeness

Both parts are explicit: what ('Automates FMCSA compliance, DQ files, IFTA filings, and audit readiness for small US motor carriers') and a 'Use when:' clause listing three tasks. The when-clause uses imperative task phrases ('Build...', 'Calculate...', 'Manage...') rather than natural user situations, so it fits anchor 4 ('when' could be more explicit or specific) instead of anchor 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

Strong domain keywords are present (FMCSA, DQ files, IFTA filings, DOT drug and alcohol, motor carriers, quarterly filings), matching anchor 4's 'good keyword coverage; a few natural terms missing'. Common user phrasings like 'trucking', 'fuel tax', 'DOT audit', 'driver qualification file', or 'Clearinghouse' are absent, so it falls short of anchor 5's synonym-complete coverage.

4 / 5

Distinctiveness Conflict Risk

'FMCSA compliance, DQ files, IFTA filings, and audit readiness for small US motor carriers' carves out a clear niche with distinct regulatory triggers, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk'). Virtually no other generic skill would fire on these terms, so anchor 4's 'minor overlap risk' understates the fit.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-trucking-compliance/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.