PluginBench
Skill
Review
Audit score 70

skill-scout

affaan-m/everything-claude-code

Search local, marketplace, GitHub, and web sources before creating a new skill.

What is skill-scout?

Skill Scout helps you find existing skills that match your workflow needs before building from scratch. Use it whenever you're asked to create, build, fork, or find a skill—it searches installed skills, marketplaces, GitHub, and the web, then presents ranked options so you can decide whether to use, fork, or create fresh.

  • Search installed local skills and marketplace sources by keyword
  • Query GitHub repositories and code for matching SKILL.md files
  • Perform targeted web searches for external skill mentions
  • Vet external matches by reviewing SKILL.md, checking for security issues, and assessing maintenance status
  • Rank results by match quality, source type, and recency
  • Present decision options: use existing, fork/extend, or create fresh

How to install skill-scout

npx skills add https://github.com/affaan-m/everything-claude-code --skill skill-scout
Claude Code
Cursor
Windsurf
Cline

How to use skill-scout

  1. 1.Extract the task, trigger conditions, domain, and 3–5 search keywords from the user's request
  2. 2.Search local installed skills and marketplace sources using find and grep commands
  3. 3.Search GitHub using gh search repos and gh search code with concise queries
  4. 4.Perform up to three targeted web searches for external mentions
  5. 5.Read SKILL.md frontmatter and check for security issues, maintenance status, and unexpected commands in any external matches
  6. 6.Rank all candidates by exact name match, description match, source type (local preferred), maintenance status, and recency
  7. 7.Present a short ranked table with skill name, source, why it matches, and any gaps
  8. 8.Guide the user to choose: use existing, fork/extend, or create fresh

Use cases

Good for
  • User asks to create a skill for a specific workflow; search first to avoid duplication
  • User wants to fork an existing skill and customize it for their needs
  • User asks if a skill exists for a particular task or domain
  • You're about to suggest creating a new skill; search to confirm no close match exists
  • User wants to extend or combine capabilities from multiple existing skills
Who it's for
  • Developers building custom skills for Claude Code or Cursor
  • Teams managing skill libraries and avoiding duplicate work
  • Users exploring what skills already exist before investing in new development
  • Anyone inheriting or auditing an existing skill collection

skill-scout FAQ

When should I use Skill Scout?

Use it whenever the user says 'create a skill', 'build a skill', 'make a skill', asks 'is there a skill for X?', describes a workflow you'd suggest a new skill for, or wants to fork an existing skill. Skip it only if the user explicitly says to create from scratch.

How many results should I present?

Cap the final list at 10 results, ranked by match quality. Present a short table with skill name, source, why it matches, and any gaps.

Should I install external skills without review?

No. Always read the SKILL.md frontmatter and instructions first. Look for unexpected shell commands, file writes, network calls, credential handling, or package installs. Check if the repository is maintained before recommending adoption.

What if no close match exists?

After confirming the search found no close match, you can proceed with creating a new skill. Present this as the user's choice after they've seen the search results.

Should I edit marketplace skills in place?

No. Prefer copying a matching skill into a fresh local branch and reviewing the diff before making modifications.

Full instructions (SKILL.md)

Source of truth, from affaan-m/everything-claude-code.


name: skill-scout description: Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow. metadata: origin: community

Skill Scout

Use this skill before creating a new skill. The goal is to avoid duplicating existing community or marketplace work, while still vetting anything external before adoption.

Source: salvaged from stale community PR #1232 by redminwang.

When to Use

  • The user says "create a skill", "build a skill", "make a skill", or "new skill".
  • The user asks "is there a skill for X?" or "does a skill exist that does Y?"
  • The user describes a workflow and you are about to suggest creating a new skill.
  • The user wants to fork or extend an existing skill.

If the user explicitly says to skip search or create from scratch, acknowledge that and proceed with the requested creation workflow.

How It Works

Step 1 - Capture Intent

Extract:

  • The task the skill should perform.
  • The trigger conditions for using it.
  • The domain, tools, frameworks, or data sources involved.
  • Three to five search keywords plus useful synonyms.

Step 2 - Search Local Sources

Search installed and marketplace skill names first. Local sources are preferred because they are already part of the user's environment.

find ~/.claude/skills -maxdepth 2 -name SKILL.md 2>/dev/null | grep -iE "keyword|synonym"
find ~/.claude/plugins/marketplaces -path '*/skills/*/SKILL.md' 2>/dev/null | grep -iE "keyword|synonym"

Then search frontmatter descriptions:

grep -RilE "keyword|synonym" ~/.claude/skills ~/.claude/plugins/marketplaces 2>/dev/null

Step 3 - Search Remote Sources

Use available GitHub and web search tools. Prefer concise queries:

gh search repos "claude code skill keyword" --limit 10 --sort stars
gh search code "name: keyword" --filename SKILL.md --limit 10

For web search, use at most three targeted queries such as:

"claude code skill" keyword
"SKILL.md" keyword
"everything-claude-code" keyword

Step 4 - Vet External Matches

Before recommending any external skill for adoption or forking:

  • Read the SKILL.md frontmatter and instructions.
  • Look for unexpected shell commands, file writes, network calls, credential handling, or package installs.
  • Check whether the repository appears maintained.
  • Prefer copying into a fresh local branch and reviewing the diff over editing marketplace originals.

Step 5 - Rank Results

Rank candidates by:

  1. Exact keyword match in the skill name.
  2. Keyword or synonym match in description.
  3. Local installed or marketplace source.
  4. Maintained GitHub source with recent activity.
  5. Web-only mention.

Cap the final list at 10 results.

Step 6 - Present Decision Options

Give the user a short table:

OptionMeaning
Use existingInvoke or install a matching skill as-is.
Fork or extendCopy the closest skill and modify it.
Create freshBuild a new skill after confirming no close match exists.

Only create a new skill after the user chooses that path or after the search finds no close match.

Examples

Result Table

| # | Skill | Source | Why it matches | Gap |
| --- | --- | --- | --- | --- |
| 1 | article-writing | Local ECC | Drafts articles and guides | Not focused on release notes |
| 2 | content-engine | Local ECC | Multi-format content workflow | Heavier than needed |
| 3 | blog-writer | GitHub | Blog writing skill with recent commits | Needs security review |

User-Facing Summary

I found two close local matches and one external candidate. The closest fit is
`article-writing`; it covers drafting and revision, but it does not include the
release-note checklist you asked for. I can either use it as-is, fork it into a
release-note variant, or create a fresh skill.

Anti-Patterns

  • Do not jump directly to new skill creation when a search is reasonable.
  • Do not install external skills without reading them first.
  • Do not present a long unranked list of weak matches.
  • Do not treat web-only mentions as trusted sources.
  • Do not edit installed marketplace originals in place.

Related

  • search-first - General search-before-building workflow.
  • skill-stocktake - Audit installed skills for health, duplicates, and gaps.
  • agent-sort - Categorize and organize existing agents and skills.