github-seolisted
Install: claude install-skill devkindhq/github-seo-skill
# GitHub SEO
A playbook for getting an open-source repo found, ranked and cited, in the right order.
Built from SERP research plus standard open-source practice.
## Evidence labels
Every claim in this skill and its references carries one of three labels. Keep them when you
report back, and never upgrade a label without a source.
- **verified**: checked against a primary source or a live search result, with a date.
- **observed**: seen in a real result at a point in time, not a documented rule. Re-check before relying on it.
- **general**: common open-source practice, not tested here. State it as practice, not fact.
GitHub does not publish its search ranking algorithm. Treat any "GitHub ranks X" statement as inference.
## Step 0: pick the path
- **Path A, plain GitHub repo**: a template, starter, benchmark harness, CLI, library or skill.
- **Path B, MCP server**: the project defines tools or resources over the Model Context Protocol
(look for `server.json`, `mcp.json` or an MCP SDK dependency). Do Path A first, then Step B.
If unsure, check whether the repo exposes MCP tools. If it does, it is Path B plus Path A.
## Step 1: safety pass (mandatory, before anything goes public)
Never skip this, and never let distribution excitement jump ahead of it.
1. Confirm the repo holds no private client code, client names, store domains, internal ticket
keys, API details specific to a client, or personal data about contractors or employees.
2. Scan the **full git history**,