Search Skill

Search and recommend Claude Code Skills from trusted marketplaces based on user requirements.

When to Use

When users describe a need and want to find an existing Skill to solve it.

Examples:

• •"Is there a skill that can auto-generate changelogs?"
• •"Find me a skill for frontend design"
• •"I need a skill that can automate browser actions"

Data Sources (by trust level)

Tier 1 - Official / High Trust (show first)

Tier 2 - Community Curated (secondary)

Tier 3 - Aggregators (use with caution)

Search Process

Step 1: Parse User Intent

Extract from user description:

• •Core functionality keywords (e.g., changelog, browser, frontend)
• •Use case (e.g., development, testing, design)
• •Special requirements (e.g., language support, specific framework)

Step 2: Multi-Source Search

IMPORTANT: Only search these 5 sources. Do NOT search the entire internet.

Search by priority:

1. Search Tier 1 (official/high trust) first
2. If fewer than 5 results, continue to Tier 2
3. If still insufficient, search Tier 3 with strict filtering
4. If still nothing found, tell user honestly - do NOT expand to other sources

Allowed search queries (use site: to restrict):

site:github.com/anthropics/skills {keywords}
site:github.com/ComposioHQ/awesome-claude-skills {keywords}
site:github.com/travisvn/awesome-claude-skills {keywords}
site:skills.sh {keywords}
site:skillsmp.com {keywords}

Search methods:

• •GitHub repos: Use site:github.com/{repo} to restrict search scope
• •skills.sh: WebFetch to scrape search results from skills.sh only
• •skillsmp.com: WebFetch with additional verification

Do NOT:

• •Search the entire web
• •Use broad queries without site: restriction
• •Include results from unknown sources

Step 3: Quality Filtering (Critical)

Must filter out the following:

Security checks:

• •Requests sensitive permissions (e.g., ~/.ssh, env variables)
• •External network requests to unknown domains
• •Contains eval() or dynamic code execution
• •Modifies system files

Step 4: Rank Results

Scoring formula:

Score = Source Weight × 0.4 + Stars Weight × 0.3 + Recency Weight × 0.2 + Relevance × 0.1

Source weights:
- Tier 1: 1.0
- Tier 2: 0.7
- Tier 3: 0.4

Step 5: Format Output

Return Top 5-10 results:

## Found X relevant Skills

### Recommended
1. **[skill-name](github-url)** - Source: anthropics/skills
   - Function: xxx
   - Stars: xxx | Last updated: xxx
   - Install: `/plugin marketplace add xxx`

### Worth considering
2. **[skill-name](github-url)** - Source: ComposioHQ
   ...

### Not recommended (for reference only)
- [skill-name](url) - Reason: low stars / not maintained

Example

User: Is there a skill that helps write commit messages?

Search process:

1. •Extract keywords: commit, message, git
2. •Search Tier 1: Found git-commit-assistant in anthropics/skills
3. •Search Tier 2: Found semantic-commit in ComposioHQ
4. •Filter: Exclude results with stars < 10
5. •Rank: Official sources first

Output:

## Found 3 relevant Skills

### Recommended
1. **git-commit-assistant** - Source: anthropics/skills (official)
   - Function: Generate semantic commit messages
   - Install: `/plugin marketplace add anthropics/claude-code`

2. **semantic-commit** - Source: ComposioHQ
   - Function: Follow conventional commits spec
   - Stars: 890 | Last updated: 2 weeks ago

Important Notes

1. •Never recommend unverified Skills - Better to recommend fewer than to recommend risky ones
2. •Stay cautious with Tier 3 sources - Results from skillsmp.com must be double-checked
3. •If nothing suitable is found - Tell the user honestly, suggest using skill-from-masters to create their own
4. •Security concerns - Clearly inform users of risks, let them decide