GitHub SEO Skill is an Agent Skill for Claude Code that gets open-source GitHub repos found on Google and GitHub search. It audits a repo's name, description, topics and README, writes a search-ready README, runs a pre-publish secret and client-data check, and walks MCP servers through registry submissions such as the Official MCP Registry, Glama and mcp.so.
It works with any tool that supports the Agent Skills format.
Install with the skills CLI:
npx skills add devkindhq/github-seo-skillOr as a Claude Code plugin:
/plugin marketplace add devkindhq/github-seo-skill
/plugin install github-seo-skill@github-seo-skill
Or copy the skill folder into a project:
git clone https://github.com/devkindhq/github-seo-skill.git
cp -r github-seo-skill/skills/github-seo your-project/.claude/skills/Then ask in plain words, for example "audit github.com/you/your-repo for search visibility" or "we are about to open-source this CLI, what should we check first?". The skill activates from its description.
| Stage | What you get |
|---|---|
| Safety pass | Full-history secret scan and client-data check before anything goes public |
| Audit | Read-only GitHub CLI checks score the description, topics, homepage, license, README shape and community files |
| README | An eight-section template aimed at the search snippet, 400 to 700 words |
| Metadata | Repo slug, About text, topics, Website field and social preview guidance |
| Launch | A tested order: repo, write-up, community, wider channels, template galleries |
| MCP servers | A registry-by-registry checklist built around the Official MCP Registry |
Needs the GitHub CLI logged in. The checks change nothing.
Follow audit-checks.md: four gh commands read the
repo, and a table gives pass, warn or fail for each check. The social preview image cannot be read
or set through the CLI, so it is listed as a manual step.
This repo collects no data and runs no server. The audit only calls the GitHub CLI (gh)
you have logged in, using read-only requests. The listing checks read public pages of the Official
MCP Registry, npm, Docker Hub and Glama, and read the awesome-mcp-servers list through gh. When the skill guides an MCP server submission, it
tells you to look up a server on the Official MCP Registry
(https://registry.modelcontextprotocol.io), and the publishing steps use the mcp-publisher
tool, which sends your server metadata to that registry. Nothing is sent unless you run those steps.
GitHub does not publish how its search ranks repositories, so every claim in the skill carries a label:
- verified: checked against a primary source, with a date.
- observed: seen in a real search result at a point in time. Re-check before relying on it.
- general: common open-source practice that has not been tested here.
The skill is built to repeat those labels when it reports back, instead of presenting guesses as rules.
skills/github-seo/ # the skill: SKILL.md, references/, evals/
.claude-plugin/ # plugin and marketplace manifests
Paldom/github-skills is a broader set of skills for professional repos (README authoring, docs sites, community files, protections). This skill focuses on search visibility, safe publishing and MCP registry listings, and the two complement each other.
Corrections backed by a source are the most useful contribution. See CONTRIBUTING.md. Security issues go through SECURITY.md, and everyone is expected to follow the Code of Conduct.
