D
devkindhq/github-seo-skill
Agent Skill for GitHub SEO: repo audit, search-ready README, pre-publish scan, MCP registry listings
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"devkindhq-github-seo-skill": {
"command": "npx",
"args": ["skills"]
}
}
}解析自我们于 2026-11-01 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"devkindhq-github-seo-skill": {
"command": "npx",
"args": ["skills"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio devkindhq-github-seo-skill -- npx skills
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 2 ★ · devkindhq/github-seo-skill · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-02 · 最近见到 2026-11-14 · 共见到 13 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 2 ★ · 1 个来源 · repo
- 安装
npx skills
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx skills。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: Agent 技能。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
devkindhq/github-seo-skill；我们收录于 2026-11-02；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/devkindhq-github-seo-skill/)
- 来源
- github · https://github.com/devkindhq/github-seo-skill
- 按领域浏览
- Agent 技能
- Traction
- 2 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。