ai-inventory
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer,…
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the
$ npx -y skills add anthropics/claude-for-legal --skill registry-browser --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/registry-browserContext preview
The summary Claude sees to decide when to auto-load this skill.
Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the
name: registry-browser description: > Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist. argument-hint: "[search query]"
1. Load `~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md` → watched registries. 2. Use the workflow below. 3. Search each registry. Show matches with descriptions. 4. Offer to show full SKILL.md for any match.
---
Find skills across the watched registries. Search, preview, decide.
`~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md` → watched registries list.
For each watched registry:
Cache the index locally (`references/registry-cache.json`) so browsing is fast. Refresh cache if >7 days old or on request.
Match query against skill names and descriptions. Simple keyword match is fine — these are small enough that fuzzy search is overkill.
Also: browse by category if the registry organizes skills that way.
## Search: "[query]" **Found [N] skills across [M] registries:** ### [skill-name] **From:** [registry name] **Description:** [from frontmatter] [View full SKILL.md] [Install] ### [skill-name] [...]
On "view full SKILL.md": fetch and show the whole file. User reads it before deciding to install. No surprises.
If the user has a URL to a registry not in the watchlist:
1. Fetch it, validate it's a skills repo (has `skills/` or `.claude-plugin/`) 2. Show what's in it 3. Add to `~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md` → watched registries on confirmation
Reference agents, skills, and data connectors for the legal workflows we see most — in-house commercial, privacy, product, corporate, employment, litigation, regulatory, AI governance, IP, and the learning side of the practice (law school clinics and
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer,…
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per…
Run the cold-start interview — learns your AI governance practice and writes…
Guided customization of your AI governance practice profile — change one thing without…
Manage matter workspaces — new, list, switch, close, or detach (practice-level).…
Keep the AI policy current with practice — weekly sweep of saved AIAs, triage results, and…