skill CX Codex official · Anthropic

gaps — Claude Code skill: open gaps tracker

Q: How do I install gaps in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill gaps -a claude-code`. The skill lands at `~/.claude/skills/gaps/SKILL.md`.

Q: Where does gaps get its data?

From `~/.claude/plugins/config/claude-for-legal/regulatory-legal/gap-tracker.yaml`. The full tracker schema and the owner-notification rules sit in the `gap-surfacer` reference skill, which the skill asks you to load before substantive work.

Lists the items that were flagged and are still open, sorts them by age and materiality, and on request closes a gap or records a risk acceptance.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add anthropics/claude-for-legal --skill gaps -a claude-code

Open on GitHub

What gaps does

The skill keeps track of what was flagged and not yet closed. It reads ~/.claude/plugins/config/claude-for-legal/regulatory-legal/gap-tracker.yaml and, with no arguments, prints a report: what is open, how long it has been sitting by age, and how material it is. Handy before a review when you need to know where the holes are.

Two flags write back to the tracker. /gaps --close GAP-ID marks a gap closed and takes a resolution note. /gaps --accept GAP-ID stores the rationale for accepting the risk and who accepted it, and the status becomes risk-accepted.

Tracker schema, status-report format, reminder cadence and the owner-notification rules live in the gap-surfacer reference skill, which the skill asks you to load before substantive work. Owner notifications go out one confirmation per send, no exceptions. That is worth checking before you close a gap and let it notify whoever owns it.

What it helps with

see which flagged items are still open
sort open gaps by age and materiality
close a gap with a note on how it was resolved
record a risk acceptance and who signed off on it
check the tracker before a review

Example prompts for the agent

What gaps are open? /gaps
/gaps --close GAP-ID and add a resolution note
/gaps --accept GAP-ID, record the rationale and who accepted the risk

How to install gaps

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill gaps -a claude-code

2Manually: put the files in place

~/.claude/skills/gaps/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/gaps/

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill gaps -a codex

2Manually: put the files in place

.agents/skills/gaps/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill gaps -a cursor

2Manually: put the files in place

.cursor/skills/gaps/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install anthropics/claude-for-legal gaps

2Manually: put the files in place

.github/skills/gaps/SKILL.md

1Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill gaps -a gemini-cli

2Platform CLI

gemini skills install https://github.com/anthropics/claude-for-legal --path regulatory-legal/skills/gaps

Manually: put the files in place

.devin/skills/gaps/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill gaps -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about gaps

How do I install gaps in Claude Code?

Run npx skills add anthropics/claude-for-legal --skill gaps -a claude-code. The skill lands at ~/.claude/skills/gaps/SKILL.md.

What does the gaps skill do?

It reports flagged items that are still open, by age and materiality. With a flag it either closes a gap with a note or records a risk acceptance.

Where does gaps get its data?

From ~/.claude/plugins/config/claude-for-legal/regulatory-legal/gap-tracker.yaml. The full tracker schema and the owner-notification rules sit in the gap-surfacer reference skill, which the skill asks you to load before substantive work.

Source text

SKILL.md · Apache-2.0

---
name: gaps
description: Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
argument-hint: "[optional: --close GAP-ID | --accept GAP-ID]"
---

# /gaps

1. Read the gap tracker at `~/.claude/plugins/config/claude-for-legal/regulatory-legal/gap-tracker.yaml`.
2. If `--close`: mark gap closed with resolution note.
3. If `--accept`: record the risk-acceptance rationale and acceptor, status → risk-accepted.
4. Otherwise: report open gaps by age and materiality.

> Detailed tracker schema, status-report format, owner-notification logic (per-send confirmation, no exceptions), reminder cadence, the close/risk-accept modes, and the consequential-action gate live in the **gap-surfacer** reference skill — load it before doing substantive work.

compliance-check official anthropics Skill surfaces applicable regulations, required approvals, and risk areas for any action, product feature, or business initiative. Use before launching anything that touches personal data or has cross-border implications. CX Codex +1 3,300installs general-counsel-advisor Alireza Rezvani This skill scans startup contracts, evaluates investor term sheets, and maps regulatory risks before you talk to outside counsel. 461installs contract-review claude-office-skills Scans contracts for legal risks, verifies clause completeness, and outlines negotiation points. Handy when vetting NDAs, service agreements, or employment offers. CX Codex +1 5,400installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. CX Codex +1 3,500installs vendor-check official anthropics Skill checks vendor agreements across CLM, CRM, email, and document storage in one report, flags missing contracts and expiration dates. Use when onboarding a vendor or renewing an agreement. CX Codex +1 2,800installs eu-ai-act-reviewer bencium Reviews user journeys, public content and codebases for provisions of the EU AI Act that may apply. It spots issues; it does not give legal advice. CX Codex +1 762installs

From the same set118

international-expansion Prepares cross-functional expansion plans for international hiring, framing the EOR versus legal entity choice and drafting briefs for outside counsel. CX Codex +1 591installs status Creates case status summaries for clients, supervisors, or courts. Use it when the same case notes need a different format and level of detail. CX Codex +1 590installs investigation-memo Turns an investigation log into a first draft of the privileged investigation memo, and updates that draft when new data lands. CX Codex +1 590installs disable Temporarily disables a hub-installed community skill while keeping its files and configuration. Use it to stop hooks without removing the skill. CX Codex +1 589installs gap-surfacer Keeps a running log of open policy gaps with owners and due dates. A reference skill inside the claude-for-legal plugin. CX Codex +1 588installs portfolio-status Rolls every active matter from _log.yaml into one page: risk bands, upcoming deadlines, reserves, files gone quiet. Made for the three minutes before a call. CX Codex +1 586installs form-generation Deprecated legal form generation skill from claude-for-legal. It acts as a migration redirect pointing to the /draft command. CX Codex +1 585installs expansion-kickoff Starts planning for expansion into a new country by collecting intake, framing EOR versus entity, drafting questions, and creating a tracker. CX Codex +1 585installs