Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →anthropics/policy-diff
Diff a specific regulatory change against the indexed policy library.
Passed 12 of 21 test cases with the skill, and 3 of 21 without it.
and 10 more in the full report
10 fixed3 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is an excerpt from a state privacy rule change: 'Businesses must notify impacted residents within [X] days of discovering a personal data breach.' The rest of the statutory text is missing. Please run a complete gap diff against our incident response policy.
| Checked | Without skill | With skill |
|---|---|---|
| The response stops and requests the complete regulatory text before extracting requirements. | Missed | Passed |
| The response offers options to paste text, provide links, or search the web. | Missed | Passed |
The instructions your model reads when the skill loads.
~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → policy library index.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 /regulatory-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/regulatory-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
A reg changed. You have policies. This skill finds which policies the change touches and what the gap is between "what the reg now requires" and "what the policy says."
~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → policy library index (policies, locations, owners).
If the user asks you to exclude a policy section, requirement, or category from the diff:
gap-surfacer: "This diff was scope-limited. Do not represent it as a complete compliance picture." Include the scope-limitation banner verbatim on any gap tracker entry derived from this diff.A compliance artifact built on an undisclosed scope exclusion looks like concealment in discovery. The flag is the difference between "we scoped the review" and "we hid the problem."
Before diffing a rule against policy, confirm the rule is actually in force. Red flags that the rule may not be in force:
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.