Source profileQuality 93/100

zgbrenner/agentcounsel/skills/employment/worker-classification/SKILL.md

Worker Classification

Use when organizing the facts of a proposed worker engagement and structuring an analysis of whether the worker should be classified as an employee or an independent contractor, producing a draft classification analysis memo for attorney review.

Source repository stars
17
Declared platforms
0
Static risk flags
0
Last source update
2026-08-05
Source checked
2026-08-28

Decision brief

What it does: where it fits

Use when organizing the facts of a proposed worker engagement and structuring an analysis of whether the worker should be classified as an employee or an independent contractor, producing a draft classification analysis memo for attorney review.

Best for

  • Produce a structured, attorney-ready classification analysis memo for a proposed worker engagement — one that has not yet started. The skill gathers and organizes the factual inputs that bear on worker classification, i…

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/zgbrenner/agentcounsel --skill "skills/employment/worker-classification"
Safe inspection promptEditorial

Inspect the Agent Skill "Worker Classification" from https://github.com/zgbrenner/agentcounsel/blob/3b2cace3160051027a81a1ec1a41df5667145a9d/skills/employment/worker-classification/SKILL.md at commit 3b2cace3160051027a81a1ec1a41df5667145a9d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Prospective-only gate. Before gathering any facts, confirm that the engagement has not yet started. Ask: "Has the worker already begun performing any work under this arrangement?" If the answer is yes, or if there is any ambiguity, stop. State clearly that this skill covers o…

    Prospective-only gate. Before gathering any facts, confirm that the engagement has not yet started. Ask: "Has the worker already begun performing any work under this arrangement?" If the answer is yes, or if there is an…Confirm inputs. Verify that all required inputs are present: description of the work, control facts, economic facts, arrangement structure, classification purpose(s), and governing jurisdiction. If any input is missing,…Organize and document the facts. Group the confirmed facts into four categories and present them clearly:
  2. 02

    Attorney Verification Checklist

    [ ] The engagement has been confirmed as prospective — no work has begun under the arrangement being analyzed.

    [ ] The engagement has been confirmed as prospective — no work has begun under the arrangement being analyzed.[ ] The governing jurisdiction has been confirmed, including any choice-of-law or multi-jurisdiction exposure.[ ] The correct classification test(s) for each stated legal purpose (tax, wage-and-hour, unemployment, benefits, workers' compensation, etc.) have been identified and verified through current research, not memory.
  3. 03

    Purpose

    Produce a structured, attorney-ready classification analysis memo for a proposed worker engagement — one that has not yet started. The skill gathers and organizes the factual inputs that bear on worker classification, identifies the test or tests that apply in the governing juri…

    Produce a structured, attorney-ready classification analysis memo for a proposed worker engagement — one that has not yet started. The skill gathers and organizes the factual inputs that bear on worker classification, i…
  4. 04

    Use When

    A company or HR professional is planning a new engagement with an individual worker and needs to think through whether the arrangement is supportable as an independent contractor relationship.

    A company or HR professional is planning a new engagement with an individual worker and needs to think through whether the arrangement is supportable as an independent contractor relationship.An attorney needs a structured intake of engagement facts to begin a classification risk assessment before work begins.A user asks "can we bring this person on as a contractor?" or "what factors should we look at before we classify this engagement?"
  5. 05

    Required Inputs

    If any required input is missing, stop and request it before proceeding. Do not fabricate facts, assumed durations, assumed pay structures, or inferred control arrangements.

    Description of the work: what the worker will do, day to day; whether the work is core to the company's business or peripheral; whether the engagement is project-based or indefinite in duration; and the level of special…Control facts: whether the company will set the worker's hours or schedule; whether the work will be performed on company premises; who will direct the method and sequence of work; whether the company will have supervis…Economic facts: how the worker will be paid (flat fee, hourly, milestone, retainer); who will provide tools, equipment, and materials; whether the worker has or will have other clients during the engagement; and whether…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score93/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars17SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
zgbrenner/agentcounsel
Skill path
skills/employment/worker-classification/SKILL.md
Commit
3b2cace3160051027a81a1ec1a41df5667145a9d
License
MIT
Collected
2026-08-28
Default branch
main
View the original SKILL.md

Worker Classification

Purpose

Produce a structured, attorney-ready classification analysis memo for a proposed worker engagement — one that has not yet started. The skill gathers and organizes the factual inputs that bear on worker classification, identifies the test or tests that apply in the governing jurisdiction for the relevant legal purpose, applies those tests to the facts in a structured factor table, and flags gaps between the intended arrangement and what the facts support. It produces draft legal work product for attorney review — not legal advice, not a legal conclusion on the lawfulness of any classification, and not a substitute for employment counsel.

Use When

  • A company or HR professional is planning a new engagement with an individual worker and needs to think through whether the arrangement is supportable as an independent contractor relationship.
  • An attorney needs a structured intake of engagement facts to begin a classification risk assessment before work begins.
  • A user asks "can we bring this person on as a contractor?" or "what factors should we look at before we classify this engagement?"
  • A proposed arrangement involves a staffing agency, vendor SOW, or direct contractor agreement, and classification risk has not yet been assessed.
  • The user needs to compare the intended contract structure against the operational facts before the engagement is executed.

Required Inputs

  • Description of the work: what the worker will do, day to day; whether the work is core to the company's business or peripheral; whether the engagement is project-based or indefinite in duration; and the level of specialization or skill required.
  • Control facts: whether the company will set the worker's hours or schedule; whether the work will be performed on company premises; who will direct the method and sequence of work; whether the company will have supervisory authority over the worker.
  • Economic facts: how the worker will be paid (flat fee, hourly, milestone, retainer); who will provide tools, equipment, and materials; whether the worker has or will have other clients during the engagement; and whether the worker bears any risk of profit or loss on the engagement.
  • Arrangement structure: whether this is a direct independent contractor agreement, a staffing-agency placement, or a vendor SOW; proposed duration; and whether the worker will be physically co-located with employees.
  • Classification purpose(s): the legal purpose(s) for which classification matters (e.g., income tax withholding, wage-and-hour obligations, unemployment insurance, benefits eligibility, workers' compensation coverage). Different purposes may trigger different tests under the governing jurisdiction's law.
  • Jurisdiction: the state, province, or country whose law will govern the engagement. If unknown, flag as [CONFIRM: governing jurisdiction].

If any required input is missing, stop and request it before proceeding. Do not fabricate facts, assumed durations, assumed pay structures, or inferred control arrangements.

Do Not Use When

  • The engagement has already started — retroactive reclassification risk analysis is a distinct, attorney-directed task that this skill does not perform. Stop, and direct the user to employment counsel for a retroactive analysis.
  • The user wants the independent contractor agreement or SOW drafted (use a contract-drafting skill).
  • The user is asking for a jurisdiction-specific legal conclusion on whether a particular classification is lawful — that determination requires attorney review.
  • The user needs back-pay, penalty, or tax-liability estimation for a prior misclassification — those calculations require attorney-directed analysis outside the scope of this skill.
  • The engagement concerns an existing employee being converted to contractor status; conversion analysis may involve additional legal considerations that require attorney judgment from the outset.

Legal Safety Rules

  • Source and citation discipline. Follow core/source-and-citation-discipline.md. Never invent legal authority, citations, quotations, statutes, cases, regulations, filing deadlines, or procedural rules. Label what is a provided source, a user-provided fact, an assumption, a legal inference, or an item requiring attorney verification, and use a citation placeholder such as [Attorney to insert authority] when no source is available.
  • Produce draft legal work product for attorney review only. This is not legal advice.
  • This skill is prospective only. If the engagement has already started, stop immediately and do not proceed. Retroactive reclassification risk analysis is a separate attorney-led matter.
  • Do not assert, from memory, what the applicable classification test is in any jurisdiction. Tests, factors, and any statutory or regulatory carve-outs must be researched and verified by the attorney. Treat all background knowledge about classification standards as [verify jurisdiction] until confirmed by research.
  • Do not invent facts, payment terms, control arrangements, or inferred business relationships not provided by the user.
  • Do not invent or assert citations, statutes, regulations, agency guidance, or case names. Use [citation needed] wherever legal authority would be referenced.
  • Separate facts, assumptions, analysis, and attorney-verification items. Label each category clearly.
  • Identify the governing jurisdiction and the classification purpose(s); if either is unknown, flag with [CONFIRM: ...] and do not proceed past fact-gathering without them.
  • Preserve confidentiality and privilege; do not place client-identifying details into reusable templates.
  • Flag every point of uncertainty rather than resolving it silently. Where a factor could reasonably support either classification, note it as contested and flag for attorney assessment.
  • Do not conclude that a proposed arrangement is legally permissible or impermissible. Provide analysis structure; leave the legal conclusion to the attorney.

Workflow

  1. Prospective-only gate. Before gathering any facts, confirm that the engagement has not yet started. Ask: "Has the worker already begun performing any work under this arrangement?" If the answer is yes, or if there is any ambiguity, stop. State clearly that this skill covers only prospective engagements; direct the user to employment counsel for retroactive reclassification risk analysis. Do not proceed.

  2. Confirm inputs. Verify that all required inputs are present: description of the work, control facts, economic facts, arrangement structure, classification purpose(s), and governing jurisdiction. If any input is missing, stop and request it. Do not infer or fabricate missing facts.

  3. Organize and document the facts. Group the confirmed facts into four categories and present them clearly:

    • The Work: tasks, core vs. peripheral, project vs. indefinite, specialization.
    • Control: hours, location, method direction, supervisory authority.
    • Economics: pay structure, tools, other clients, profit/loss risk, business entity status.
    • The Arrangement: contract form (direct IC, agency, SOW), duration, co-location. Separate each confirmed fact from any assumption. Label assumptions explicitly.
  4. Identify the applicable test(s). Based on the governing jurisdiction and the stated classification purpose(s), identify the type of test or tests that apply — noting, for example, whether the purpose implicates a multi-factor common-law test, an economic-realities test, an ABC-style test, or a hybrid. Mark the applicable test as [verify jurisdiction] and note that the attorney must confirm the correct test, its current elements, and any statutory or regulatory carve-outs before the analysis is relied upon. Do not name specific statutes, agencies, or case law.

  5. Apply the facts to the test in a factor table. For each factor or element of the identified test type, apply the gathered facts and assign a directional signal:

    • Supports Employee: the fact, as stated, points toward employee classification.
    • Supports Contractor: the fact, as stated, points toward independent contractor classification.
    • Contested / Unclear: the fact is ambiguous, contested, or missing. Flag each "Contested / Unclear" entry for attorney review. Where a factor is not yet determinable from the provided facts, note what additional information is needed.
  6. Run a gap analysis. Compare the intended arrangement structure (as described and as the contract is expected to read) against what the operational facts actually reflect. Identify any gaps — facts that, if present at engagement time, would undermine the intended classification — and classify each gap as:

    • High-risk gap: the fact directly contradicts the intended classification under the identified test type.
    • Moderate-risk gap: the fact is ambiguous or creates exposure that the attorney should address.
    • Low / No gap: the fact is consistent with the intended classification. Produce an overall gap-analysis risk signal (High / Moderate / Low) with a brief plain-language explanation. Do not label this signal as a legal conclusion; it is an indicator for attorney review.
  7. Flag escalation factors. Identify and call out any of the following, which require heightened attorney attention:

    • The governing jurisdiction is known or suspected to apply a strict classification test (note as [verify jurisdiction] — do not name the jurisdiction or test).
    • The work described is core to the company's primary business rather than peripheral.
    • The company will exercise supervisory authority over the worker's method or schedule.
    • The proposed engagement duration is long or indefinite rather than project-specific.
    • Any classification factor is outcome-determinative and presently points toward employee.
    • The company or individual has prior audit, settlement, or enforcement history in the classification area ([CONFIRM: any prior classification history]).
    • Multiple classification purposes apply and the tests may yield different results.
  8. List attorney verification items. Produce a numbered list of the specific questions and confirmations the attorney must resolve before the analysis can be relied upon. These should include: the confirmed governing jurisdiction, the confirmed applicable test(s) for each purpose, any contested factors, all gap items, and any escalation flags.

  9. Assemble the draft memo. Combine the outputs of the preceding steps into the structured memo described in Output Format. Label the complete output as: Draft legal work product for attorney review. Not legal advice.

Output Format

Deliver the following sections, clearly labeled:

  1. Engagement Summary — a brief, plain-language description of the proposed arrangement based on the inputs provided.

  2. Fact Record

    • Confirmed Facts — organized into the four categories: The Work / Control / Economics / The Arrangement.
    • Assumptions — explicit list of any facts assumed in the absence of confirmed information, each labeled [CONFIRM: ...].
  3. Applicable Test(s) — identification of the type(s) of classification test that apply for each stated purpose in the governing jurisdiction, marked [verify jurisdiction], with a note that the attorney must confirm the correct test and its current elements before reliance.

  4. Factor Application Table — a table with columns: Factor | Relevant Facts | Signal (Supports Employee / Supports Contractor / Contested) | Notes for Attorney. One row per factor of the identified test type.

  5. Gap Analysis — a comparison of the intended arrangement structure against the operational facts, with each gap rated High / Moderate / Low and an overall risk signal. Include a plain-language explanation. Label this section: Indicator for attorney review — not a legal conclusion.

  6. Escalation Flags — a bulleted list of any escalation factors identified, each explained in one or two sentences.

  7. Attorney Verification Items — a numbered list of the questions and confirmations the attorney must resolve before the analysis is relied upon.

  8. Assumptions — a consolidated list of all assumptions made throughout the memo, each paired with the corresponding [CONFIRM: ...] placeholder.

Use [CONFIRM: ...] wherever any fact, legal requirement, or jurisdictional rule is unverified. Use [VERIFY: ...] for factual matters to be checked. Use [ATTORNEY TO CONFIRM: ...] for points of legal judgment. Use [verify jurisdiction] for any classification standard, test, or authority requiring jurisdictional confirmation. Use [deadline verification required] for any date or timing item. Label the complete output: Draft legal work product for attorney review. Not legal advice.

Optional: Business Stakeholder Summary

When the output will be used to brief a non-lawyer business stakeholder — a product owner, deal lead, people manager, founder, or executive — add a Business Stakeholder Summary as a clearly separated, plainly labeled section, following core/business-stakeholder-communication.md. Produce it only when the user requests it or when the audience is plainly a business decision-maker. It is an addition to the deliverable above — never a replacement for it, and never a substitute for attorney review. It contains:

  • Business Summary — the bottom line in plain language, with unnecessary legal jargon removed and legal risk stated separately from business and commercial risk.
  • Decision Needed — the specific business decision(s) now on the table, stated as concrete choices, each with its owner.
  • Recommended Ask — the legal team's recommended position or course of action, framed as a recommendation for the business to weigh, not a decision made on its behalf.
  • Fallback Position — the minimum acceptable alternative if the Recommended Ask cannot be achieved.
  • Escalation Needed? — whether the matter should be escalated, to whom (senior management, the board, or outside counsel), and why — or a plain statement that no escalation is needed.

Attorney Verification Checklist

  • The engagement has been confirmed as prospective — no work has begun under the arrangement being analyzed.
  • The governing jurisdiction has been confirmed, including any choice-of-law or multi-jurisdiction exposure.
  • The correct classification test(s) for each stated legal purpose (tax, wage-and-hour, unemployment, benefits, workers' compensation, etc.) have been identified and verified through current research, not memory.
  • Any statutory or regulatory carve-outs, safe harbors, or per se categories applicable in the governing jurisdiction have been identified and assessed.
  • All facts in the Fact Record have been confirmed by the client; no assumed facts have been treated as established.
  • Each factor in the Factor Application Table has been assessed under the verified test, not under a generic or assumed test.
  • The gap analysis risk signal has been reviewed in light of the verified test and the client's actual risk tolerance and remediation options.
  • All escalation flags have been reviewed and addressed or accepted with informed client consent.
  • Any prior classification audit, settlement, or enforcement history has been disclosed and incorporated into the analysis.
  • If multiple classification purposes apply, the results under each test have been reconciled and any divergences addressed.
  • The intended contract structure (IC agreement, SOW, agency agreement) has been reviewed to confirm it is consistent with the operational facts and the applicable test.
  • No legal authority, citation, statute, or case name asserted in this memo has been relied upon without independent verification.
  • The client has been advised that this document is draft work product, not legal advice, and that the final classification determination requires attorney sign-off.

Frequently asked questions

What to verify before installation and use

What does the Worker Classification source document cover?

Use when organizing the facts of a proposed worker engagement and structuring an analysis of whether the worker should be classified as an employee or an independent contractor, producing a draft classification analysis memo for attorney review.

How do I install Worker Classification?

The source record exposes this install command: npx skills add https://github.com/zgbrenner/agentcounsel --skill "skills/employment/worker-classification". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10045,960

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 10045,960

coreyhaines31/marketingskills

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

Computed 10025,136

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,385

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.