github-discoverabilitylisted
Install: claude install-skill skill-federation/skill-federation
# GitHub discoverability for Agent Skills
Get a repo or skill **found** by the tools people actually use to discover skills:
automated scrapers, curated lists, and registries. This is a distribution playbook,
not generic SEO — it targets the specific signals the skill ecosystem keys on.
> **Do it honestly.** Real project, real value, one accurate entry per destination.
> Topics must be genuinely relevant; descriptions come from the actual `SKILL.md`.
> Keyword-stuffing topics or spraying low-effort PRs across many lists gets a project
> **removed** from curated lists — it's negative-sum. When a curator declines, that's
> their call; don't re-submit.
## How discovery actually works (three lanes)
1. **Automated scrapers** (SkillsMP/awesomeskills.dev, GitHub `/topics` pages, `gh skill`).
They key on **GitHub topics** and on **`SKILL.md` files at conventional paths**. Zero
human in the loop — conform to the convention and you're indexed.
2. **Curated "awesome" lists** (VoltAgent, travisvn, ComposioHQ, tech-leads-club).
Manual PRs, human review. Higher trust, but most **reject brand-new skills** and
require social proof / real usage.
3. **Registries** (agentskills.io spec, `registry.modelcontextprotocol.io` for MCP
servers). Conformance + being on GitHub is the entry condition.
## Playbook — run in this order
**1. Put `SKILL.md` where scrapers look.** The single most common miss: the skill lives
at a nested path (e.g. `integrations/foo/skills/x/SKILL.md`) that