related-skills-surfacer
Suggest community skills based on recent activity in other plugins. Checks whether the community has built something relevant to a task and mentions it once, non-intrusively. Use when the user says "is there a community skill for this", "what else is out there", or asks for skill recommendations; also runs passively as part of other plugins' workflows.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 10.0k
- Forks
- 2.0k
01 前言 Front Matter
- name
- related-skills-surfacer
- description
- Suggest community skills based on recent activity in other plugins. Checks whether the community has built something relevant to a task and mentions it once, non-intrusively. Use when the user says "is there a community skill for this", "what else is out there", or asks for skill recommendations; also runs passively as part of other plugins' workflows.
03 SKILL.md 正文
/related-skills-surfacer
- Load
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md→ practice profile. - Use the workflow below.
- Check what other plugins have been doing. Match against registry.
- Suggest: "You've been doing X — community has a skill for Y that's related."
Purpose
The community might have built the thing you're about to build. This skill notices and mentions it — once, briefly, non-annoyingly.
How it runs
This skill surfaces related community skills after a task. It can be invoked directly by the user ("what else is out there for X?") or wired into other plugins via a Stop hook — the hook-based pattern requires each sibling plugin to declare a Stop hook that calls this skill, which is not wired by default. Without the hook wiring, invoke it directly.
Other plugins can include a light check at the end of a task:
"The legal-builder-hub found a community skill that might help with this kind of thing: [name] — [one-line]. Want to take a look?"
Load context
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → practice profile, installed skills (don't suggest what's already installed).
Registry cache from registry-browser.
The match
Given a task description (what the user was just doing), find registry skills that match:
- Keyword overlap between the task and skill descriptions
- Practice profile fit (don't suggest litigation skills to a transactional lawyer)
- Not already installed
Threshold: Only surface if the match is strong. Weak matches are noise. Better to surface nothing than to annoy.
Output
If strong match:
💡 The community has a skill for this: [name] from [registry] — "[description]".
/legal-builder-hub:skill-installer [name]to try it.
If no strong match: silent. No output. Don't announce "I found nothing."
Frequency limit
Don't surface the same skill twice. If the user didn't install it the first time, they saw it and decided no. Track dismissals in references/surfaced.json.
User control
Per ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → new skill notifications:
- All: Surface any match
- Matching practice profile: Filter by profile (default)
- None: This skill is off
Close with the next-steps decision tree
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.
What this skill does not do
- Install anything.
- Interrupt a task in progress. Surfacing happens at the end of a task, not in the middle.
- Nag. One mention per skill, ever.
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.