registry-browser
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 10.0k
- Forks
- 2.0k
01 前言 Front Matter
- 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]
02 资源文件 1
- 参考文档references/registries.yaml474 B
03 SKILL.md 正文
/registry-browser
- Load
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ watched registries. - Use the workflow below.
- Search each registry. Show matches with descriptions.
- Offer to show full SKILL.md for any match.
Purpose
Find skills across the watched registries. Search, preview, decide.
Load context
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → watched registries list.
Workflow
Step 1: Fetch registry indexes
For each watched registry:
- GitHub repos: fetch
skills/directory listing and eachSKILL.mdfrontmatter (name + description). - Marketplace-style registries: fetch the index.
Cache the index locally (references/registry-cache.json) so browsing is fast. Refresh cache if >7 days old or on request.
Step 2: Search
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.
Step 3: Present matches
## Search: "[query]"
**Found [N] skills across [M] registries:**
### [skill-name]
**From:** [registry name]
**Description:** [from frontmatter]
[View full SKILL.md] [Install]
### [skill-name]
[...]
Step 4: Preview
On "view full SKILL.md": fetch and show the whole file. User reads it before deciding to install. No surprises.
Step 5: Add a registry
If the user has a URL to a registry not in the watchlist:
- Fetch it, validate it's a skills repo (has
skills/or.claude-plugin/) - Show what's in it
- Add to
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ watched registries on confirmation
Default registries
- lpm-skills — 14 legal project management skills. Practice-agnostic. Good starting point.
- Space for others to be added as the ecosystem grows.
What this skill does not do
- Install anything. It browses. skill-installer installs.
- Rate or review skills. It shows you the SKILL.md; you judge.
- Search the whole internet. Only watched registries.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
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.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.