Reg Gap Analysis
Diff a new AI regulation or guidance against your current governance posture, surfaces...
Install
npx skills add anthropics/claude-for-legal --skill reg-gap-analysis -g -a claude-code -y- Repository
- anthropics/claude-for-legal9.9k
- Category
- Engineering
- Updated
- 6d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Diff a new AI regulation or guidance against your current governance posture, surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act", "compliance check against [AI law or guidance]", or pastes regulatory text.
/reg-gap-analysis
- Read
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md. Confirm regulatory footprint and use case registry are populated. - Use the framework below.
- Scope: does this regulation apply? (Jurisdiction, threshold, builder/deployer, sector.) If not, one line and done.
- Extract requirements. Diff against current state in
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md. - Prioritize gaps. Output: remediation plan with must-do / should-do / already compliant / accepted gaps.
- Save as dated markdown doc for the file.
/ai-governance-legal:reg-gap-analysis "EU AI Act high-risk provisions"
Purpose
The EU AI Act goes live. Colorado passes an AI law. The CFPB issues model risk guidance. The FTC publishes an AI enforcement policy. Something moves, and now you need to know what, if anything, you have to change.
This skill diffs the new requirement against your current AI governance posture
(per ~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md, use case registry, vendor positions, impact assessment practices,
and AI policy commitments) and produces a gap list with a remediation plan.
The AI regulatory landscape is moving faster than any other area of law right now. When a regulation is genuinely ambiguous, say so. Don't paper over uncertainty, legal teams need to know when they're on solid ground versus when they're making a judgment call.
Load current state
Read ~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md:
## Regulatory footprint, what already applies## Use case registry, what AI you're actually running, and under what conditions## AI policy commitments, what you've publicly or contractually committed to## Vendor AI governance, what vendor positions are in place## Impact assessment house style, what assessment practices exist
