skill-search
Skill38 starsChanged 8 months agoMITView on GitHub
Search for Claude Code skills across multiple sources. user-invocable: false description: Searches for relevant skills across local installation, skills.sh directory, and GitHub. Called by other skills or commands. allowed-tools: [Read, Glob, Grep, Bash, WebSearch] When called with a search query, search these 3 sources and return consolidated results. Mark these as installed: true. Parse the output to extract matching skills. Each line follows the format: Extract from the output: - Skill name and exact owner/repo@skill-name path - Install count (popularity…
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ong6/skillstheir own version, first seen Nov 5, 2026
- kinged007/agent-skill-searchtheir own version, first seen Oct 15, 2026
- AI-ModCon/genesis-skillstheir own version, first seen Sep 24, 2026
- taxueseek/session-diggertheir own version, first seen Jul 17, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- taxueseek/session-digger★ 34same name
- AI-ModCon/genesis-skills★ 30same name
- kinged007/agent-skill-search★ 0same name
- ong6/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- auto-discoverySkill
- skill-installerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Search for Claude Code skills across multiple sources.
- Distinctive: line 11
When called with a search query, search these 3 sources and return consolidated results.
- Very specific: line 22
Search the skills.sh open skill directory using the CLI:
- Distinctive: line 36
IMPORTANT: Always use the exact owner/repo path from the CLI output.
- Distinctive: line 39
Only if Sources 1-2 return fewer than 3 results total:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: skill-search
Search for Claude Code skills across multiple sources.
user-invocable: false description: Searches for relevant skills across local installation, skills.sh directory, and GitHub. Called by other skills or commands. allowed-tools: [Read, Glob, Grep, Bash, WebSearch]
Instructions
When called with a search query, search these 3 sources and return consolidated results.
Source 1: Local Installed Skills
Search already-installed skills:
Glob: ~/.claude/skills/*/SKILL.md
Grep: search for the query keywords in matched filesMark these as installed: true.
Source 2: skills.sh Directory
Search the skills.sh open skill directory using the CLI:
npx skills find {query}Parse the output to extract matching skills. Each line follows the format:
owner/repo@skill-name <N> installs
└ https://skills.sh/owner/repo/skill-nameExtract from the output:
- Skill name and exact owner/repo@skill-name path
- Install count (popularity indicator)
- Install command:
npx skills add -y -g <owner/repo@skill-name>
IMPORTANT: Always use the exact owner/repo path from the CLI output. Do NOT guess or modify the path.
Source 3: GitHub (Fallback)
Only if Sources 1-2 return fewer than 3 results total:
WebSearch: site:github.com "SKILL.md" claude {query}Parse results to extract skill repositories.
Output Format
Return results as a markdown table:
| # | Name | Source | Description | Installed |
| 1 | skill-name | local/skills.sh/github | Short description | Yes/No |
Sort order: local first, then skills.sh, github.
Also return a structured JSON block for programmatic use:
{
"results": [
{
"name": "skill-name",
"source": "local|skills.sh|github",
"description": "...",
"installed": true,
"install_info": {
"type": "skills-add|github-plugin|skill-md|installed",
"url_or_name": "..."
}
}
],
"query": "original query",
"total": 5
}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

