handbook-updates — Claude Code skill: what it does, how to install
This skill diffs a proposed policy change against your current handbook, then shows which sections and state supplements the edit breaks.
npx skills add anthropics/claude-for-legal --skill handbook-updates -a claude-codeWhat handbook-updates does
The skill takes a proposed change, reads the current handbook section and prints the diff as - and + lines. Next it hunts for cross-references: other policies that point at the changed section, defined terms, the state supplements that modify it. Each one comes back marked as still accurate or in need of a fix.
There is a promise check as well. If the edit cuts something the old version granted, the skill raises a flag, because some states treat handbook policies as contractual. A benefit reduction may need advance notice or consideration, and sometimes it cannot be done retroactively.
Everything runs off ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md, which records where the handbook lives and which supplements are in play. With that file missing there is nothing to diff against, so look at it before you run anything. Approving the change, telling employees and collecting acknowledgments stay outside the skill.
What it helps with
- diff a proposed policy tweak against the version in force
- list sections that cite the changed policy and may now be wrong
- check whether a state supplement went obsolete after the edit
- get a warning when a benefit is being cut
- produce a publish checklist with version number and date
Example prompts for the agent
- Update the PTO section of the handbook: unused days now carry over to next year
- What breaks in the handbook if we delete the accrual cap from the leave policy?
- Here's the new remote work policy — insert it into the handbook and flag every section and supplement that needs a fix
How to install handbook-updates
1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill handbook-updates -a claude-code2Manually: put the files in place
~/.claude/skills/handbook-updates/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/handbook-updates/
1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill handbook-updates -a codex2Manually: put the files in place
.agents/skills/handbook-updates/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill handbook-updates -a cursor2Manually: put the files in place
.cursor/skills/handbook-updates/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-for-legal handbook-updates2Manually: put the files in place
.github/skills/handbook-updates/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill handbook-updates -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-for-legal --path employment-legal/skills/handbook-updatesManually: put the files in place
.devin/skills/handbook-updates/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill handbook-updates -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about handbook-updates
How do I install handbook-updates in Claude Code?
Run npx skills add anthropics/claude-for-legal --skill handbook-updates -a claude-code. The skill lands at ~/.claude/skills/handbook-updates/SKILL.md.
What does handbook-updates do?
It diffs a proposed handbook change against the current section, then lists the cross-references and state supplements that the change affects. A separate check flags edits that reduce a benefit employees were already promised.
Does the skill approve or publish handbook changes?
No. HR and legal leadership approve them, and the skill does not communicate changes to employees or track acknowledgments.
Source text
SKILL.md · Apache-2.0
---
name: handbook-updates
description: >
Diff a proposed handbook change against the current version, flag ripple
effects and state supplement impacts. Use when user says "update the
handbook", "add this to the handbook", "handbook change", or has a policy
ready for insertion.
---
# Handbook Updates
## 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
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.
## Load context
`~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md` → handbook location, state supplements list, update cadence.
## Workflow
### Step 1: Get the change
- What section is changing?
- What's the new language?
- Why? (Legal requirement, policy decision, cleanup)
### Step 2: Diff against current
Read the current handbook section. Show the diff:
```diff
- [old language]
+ [new language]
```
### Step 3: Find cross-references
Search the handbook for references to the changed section:
- Other policies that cite this one ("see the PTO policy for accrual rates")
- Defined terms that this section uses or defines
- State supplements that modify this section
Each cross-reference: does it still make sense after the change? Flag any that break.
### Step 4: State supplement impact
For each state supplement in `~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md`:
- Does this supplement modify the section being changed?
- Does the change make the supplement obsolete, wrong, or incomplete?
- Does the change create a need for a *new* supplement in a state that didn't need one before?
### Step 5: Promise check
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.
## Output
```markdown
## 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)
```
## What this skill does not do
- Approve handbook changes. HR/legal leadership does.
- Communicate changes to employees.
- Track acknowledgments.
© anthropics · Apache-2.0 · anthropics/claude-for-legal