CtrlK
BlogDocsLog inGet started
Tessl Logo

wage-hour-qa

Jurisdiction-aware wage/hour and employment Q&A — classification, overtime, meal/rest breaks, leave, final pay — answered for the specific state/country with the controlling rule researched and cited rather than stated from memory. Use when the user asks any employment law question, or says "what's the rule in [state]", "is this exempt", "do we have to pay overtime for", or "can we classify this as".

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

A substantive, well-sequenced legal Q&A workflow with strong actionability and verification checkpoints, but it is a long single-file body that carries some rhetorical redundancy and does not progressively disclose its detailed FLSA computation material into a separate reference.

Suggestions

Trim rhetorical padding — the "It depends is true but unhelpful" opener and the Purpose section restate value already conveyed by the workflow; cut or compress them.

Consolidate the "Load context" section with Step 1, since both cover jurisdiction identification and footprint loading, removing the redundancy.

Extract the detailed Step 2a FLSA regular-rate scaffold into a one-level-deep reference file (e.g. REFERENCES.md) so SKILL.md stays a lean overview with a clearly signaled pointer.

DimensionReasoningScore

Conciseness

Mostly high-signal specialist guidance (FLSA regular-rate exclusions, half-time vs. time-and-a-half, liquidated damages), but it opens with rhetorical padding ("It depends is true but unhelpful") and the "Load context" section repeats jurisdiction-identification guidance already stated in Step 1, so it could be tightened. Not a 1 because it does not explain concepts Claude already knows; not a 3 because the ~200-line body carries some redundancy and filler.

2 / 3

Actionability

Step 2a gives copy-paste-ready formulas with explicit inputs and a code block, pins specific authorities (29 U.S.C. §207(e), 29 C.F.R. §778.110(b), §216(b), §255(a)), and the verify-tag and "ask before computing" rules are concrete and specific; for an instruction-only Q&A skill this is fully actionable guidance.

3 / 3

Workflow Clarity

A clear sequence (Step 1 jurisdiction → Step 2 research/state → Step 2a FLSA calc → Step 3 flag → output format) with explicit validation checkpoints: verify currency before stating a rule, stop-and-ask on thin research results ("No silent supplement"), and ask before computing when inputs are missing, plus feedback loops for close calls and unverifiable law.

3 / 3

Progressive Disclosure

Sections are clearly headed and there is no deep reference nesting, but the body is a long single file with the entire detailed FLSA regular-rate scaffold inline; that scaffold could be a one-level-deep reference file, and with no bundle files present the skill is effectively monolithic rather than an overview pointing to detail.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A precise, third-person description that names concrete capabilities, supplies natural trigger phrasings, and answers both what and when explicitly. It is clearly distinguishable from adjacent legal skills.

DimensionReasoningScore

Specificity

Names concrete domain actions and enumerates specific topic areas — "classification, overtime, meal/rest breaks, leave, final pay" — and the action of answering with researched, cited rules rather than from memory, matching the multiple-concrete-actions anchor.

3 / 3

Completeness

Explicitly answers what (jurisdiction-aware wage/hour Q&A across named topics, researched and cited) and when (an explicit "Use when..." clause with concrete triggers), satisfying both halves.

3 / 3

Trigger Term Quality

Quotes natural user phrasings — "any employment law question", "what's the rule in [state]", "is this exempt", "do we have to pay overtime for", "can we classify this as" — which a user would genuinely say, giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Clear niche (jurisdiction-specific wage/hour employment Q&A) with distinct triggers; the one adjacent skill (worker-classification) is explicitly routed elsewhere, so it is unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-for-legal
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.