A
arm-pz/skills-site
Static site and publish pipeline for an agent skills catalog: a generated landing page per SKILL.md skill or…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"arm-pz-skills-site": {
"command": "npx",
"args": ["skills"]
}
}
}解析自我们于 2026-10-31 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"arm-pz-skills-site": {
"command": "npx",
"args": ["skills"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio arm-pz-skills-site -- npx skills
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 0 ★ · arm-pz/skills-site · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-01 · 最近见到 2026-11-14 · 共见到 14 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 2 个来源 · repo
- 安装
npx skills
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx skills。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: Agent 技能。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
arm-pz/skills-site；我们收录于 2026-11-01；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# skills-site
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A static site and publish pipeline for a catalog of agent skills. Each skill
(a SKILL.md repo) or Claude Code mod gets its own landing page with a one-line
install command; /skills/, /mods/ and /workflows/ list them by type (every workflow
also gets its own page); the homepage leads with outcomes; and a
/.well-known/agent-skills/index.json discovery index lets anyone run
npx skills add https://your-domain. One GitHub Actions workflow keeps the
manifest in step with GitHub and tests, builds and verifies the site, then
commits the build to a deploy branch that Cloudflare Pages pulls through its
own GitHub app, so CI holds no Cloudflare credentials. Plain HTML, CSS and Python, no
framework. It is the source of skillsmith.tech, formerly skills.caffeinity.com.
Fork it for your own skills: list them in site/skills.json, then follow
Run locally. Every page is self-contained, and the shared design
tokens live in one :root block per page.
Related: caffeinity-skills is
the plugin marketplace for the same skills, and
publish-pipeline is the agent
skill that sets up and repairs this kind of pipeline.
## Run locally
python tools/agent-skills/build.py # needs the GitHub CLI, gh auth login
python tools/agent-skills/gensitemap.py --write
bash tools/agent-skills/makedist.sh
python -m http.server 8080 --directory dist
## Deploy
CI holds no Cloudflare credentials; Cloudflare pulls. Every hour, and on every
push to main, .github/workflows/publish.yml runs sync.py, which brings
site/skills.json in line with GitHub (new skill repos, moved repo HEADs,
renames, removals), rebuilds the site, gates it with checkdist.py and
verify.mjs, commits the sync back to main, and commits the gated dist/ to
the deploy branch (under public/, only when the build changed). The
Cloudflare Pages project is connected to that branch, so each push there goes
live in a few minutes. The job then waits for the live version.json to match
and verifies the live site; if it never matches it opens one "Deploy pending"
issue, and closes it once live matches. .github/workflows/health.yml runs tune-skill's regression check over
every published skill each night. PROJECT.md maps the whole ecosystem.
### Connecting Cloudflare Pages (once)
Cloudflare cannot attach Git to a project created by direct upload, so this is
a new Pages project that takes over the domain:
1. Merge to main and let publish run once, so the deploy branch exists.
2. Cloudflare dashboard → Workers & Pages → Create → Pages → Connect to Git.
Authorize the Cloudflare GitHub app for arm-pz/skills-site only.
3. Production branch deploy; framework preset None; build command empty
(or exit 0); build output directory public. No environment variables.
4. Settings → Builds → Branch control: Preview branches: None, so main
and PR branches never build (they hold sources, not a site).
5. Once its .pages.dev URL serves the hub, remove skills.caffeinity.com
from the old skills project's Custom domains and add it to the new one.
6. Run publish again (Actions → publish → Run workflow); the "Deploy pending"
(a SKILL.md repo) or Claude Code mod gets its own landing page with a one-line
install command; /skills/, /mods/ and /workflows/ list them by type (every workflow
also gets its own page); the homepage leads with outcomes; and a
/.well-known/agent-skills/index.json discovery index lets anyone run
npx skills add https://your-domain. One GitHub Actions workflow keeps the
manifest in step with GitHub and tests, builds and verifies the site, then
commits the build to a deploy branch that Cloudflare Pages pulls through its
own GitHub app, so CI holds no Cloudflare credentials. Plain HTML, CSS and Python, no
framework. It is the source of skillsmith.tech, formerly skills.caffeinity.com.
Fork it for your own skills: list them in site/skills.json, then follow
Run locally. Every page is self-contained, and the shared design
tokens live in one :root block per page.
Related: caffeinity-skills is
the plugin marketplace for the same skills, and
publish-pipeline is the agent
skill that sets up and repairs this kind of pipeline.
## Run locally
python tools/agent-skills/build.py # needs the GitHub CLI, gh auth login
python tools/agent-skills/gensitemap.py --write
bash tools/agent-skills/makedist.sh
python -m http.server 8080 --directory dist
## Deploy
CI holds no Cloudflare credentials; Cloudflare pulls. Every hour, and on every
push to main, .github/workflows/publish.yml runs sync.py, which brings
site/skills.json in line with GitHub (new skill repos, moved repo HEADs,
renames, removals), rebuilds the site, gates it with checkdist.py and
verify.mjs, commits the sync back to main, and commits the gated dist/ to
the deploy branch (under public/, only when the build changed). The
Cloudflare Pages project is connected to that branch, so each push there goes
live in a few minutes. The job then waits for the live version.json to match
and verifies the live site; if it never matches it opens one "Deploy pending"
issue, and closes it once live matches. .github/workflows/health.yml runs tune-skill's regression check over
every published skill each night. PROJECT.md maps the whole ecosystem.
### Connecting Cloudflare Pages (once)
Cloudflare cannot attach Git to a project created by direct upload, so this is
a new Pages project that takes over the domain:
1. Merge to main and let publish run once, so the deploy branch exists.
2. Cloudflare dashboard → Workers & Pages → Create → Pages → Connect to Git.
Authorize the Cloudflare GitHub app for arm-pz/skills-site only.
3. Production branch deploy; framework preset None; build command empty
(or exit 0); build output directory public. No environment variables.
4. Settings → Builds → Branch control: Preview branches: None, so main
and PR branches never build (they hold sources, not a site).
5. Once its .pages.dev URL serves the hub, remove skills.caffeinity.com
from the old skills project's Custom domains and add it to the new one.
6. Run publish again (Actions → publish → Run workflow); the "Deploy pending"
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/arm-pz-skills-site/)
- 来源
- github · https://github.com/arm-pz/skills-site
- 按领域浏览
- Agent 技能
- 收录来源
- 2 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。