Official agent skill

Wage Hour QA

by anthropics in anthropics/claude-for-legal

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…

OfficialApache-2.0Auto-check passed

Install Wage Hour QA

skills CLI
$ npx skills add anthropics/claude-for-legal --skill wage-hour-qa -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal wage-hour-qa --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/employment-legal/skills/wage-hour-qa .claude/skills/wage-hour-qa && rm -rf skills-src

Use ~/.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/

Facts

Skill name
wage-hour-qa
GitHub stars
9.6k
Used in
1 other repo
Token cost
~3.3k tokens
SKILL.md length
1,766 words
Files
1
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 3 steps: Jurisdiction → Research the rule, then state it → The flag
  • The user asks any employment law question
  • SKILL.md covers Matter context, Purpose, Load context and The answer, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wage Hour QA is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. 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".

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.

When your agent uses it

  • The user asks any employment law question
  • Says whats the rule in [state]
  • Do we have to pay overtime for
  • Can we classify this as

Example prompts

  • “s the rule in [state]”
  • “is this exempt”
  • “do we have to pay overtime for”
  • “/wage-hour-qa”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Jurisdiction
  2. Research the rule, then state it
  3. The flag

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. 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

Wage Hour QA loads about 3.3k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,766 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

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 anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,766 words, ~3,321 tokens.

Download SKILL.mdSave it as .claude/skills/wage-hour-qa/SKILL.md (or your agent's skills folder).
name
wage-hour-qa
description
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".
argument-hint
[question]

/wage-hour-qa

  1. Load ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint.
  2. Use the workflow below.
  3. Identify jurisdiction the question is about. If not specified, ask.
  4. Answer per that jurisdiction's rule. Cite. Flag if it's a close call or law is shifting.

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /employment-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/employment-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.


Purpose

"It depends" is true but unhelpful. This skill produces a jurisdiction-specific answer grounded in researched, cited primary sources — and flags when the question is close enough to need human judgment. It does not state rules from memory: wage-and-hour thresholds, exemption criteria, and final-pay timing change frequently and vary meaningfully by state.

Load context

~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint. If the question doesn't specify a jurisdiction, ask — or answer for the state with the most employees and note that.

The answer

Step 1: Jurisdiction

Which state/country is this about? If not stated:

  • If it's about a specific employee: where do they work?
  • If it's a policy question: identify the jurisdictions in the footprint that are most likely to be the most restrictive on the question at hand, then research those.
Step 2: Research the rule, then state it

Research before answering. For the jurisdiction and question, identify the currently operative rule. Cite the controlling primary source (statute, regulation, wage order, or case) with a pinpoint cite. Note the effective date and whether the rule has been recently amended, indexed, or is in litigation. If you are uncertain or cannot verify the current state of the law, say so and flag for attorney verification — do not state a rule you haven't confirmed.

State the rule in one paragraph, tied to the cite. Use your tools (web search, legal research integrations, team reference materials) to verify currency — especially for:

No silent supplement. If a research query to the configured legal research tool (Westlaw, CourtListener, or firm platform) returns few or no results for the jurisdiction-and-question, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [jurisdiction / question]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged [web search — verify] and should be checked against a primary source before relying, or (4) flag the question as unverified and stop here. Which would you like?" A lawyer decides whether to accept lower-confidence sources.

Source attribution. Tag every citation in the answer with where it came from: [Westlaw], [CourtListener], or the MCP tool name for citations retrieved from a legal research connector; [web search — verify] for web-search citations; [model knowledge — verify] for citations recalled from training data; [user provided] for citations the user supplied. Citations tagged verify carry higher fabrication risk and should be checked first. Never strip or collapse the tags.

  • Salary thresholds for any exemption (federal and state — several states index annually and several have tiered thresholds by employer size).
  • Final-pay timing on termination vs. resignation (many states differ).
  • PTO payout requirements (jurisdiction-specific; some require, some leave it to policy, some depend on accrual-plan design).
  • Meal and rest break rules and any penalty-pay consequence.
  • Daily or weekly overtime rules (some states have daily overtime and double-time rules that federal law does not).
  • Classification tests — see the worker-classification skill; the applicable test depends on jurisdiction and purpose.

Common question types you may be asked — for each, the answer is jurisdiction-specific and time-sensitive. Do not state the rule here; route to research:

  • "Is this role exempt?" — Research the applicable federal and state salary thresholds (verify current amounts and any employer-size tiers) and the applicable duties test(s).
  • "Do we have to pay overtime for X?" — Research federal FLSA overtime plus any state-specific overtime rules (daily OT, double-time, alternative workweeks).
  • "Do we have to provide meal/rest breaks?" — Research the applicable state rule and any penalty-pay consequence for missed breaks.
  • "When is final pay due?" — Research the applicable state rule, including whether timing differs for termination vs. resignation and whether waiting-time or late-pay penalties apply.
  • "Do we have to pay out accrued PTO?" — Research the applicable state rule and any carve-out for accrual-cap or use-it-or-lose-it policies.
  • "Can we classify this person as a contractor?" — Route to /employment-legal:worker-classification if the facts are not already clear.
Step 2a: FLSA regular-rate and back-pay calculations

When the question is a back-pay computation, unpaid-OT computation, or any question that turns on the FLSA "regular rate," use this scaffold. Do not answer from bare hourly wage × OT hours; that's the two most common errors this skill exists to catch.

The regular rate is NOT just the hourly wage. Under 29 U.S.C. §207(e), the regular rate is all remuneration for employment EXCEPT the eight statutory exclusions in §207(e)(1)–(8) (e.g., discretionary bonuses, gifts, premium pay, expense reimbursements, profit-sharing plans meeting the DOL regs, stock options meeting §207(e)(8), retirement/insurance contributions). Anything NOT within those eight exclusions is IN.

  1. Non-discretionary bonuses are IN the regular rate. Productivity bonuses, attendance bonuses, commissions, shift differentials, contest awards, and most "bonuses" a reasonable employee would expect as a matter of course are non-discretionary under §207(e)(3) and 29 C.F.R. §778.211. Divide the bonus by the total hours worked in the bonus period to get the per-hour increase to the regular rate. True discretionary bonuses (§207(e)(3)) require both the fact of payment AND the amount to be within the employer's sole discretion, determined at or near the end of the period — narrow category.
  2. The unpaid OT premium is 0.5×, not 1.5× — when straight time was already paid for all hours. If the employee was paid straight time for every hour (including the OT hours) but no premium, they are owed the half-time premium on OT hours, not time-and-a-half: unpaid OT = 0.5 × regular rate × OT hours. 29 C.F.R. §778.110(b). If the employee was NOT paid for the OT hours at all, the owed amount is 1.5× the regular rate on those hours. State which pay posture you're assuming before you compute — it determines 0.5× vs. 1.5× and is the most common error in this computation.
  3. Show your math. Print the formula and the inputs explicitly:
    Regular rate    = (straight-time wages + non-discretionary bonuses + other non-excluded comp) ÷ total hours worked
    OT premium owed = 0.5 × regular rate × OT hours    [if straight time already paid for OT hours]
                    = 1.5 × regular rate × OT hours    [if OT hours were unpaid]
    A number without the formula is not usable by a wage-and-hour lawyer.
  4. Liquidated damages double the back-pay. 29 U.S.C. §216(b). Liquidated damages equal the unpaid back-pay amount unless the employer proves, to the court's satisfaction, that the violation was in good faith and based on reasonable grounds to believe it was not a violation. 29 U.S.C. §260. Default assumption is liquidated damages apply; the employer bears the burden to avoid them.
  5. Statute of limitations is 2 years; 3 for willful. 29 U.S.C. §255(a). State the lookback explicitly and compute both bookends unless the willfulness posture is already established by the user.
  6. State overlay. Many states have longer lookback, higher overtime multipliers (daily OT, double-time), and different regular-rate rules. Check state wage-and-hour law against the jurisdiction gate from Step 1 and flag where state law compounds (higher cap) or replaces (different rate) federal. California, New York, Massachusetts, and Washington are the most frequent overlay hits.
  7. Attach the verify tag to the number. Any back-pay amount produced by this skill carries [verify — consult wage-and-hour counsel before asserting or paying] on the line the number appears. The computation is specialist work; the skill is scaffolding, not opinion.
Show full SKILL.md (481 more words)Show less

If the question is a back-pay calculation and any of these inputs are missing (bonus breakdown, whether straight time was paid for OT hours, willfulness posture, state jurisdiction), ask before computing. A confident wrong number is the worst output this skill can produce.

Step 3: The flag

Is this a close call? Be honest.

  • If the answer is clear on the researched rule: say so. "Exempt — meets each element of the applicable duties test and the current salary threshold."
  • If it's close: say so. "The duties test is borderline — this role could go either way. Recommend classifying as non-exempt to be safe, or getting a formal opinion."
  • If the law is in flux: say so. "This rule has been amended recently — the current version takes effect [date]. Confirm effective date before relying on this answer."
  • If you could not verify currency: say so. Do not guess.

Output format

Conversational. This is a Q&A, not a memo.

Research-connector pre-flight. Before emitting the answer, check whether a legal research connector is reachable for this session — Westlaw, CourtListener, or any firm-configured research MCP. Collect this into the reviewer note per CLAUDE.md ## Outputs: if no connector returns results in Step 2 (or none is configured at run time), record it in the Sources: line of the reviewer note — e.g., not connected — cites from training knowledge; pinpoint cites (volume/page/subsection) carry the highest fabrication risk, spot-check those first. Per-citation [model knowledge — verify] tags remain inline. Do not emit a standalone banner above the output.

Jurisdiction assumption. Answers apply only to the jurisdiction identified. Wage-hour rules, exemption thresholds, and final-pay timing vary materially by state and country, and many rules index or change year over year. If the employee works in another jurisdiction, or the question is answered for the default-footprint state, this answer may not apply as written.

**[Jurisdiction]:** [The researched rule, one paragraph, with pinpoint cite
and currency note.]

[If close call or shifting law: the flag.]

[If the answer differs in other footprint jurisdictions: one line noting that,
and whether the differences are material.]

Verify citations. Any case, statute, regulation, or wage-order cite above was generated with AI assistance. Before relying on a cite, check it against Westlaw, CourtListener, the relevant state agency's site, or your firm's research tool for accuracy, currency, and subsequent history. Fabricated or misquoted citations in filings or formal advice have resulted in sanctions.

Close with the next-steps decision tree

End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

What this skill does not do

  • State the rule from memory — every answer is grounded in a researched, cited primary source verified for currency.
  • Make classification decisions for borderline cases. It states the rule and flags the close call. Human decides.
  • Give a 50-state survey unless asked. Answers for the relevant jurisdiction(s).
  • Track when the answer changes. If thresholds index or law shifts, the answer goes stale. Re-ask for current.

© anthropics, Apache-2.0. 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 employment-legal/skills/wage-hour-qa of anthropics/claude-for-legal.

Open the folder on GitHubat commit 4a6c651

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Wage Hour QA 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.

Wage Hour QA compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wage Hour QA this skillanthropics/claude-for-legal9.6k1 repos~3.3kAutomated safety check: PassApache-2.0
Employment Compliancecbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
Instance Awarenessn8n-io/n8n207k—~1.4kAutomated safety check: PassCustom licence
YC Office Hoursgarrytan/gstack136k—~4.2kAutomated safety check: PassMIT
Office Hoursalirezarezvani/claude-skills28k—~935Automated safety check: PassMIT
Cv Classificationaiming-lab/AutoResearchClaw15k—~304Automated safety check: PassMIT

Similar skills

  • Employment Compliance

    cbrock84/headcount

    Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Backend & APIsAuto-check passed
  • Official

    Load when the request depends on what is already on this instance rather than on what the user just typed: a short or ambiguous opener ("fix it", "carry on", "what should I look at"), a reference to…

    207k GitHub stars~1.4k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • YC Office Hours

    garrytan/gstack

    Runs a YC-style office hours session that pressure-tests a product idea before any code and ends in a design document instead of an implementation.

    136k GitHub stars~4.2k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Office Hours

    alirezarezvani/claude-skills

    /cs:office-hours <topic — YC-style 6-question founder interrogation before any advice.

    28k GitHub stars~935 tokensUpdated 1 mo ago
    Auto-check passed
  • Cv Classification

    aiming-lab/AutoResearchClaw

    Best practices for image classification tasks. An agent skill from aiming-lab/AutoResearchClaw.

    15k GitHub stars~304 tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • LLM API 使用成本优化模式 —— 基于任务复杂度的模型路由、预算跟踪、重试逻辑和提示缓存. An agent skill from affaan-m/ECC.

    277k GitHub starsUsed in 3 repos~1.1k tokens
    AI & LLM EngineeringAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo
  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed
  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed
  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed
  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed
  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about Wage Hour QA

What does Wage Hour QA do?

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…. Wage Hour QA is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. 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.

When should I use Wage Hour QA?

Wage Hour QA fits situations like: the user asks any employment law question; says whats the rule in [state]; do we have to pay overtime for; can we classify this as.

How do I install Wage Hour QA in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill wage-hour-qa -a claude-code`. Or copy the skill folder (employment-legal/skills/wage-hour-qa in anthropics/claude-for-legal) into .claude/skills/wage-hour-qa in your project. Claude Code loads it when a task matches its description.

How do I install Wage Hour QA in Codex?

Run `npx skills add anthropics/claude-for-legal --skill wage-hour-qa -a codex`. Or copy the skill folder (employment-legal/skills/wage-hour-qa in anthropics/claude-for-legal) into .agents/skills/wage-hour-qa in your project. Codex loads it when a task matches its description.

Can I use Wage Hour QA 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 anthropics/claude-for-legal --skill wage-hour-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wage-hour-qa, .gemini/skills/wage-hour-qa, .github/skills/wage-hour-qa and .opencode/skills/wage-hour-qa in your project.

What does Wage Hour QA need to run?

SKILL.md names no scripts, command-line tools or credentials: Wage Hour QA is instructions for the agent only.

Does Wage Hour QA 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 Wage Hour QA 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 Wage Hour QA use?

Wage Hour QA is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wage Hour QA use?

About 3.3k tokens (SKILL.md is roughly 13k 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 Wage Hour QA?

Skills that share tags, products or a category with Wage Hour QA: Employment Compliance (cbrock84/headcount, 2k stars), Instance Awareness (n8n-io/n8n, 207k stars), YC Office Hours (garrytan/gstack, 136k stars) and Office Hours (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wage Hour QA?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,633 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.

Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.