How do I install the Related Skills Surfacer skill?

Run npx skillmds@latest add infometa/related-skills-surfacer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Related Skills Surfacer safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Related Skills Surfacer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Related Skills Surfacer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Related Skills Surfacer?

infometa (@infometa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Related Skills Surfacer by infometa

Name: Related Skills Surfacer
Rating: 4.666666666666667 (3 reviews)
Author: infometa

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.

infometa Updated Sep 9, 2026 228 repo stars

File contents

/related-skills-surfacer

Load ~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.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

~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.md → practice profile, installed skills (don't suggest what's already installed).

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:

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 ~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.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 practice-profile.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.

---name: related-skills-surfacerdescription: 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.--- # /related-skills-surfacer 1. Load `~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.md` → practice profile. 2. Use the workflow below. 3. Check what other plugins have been doing. Match against registry. 4. 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 `~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.md` → practice profile, installed skills (don't suggest what's already installed). ## 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: 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 `~/.codebuddy/plugins/config/legal-workflows/legal-builder-hub/practice-profile.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 practice-profile.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.

Frequently asked questions