$ loading_
Suggests relevant community skills based on your task and recent plugin activity.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "related-skills-surfacer" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-builder-hub/skills/related-skills-surfacer/SKILL.md 2. Save it as ~/.claude/skills/related-skills-surfacer/SKILL.md 3. Reload skills and tell me it's ready
I was just working on a contract review workflow. Are there any related community skills I can look at?
Returns a highly relevant community skill suggestion with its name and a one-line description; if no strong match exists, it stays silent.
Besides my current task, what other related community skills are available in the community?
Filters the current task context and surfaces potentially relevant community skills while avoiding already installed or clearly mismatched ones.
After another plugin finishes a task, check whether there is a related community skill worth reviewing.
Provides a one-time brief suggestion at the end of a task, indicating a related community skill without interrupting work in progress.
After a user finishes a task, this skill checks the community registry for highly relevant existing skills and briefly surfaces one only when the match is strong. It helps people avoid rebuilding something from scratch.
When a user directly asks whether a community skill exists or what else is available, it searches for related skills based on the current task. It focuses on surfacing only options that closely fit the scenario.
It can also act as a lightweight end-of-workflow check for other plugins, surfacing related community skills without interrupting the main task. This fits workflows that want a gentle recommendation step at the end.
The README explains that related-skills-surfacer checks whether a strong community skill match exists for the task a user just completed. It can be called directly or triggered at the end of another plugin via a Stop hook. The docs emphasize strong-match filtering, avoiding already installed skills, surfacing each skill only once, staying silent when nothing relevant is found, and not interrupting work in progress or installing anything itself.
~/.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.
No. The documentation explicitly says it only discovers and mentions related skills and does not install anything.
It does not interrupt the user during a task. It surfaces a brief suggestion after the task ends, and stays silent if there is no strong match.
It can be invoked directly by the user or triggered at the end of another plugin's workflow through a Stop hook. The docs also note that this hook-based wiring is not enabled by default.
Manage matter workspaces to separate, switch, and archive client contexts.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Standardize new matter intake and generate matter files plus a structured log.
Compare proposed handbook edits and identify cross-reference and state supplement impacts.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Create, refine, and evaluate AI skills for better performance and triggering accuracy.
Create, refine, validate, and restructure AgentSkills and SKILL.md files.
Turn a repeated workflow into a reusable skill file from the current session.
Find reusable skills across local and online sources before creating one.
Safely review and install community skills with explicit user approval.
Create or update skills that extend Codex with knowledge, workflows, and tools.