$ loading_
Review an offer letter and any restrictive covenants — jurisdiction check included. Substantive rules (covenant enforceability, pay-transparency, salary-history limits, exemption criteria) are researched per hire, not stored. Use when the user says "review this offer", "can we use a non-compete here", "check this offer letter", "hiring in [state]", or attaches an offer.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "hiring-review" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/employment-legal/skills/hiring-review/SKILL.md 2. Save it as ~/.claude/skills/hiring-review/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint, hiring review triggers, restrictive covenant policy.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.
Offer letters are mostly boilerplate until they're not. The jurisdiction check and the restrictive-covenant check are where this skill earns its keep. The skill does not state the law — every jurisdiction-specific rule is researched and cited at the time of review.
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint, hiring review triggers, restrictive
covenant policy, offer letter template location.
Prepend the work-product header from ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → ## Outputs (it differs by user role — see ## Who's using this).
Where will this person work? Not where HQ is — where they are.
If remote: their home state/country governs. If hybrid: usually their home state, but check the offer letter's choice-of-law clause (may or may not hold up).
Check the jurisdiction table in ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md for this state/country. If it's
not in the table — new jurisdiction — flag that: "First hire in [state]. The
jurisdiction table doesn't cover this. Research needed before offer goes out."
Exempt or non-exempt? The offer should say, and the role should support it.
| Test | Check |
|---|---|
| Salary basis | Paid a fixed salary regardless of hours? |
| Salary level | Above the applicable federal and state thresholds? |
| Duties test | Does the role actually involve the exempt duties? |
Research before calling exemption. Identify the currently operative salary thresholds (federal and state — several states index annually and several have tiered thresholds by employer size) and the applicable duties test(s) for the role. Cite primary sources. Verify currency.
If the offer says exempt but the role description does not support the exempt duties — flag it. Misclassification is expensive.
If the offer includes a non-compete, customer non-solicit, employee non-solicit, or confidentiality/IP assignment:
Research enforceability before advising. For the employee's jurisdiction, identify the currently operative rules on each restrictive covenant in the offer. Non-compete enforceability in particular has shifted in multiple states in recent years through legislation, agency action, and litigation — do not rely on prior memory of which states permit non-competes. Note:
- The specific type of covenant (non-compete, customer non-solicit, employee non-solicit, confidentiality/trade-secret, IP assignment) — each has its own rules.
- Any salary or income threshold that conditions enforceability.
- Any notice, consideration, or garden-leave requirements.
- Any industry-specific carve-outs (e.g., healthcare, broadcasting).
…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.