Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 14% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 85% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 47% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 21% | 0% |
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → practice profile.The community might have built the thing you're about to build. This skill notices and mentions it — once, briefly, non-annoyingly.
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?"
~/.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.
Given a task description (what the user was just doing), find registry skills that match:
Threshold: Only surface if the match is strong. Weak matches are noise. Better to surface nothing than to annoy.
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."
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.
Per ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → new skill notifications:
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.
Other measured skills in the registry, with their headline benchmark lift.