skill-scout
affaan-m/ecc
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 about to create, fork, or extend a skill to avoid duplication and leverage community work.
- 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 references
- Vet external matches for security, maintenance, and relevance
- Rank candidates by match quality, source, and activity
- Present decision options: use existing, fork/extend, or create fresh
How to install skill-scout
npx skills add null --skill skill-scoutHow to use skill-scout
- 1.Extract the task, trigger conditions, domain, and 3–5 search keywords from the user's request
- 2.Search local installed skills and marketplace sources using find and grep
- 3.Query GitHub repositories and code using gh search with SKILL.md filename filters
- 4.Run 2–3 targeted web searches for external skill mentions
- 5.Read SKILL.md frontmatter and check for security issues, maintenance status, and relevance
- 6.Rank results by exact name match, keyword match, source type, and activity level
- 7.Present a short table with skill name, source, why it matches, and any gaps
- 8.Guide the user to choose: use existing, fork/extend, or create fresh
Use cases
- User asks to create a skill—search first to find existing matches
- User describes a workflow and you're about to suggest a new skill
- User wants to fork or extend an existing skill for a specific use case
- User asks 'is there a skill for X?' and needs a ranked list of options
- Avoiding duplicate effort by discovering community or marketplace solutions
- Coding agents (Claude Code, Cursor) building or recommending skills
- Developers deciding whether to create, adopt, or fork a skill
- Teams managing skill libraries and avoiding duplication
- Anyone onboarding to a skill ecosystem and exploring existing options
skill-scout FAQ
Use it whenever the user says 'create a skill', 'build a skill', 'is there a skill for X?', or describes a workflow where you're about to suggest a new skill. Skip it only if the user explicitly says to create from scratch.
Local installed skills (~/.claude/skills), marketplace sources (~/.claude/plugins/marketplaces), GitHub repositories (via gh search), and general web search.
Read the SKILL.md frontmatter and instructions, look for unexpected shell commands or network calls, check repository maintenance and recent activity, and prefer copying to a local branch for review over editing marketplace originals.
After confirming the search found no relevant skill, present the 'create fresh' option and proceed with the new skill creation workflow.
Cap the final ranked list at 10 results, prioritizing exact name matches, local sources, and maintained repositories over weak web-only mentions.
Full instructions (SKILL.md)
Source of truth, from affaan-m/ecc.
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.mdfrontmatter 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:
- Exact keyword match in the skill name.
- Keyword or synonym match in description.
- Local installed or marketplace source.
- Maintained GitHub source with recent activity.
- Web-only mention.
Cap the final list at 10 results.
Step 6 - Present Decision Options
Give the user a short table:
| Option | Meaning |
|---|---|
| Use existing | Invoke or install a matching skill as-is. |
| Fork or extend | Copy the closest skill and modify it. |
| Create fresh | Build 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.
Related skills
More from affaan-m/ecc and the wider catalog.
skill-stocktake
Audit Claude skills and commands for quality, overlap, and currency using AI judgment.
social-graph-ranker
Weighted graph-ranking engine for discovering warm intro paths and bridge value across X and LinkedIn.
social-publisher
Schedule and publish social media posts across 13 platforms via SocialClaw API.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, and production-grade backend patterns.
springboot-security
Spring Security best practices for authentication, authorization, validation, and secrets management in Java Spring Boot.
springboot-tdd
Test-driven development for Spring Boot with JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo coverage.