chsh-sk-skill-create

Guides authoring of Agent Skills with SKILL.md frontmatter, structure, and registration rules.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-skill-create-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-skill-create
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-skill-create
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-skill-create-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a new Agent Skill is easy to get wrong: descriptions that fail to route, bloated bodies that waste context, missing Gotchas sections, and frontmatter names that don't match directory names. This Skill walks you through a disciplined, phase-based process for creating skills that actually trigger correctly and stay concise. ## Core Features & Use Cases - Structured creation workflow: Six phases from eval-first design through discovery, implementation, verification, registration in index.md and log.md, and handoff. - Authoring rules and anti-patterns: Enforces routing-trigger descriptions, the Pascal test for conciseness, progressive disclosure, decision-flow sections, and a canonical Self-Update Policy. - Use Case: You want to add a new skill for reviewing pull requests to your ~/.claude/skills vault. This Skill gathers requirements via structured questions, drafts the SKILL.md with correct frontmatter, seeds Gotchas from real failures, and registers it in the vault index. ## Quick Start Ask the agent to create a new skill for your workflow, for example: create a skill that generates commit messages in our team's format.

Frequently Asked Questions about chsh-sk-skill-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Agent Skill with SKILL.md?

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, followed by markdown instructions. Follow a phased workflow: write eval queries first, gather requirements, draft the body under 500 lines, then register it in the vault index.

How should I write a skill description for correct routing?

Start the description with "Use when" or "Load when" and describe the user's intent in their own words, keeping it under 50 words. Descriptions that summarize what the skill does instead of when to load it cause off-target activation.

What is the difference between personal and project skills?

Personal skills live in ~/.claude/skills/ and are available across all your projects. Project skills live in .claude/skills/ within a repository and are shared with anyone using that repository.

Why must the frontmatter name match the skill directory name?

Skill discovery scans directories and loads SKILL.md, so a mismatch between the directory name and the frontmatter name field can prevent the skill from surfacing. After renaming a directory, you must also update the name field inside SKILL.md.

When should a skill include a scripts directory?

Include scripts when operations are fragile or consistency is critical, such as database migrations or validation tasks. Pre-made scripts are more reliable than generated code, save tokens, and ensure consistent behavior across uses.