$ loading_
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.
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
~/.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.
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
Review an offer letter and any restrictive covenants — jurisdiction check included. Substantive rules (covenant enforceability, pay-transparency, salary-history limits, exemption criteria) are researched per hire, not stored. Use when the user says "review this offer", "can we use a non-compete here", "check this offer letter", "hiring in [state]", or attaches an offer.
Draft an audience-specific summary from the privileged investigation memo — HR, leadership, or outside counsel versions. Use when an investigation memo needs to be communicated to an audience that should not see the full privileged work product.
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
Read VDR documents and extract issues per house categories and materiality thresholds, producing findings in house memo format. Use when user says "review the data room", "extract issues from [folder]", "diligence review", "what's in the VDR", or points at VDR documents.