D
devkindhq/github-seo-skill
Agent Skill for GitHub SEO: repo audit, search-ready README, pre-publish scan, MCP registry listings
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"devkindhq-github-seo-skill": {
"command": "npx",
"args": ["skills"]
}
}
}Parsed from the README we fetched on 2026-11-01; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"devkindhq-github-seo-skill": {
"command": "npx",
"args": ["skills"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio devkindhq-github-seo-skill -- npx skills
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 2 ★ · devkindhq/github-seo-skill · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-02 · last seen 2026-11-14 · seen 13× · listed by 1 sources
- Score
- score 103 · 2 ★ · 1 sources · repo
- Install
npx skills
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
devkindhq/github-seo-skill；first catalogued 2026-11-02；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# GitHub SEO Skill
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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, Smithery, Glama and mcp.so.
It works with any tool that supports the Agent Skills format.
## Quick start
Install with the skills CLI:
bash
npx skills add devkindhq/github-seo-skill
Or 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:
bash
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.
## What it does
| Stage | What you get |
| Safety pass | Full-history secret scan and client-data check before anything goes public |
| Audit | A read-only script scores 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 |
## Run the audit yourself
Needs the GitHub CLI logged in. The script changes nothing.
bash
python3 skills/github-seo/scripts/checkreposeo.py owner/repo
It prints PASS, WARN or FAIL per check and exits non-zero on any FAIL. The social preview
image cannot be read or set through the CLI, so it is listed as a manual step.
## Network access and data
This repo collects no data and runs no server. The audit script only calls the GitHub CLI (gh)
you have logged in, using read-only requests. 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.
## How the advice is labelled
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.
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, Smithery, Glama and mcp.so.
It works with any tool that supports the Agent Skills format.
## Quick start
Install with the skills CLI:
bash
npx skills add devkindhq/github-seo-skill
Or 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:
bash
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.
## What it does
| Stage | What you get |
| Safety pass | Full-history secret scan and client-data check before anything goes public |
| Audit | A read-only script scores 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 |
## Run the audit yourself
Needs the GitHub CLI logged in. The script changes nothing.
bash
python3 skills/github-seo/scripts/checkreposeo.py owner/repo
It prints PASS, WARN or FAIL per check and exits non-zero on any FAIL. The social preview
image cannot be read or set through the CLI, so it is listed as a manual step.
## Network access and data
This repo collects no data and runs no server. The audit script only calls the GitHub CLI (gh)
you have logged in, using read-only requests. 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.
## How the advice is labelled
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/devkindhq-github-seo-skill/)
- Source
- github · https://github.com/devkindhq/github-seo-skill
- Browse by field
- Agent skills
- Traction
- 2 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.