/ Directory / Playground / skill-fetch
← All servers ↗ GitHub
● Community girofu ⚡ Instant

skill-fetch

by girofu · girofu/skill-fetch

Search 9 skill registries at once, score results, and install the winner — a package manager-ish UX for Claude Code skills.

skill-fetch is a meta-skill: it queries multiple community registries for agent skills, ranks matches by relevance and quality signals (stars, recency), and handles the git-clone install step. Saves you from manually browsing nine different 'awesome-claude-skills' lists.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

skill-fetch-skill.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use skill-fetch

Find and install a skill for a task you're doing right now

👤 Claude Code users who don't know what skills exist ⏱ ~5 min beginner

When to use: You're about to do X and you suspect someone already built a skill for it.

Flow
  1. Describe what you need
    Use skill-fetch. I need a skill for generating OpenAPI specs from existing code. Search and score the top 5.✓ Copied
    → Ranked list with repo, stars, last commit, one-line summary per result
  2. Inspect the top pick
    Show me the SKILL.md of the top result without installing.✓ Copied
    → Raw SKILL.md content for review

Outcome: A new skill installed, tested, and ready — 5 minutes from 'I need something' to 'I have it'.

Pitfalls
  • Installing a skill without reading SKILL.md first — Always inspect the SKILL.md — skills can include hooks that run arbitrary code

Audit the skills you already have installed

👤 Users with a cluttered ~/.claude/skills/ directory ⏱ ~10 min beginner

When to use: You installed a bunch of skills months ago and don't remember what they do.

Flow
  1. Flag abandoned ones
    Which of these haven't been updated upstream in 6+ months?✓ Copied
    → List of stale skills

Outcome: Knowledge of what's installed, what's active, and what can be removed.

Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

skill-fetch-skill + woodshed-skill

Find candidate skills with skill-fetch, then iterate on improvements with woodshed

Find a skill for X, install it, then use woodshed to test and refine it for my use case.✓ Copied
skill-fetch-skill + filesystem

Batch manage skills directory structure

Archive all skills not used in the last 30 days into ~/.claude/skills-archive/✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
search_registries query, limit Finding skills across multiple sources 9 HTTP requests
inspect_skill repo URL Preview before install 1 HTTP request
install_skill repo URL, local name After inspection, to add the skill locally git clone
list_installed none Auditing what you have local read

Cost & Limits

What this costs to run

API quota
Subject to GitHub API limits (60/h unauthenticated, 5000/h with PAT)
Tokens per call
~500 tokens per search result
Monetary
Free
Tip
Set GITHUB_TOKEN to get 5000 req/h instead of 60.

Security

Permissions, secrets, blast radius

Credential storage: Optional GITHUB_TOKEN for higher rate limits
Data egress: GitHub API and skill registries only

Troubleshooting

Common errors and fixes

Search returns 0 results for a common query

Hitting rate limits. Set GITHUB_TOKEN env var.

Verify: curl -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/rate_limit

Alternatives

skill-fetch vs others

AlternativeWhen to use it insteadTradeoff
Manually browsing awesome-claude-skills listsYou only install a skill once in a blue moonSlow, no scoring, no install automation
claude-skills-vault-skillYou want a curated bundle rather than search-and-pickOpinionated; less flexible

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Browse all topic collections → · See 29 new official additions →