一键导入
check-skill-name
Checks proposed skill names for collisions with reserved or existing names. Use when validating a skill or command name before creation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Checks proposed skill names for collisions with reserved or existing names. Use when validating a skill or command name before creation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Splits a large branch or PR into smaller, independently reviewable units by grouping changes and proposing parallel PRs or a stacked series. Use when a changeset is too big to review well and should be broken up.
Captures the portable, non-secret pi config from a live ~/.pi/agent into this repo's pi/ directory and commits it, without reading or copying secrets. Use when live pi config or extensions have drifted from the repo and need to be synced back.
Refreshes PR titles and descriptions to match the current branch changeset. Use when the PR title or body has drifted from the code.
Reviews the current session for problems and their eventual fixes, then proposes durable improvements to repo skills, scripts, or docs that prevent recurrence. Use when a session hit avoidable friction worth turning into a lasting fix.
Runs discovery and uncertainty resolution for a change, then writes a terse plan document covering purpose, behaviour, validation, architecture, and phased vertical slices. Use before building when a change needs a clear, agreed design.
| name | check-skill-name |
| description | Checks proposed skill names for collisions with reserved or existing names. Use when validating a skill or command name before creation. |
Validate skill/command names before creation to avoid collisions across harnesses and this repo.
known-names.json is the source of truth; only update it in explicit update mode.
Follow repo naming rules from CLAUDE.md / AGENTS.md.
check (default) or update./, basename only).known-names.json and in-repo names from frontmatter.CONFLICT: exact reserved/repo match.RISKY: near-match or alias collision.CLEAR: no collision.updated date.sources in known-names.json.known-names.json with merged names and new updated date.known-names.json, and only in update mode. Do not edit it during a check.known-names.json.For check: normalized name, verdict (CLEAR/CONFLICT/RISKY), owning sources, safe alternatives when needed, and updated date.
For update: per-source add/remove/unchanged counts, new updated date, and any failed refreshes.