Guidance for editing Claude Code skills. Use when Claude touches skill folders or SKILL.md files so slash-command naming, frontmatter, helper scripts, and conditional paths stay coherent.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Guidance for editing Claude Code skills. Use when Claude touches skill folders or SKILL.md files so slash-command naming, frontmatter, helper scripts, and conditional paths stay coherent.
Skill Authoring
When editing skills:
The folder name is the actual slash command. Keep it stable and only rename intentionally.
Keep frontmatter high-signal. Use argument-hint, disable-model-invocation, context, agent, hooks, and paths only when they materially change behavior.
Put repetitive or fragile logic in scripts/ instead of re-describing it in Markdown.
If a skill depends on helper scripts or external tools, update the setup docs in the same change.
Use path-scoped skills for authoring guidance or narrow domain rules, not for broad project policy that belongs in CLAUDE.md.
Keep bodies concise and procedural. Avoid long "when to use" prose in the body; that belongs in the description.