create-skill

Create Claude Code skills with structured frontmatter, workflows, and supporting reference files.

4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/willem4130/sageo-cli --skill create-skill-willem4130
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/willem4130/sageo-cli/tree/main/.claude/skills/create-skill
Command: npx skills add https://github.com/willem4130/sageo-cli --skill create-skill-willem4130

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Claude Code skill that actually triggers correctly and follows best practices is error-prone: vague descriptions prevent discovery, bloated SKILL.md files waste context, and missing frontmatter breaks loading. This Skill guides you through a proven six-step process to create well-structured, discoverable skills. ## Core Features & Use Cases - Guided six-step workflow: Define purpose, choose location and invocation pattern, write frontmatter, create concise content, add supporting files, and test the skill. - Templates and examples: Ships with templates.md (reference, task, review, commit message, debugging, and test-generation patterns), examples.md (seven real-world skills), and troubleshooting.md (common failure fixes). - Use Case: You want a custom /deploy slash command for your project. Invoke this Skill, follow the checklist, pick the project-level location with disable-model-invocation: true, and produce a tested SKILL.md in minutes. ## Quick Start Ask Claude to create a new skill for your desired task, for example: create a skill that generates conventional commit messages from staged changes.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a custom Claude Code skill?▼

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by concise markdown instructions. Place it in ~/.claude/skills/ for personal use or .claude/skills/ for project-level sharing, then test by invoking it.

What makes a good skill description for Claude Code?▼

A good description states what the skill does and when to use it, with specific keywords users naturally say. Write in third person, avoid vague phrases like "helps with files", and include trigger contexts so Claude can discover it automatically.

Why is my Claude Code skill not triggering automatically?▼

Skills fail to trigger when descriptions are too vague, frontmatter YAML is invalid, or disable-model-invocation is set to true. Verify the skill appears when asking what skills are available, then sharpen the description with specific keywords.

Where should I put project skills vs personal skills?▼

Project skills live in .claude/skills/<name>/SKILL.md and apply only to that repository, making them shareable via version control. Personal skills live in ~/.claude/skills/ and apply across all your projects.

How long should a SKILL.md file be?▼

Keep SKILL.md under 500 lines and include only what Claude does not already know. Move detailed documentation, examples, and large reference tables into supporting files loaded on demand through progressive disclosure.