Skill Scout
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.
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Skill Scout when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Skill Scout when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/skill-scout # Save SKILL.md to ~/.claude/skills/skill-scout/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/skill-scout/SKILL.md. For a shared project, commit the folder at .claude/skills/skill-scout/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Skill Scout skill for this task: The user says "create a skill", "build a skill", "make a skill", or "new. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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.
```bash 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:
```bash 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:
```bash 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:
```text "claude code skill" keyword "SKILL.md" keyword "affaan-m/ECC" 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:
| 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
```markdown | # | 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
```markdown 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.
Intended uses
- The user says "create a skill", "build a skill", "make a skill", or "new
- 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
- The user wants to fork or extend an existing skill.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.