$ loading_
Compare proposed handbook edits and identify cross-reference and state supplement impacts.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "handbook-updates" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/employment-legal/skills/handbook-updates/SKILL.md 2. Save it as ~/.claude/skills/handbook-updates/SKILL.md 3. Reload skills and tell me it's ready
Please update the PTO policy in the employee handbook to: “employees begin accruing 1.25 days of PTO per month from their start date,” then diff it against the current version, check cross-references, state supplement impacts, and whether it reduces any prior promise.
A diff of old versus new language, impacted handbook cross-references, whether state supplements need updates, and a risk note if the change reduces prior promises.
Add this remote work policy to the appropriate handbook section and check whether it conflicts with or requires updates to existing definitions, referenced policies, or state supplements.
Suggested insertion location, a change diff against current text, a list of sections that need coordinated edits, and a state supplement impact analysis.
Here is the new sick leave language. Compare it against the current handbook, identify every section that references this policy, and explain which state supplements may become obsolete, incorrect, or incomplete.
A sick leave policy diff, a cross-reference review table, and itemized action recommendations for state supplements.
When a team plans to revise a handbook section, it can first diff the new wording against the current version, then check whether related policies, definitions, and cross-references also need updates.
If a core handbook policy changes, this skill can review each state supplement to see whether it remains valid, needs revision, becomes obsolete, or requires a new supplement.
When a revision may reduce a previously promised benefit or entitlement, this skill flags the risk and notes that the change may involve more than just updating the document.
The README describes a skill for reviewing employee handbook updates. It gathers the proposed section change, new language, and reason, then diffs the proposal against the current handbook text. It checks related policies, defined terms, and cross-references, and reviews each state supplement to determine whether it stays valid, needs updating, becomes obsolete, or requires a new supplement. It also flags risk when a change reduces previously promised benefits and specifies a structured output format.
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.
Handbook changes have ripple effects. Change the PTO policy and you've affected the final pay calculation, the leave policy cross-reference, and three state supplements. This skill finds the ripples before they become inconsistencies.
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → handbook location, state supplements list, update cadence.
Read the current handbook section. Show the diff:
- [old language]
+ [new language]
Search the handbook for references to the changed section:
Each cross-reference: does it still make sense after the change? Flag any that break.
For each state supplement in ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md:
Is the change reducing something the old version promised?
If yes: that's a risk. Some states treat handbook policies as contractual. Reducing a benefit may need more than just updating the document — advance notice, consideration, or in some cases it can't be done retroactively.
Flag this. Don't block it — but flag it.
## Handbook Update: [Section name]
### Change
[diff]
### Cross-reference impact
| Section | References changed section | Still accurate? | Fix needed |
|---|---|---|---|
| [name] | [how] | ✅/⚠️ | [what] |
### State supplement impact
| State | Current supplement | After change | Action |
|---|---|---|---|
| [state] | [what it says] | [still valid / obsolete / needs update] | [none / update / new supplement needed] |
### Promise check
[If reducing a benefit: flag + jurisdictional risk note]
### Ready to publish
- [ ] Cross-references updated
- [ ] State supplements updated
- [ ] [If benefit reduction: notice/consideration addressed]
- [ ] Version number and date updated
- [ ] Acknowledgment process (if required)
It is used for employee handbook updates: diffing proposed changes against the current version, finding cross-reference impacts, and assessing whether state supplements need updates. It also flags risk when a change may reduce prior promises.
The documentation shows it first gathers the proposed change, including which section is changing, the new language, and the reason for the change. It also reads the handbook location, state supplement list, and update cadence from configuration.
No. The documentation says that if a change reduces something promised in the old version, it will flag that as a risk but will not block the change. For more detail, see the source repository.
Manage matter workspaces to separate, switch, and archive client contexts.
Safely review and install community skills with explicit user approval.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Temporarily disable or re-enable an installed community skill without deleting files.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Review contracts against playbooks with redlines, deviation flags, and impact analysis.
Compare contract clauses against internal policy requirements and identify gaps.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Assess compliance requirements, approvals, and risks for proposed features or initiatives.
Review contracts, flag risks, and generate a separate redlined DOCX.
Create approval-ready change requests with impact analysis and rollback planning.