create-skill

Scaffolds, validates, and packages new SKILL.md skill units from a template.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/hpark0011/mirror --skill create-skill-hpark0011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/hpark0011/mirror/tree/main/.agents/skills/create-skill
Command: npx skills add https://github.com/hpark0011/mirror --skill create-skill-hpark0011

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Creating a new AI skill by hand leads to inconsistent naming, vague discovery descriptions, and duplicated workflows. This Skill enforces a single authoring convention so every new skill is discoverable, correctly structured, and non-overlapping with existing ones. ## Core Features & Use Cases - Template-based scaffolding: Runs init_skill.py to copy the canonical SKILL.md template while enforcing naming rules (lowercase hyphenated, max 64 chars, no reserved words). - Mechanical validation: Runs validate_skill.py to check frontmatter, name-directory match, description triggers, body length, inline block size, and nested reference depth. - Overlap prevention: Greps existing skills for trigger phrases before writing anything, stopping near-duplicate skills at the source. - Use Case: When you ask to "make a skill for scaffolding Convex tables", it clarifies the brief, checks for overlap, scaffolds the directory, validates it, and reports the result in one sentence. ## Quick Start Ask the assistant to create a new skill for your repeated workflow, describing its purpose and trigger phrases.

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 new AI skill with a SKILL.md file?▼

Run init_skill.py with a lowercase hyphenated name to scaffold the directory from the template, then fill in the frontmatter and body sections. Finish by running validate_skill.py, which must exit 0 before the skill is considered done.

What naming convention should a skill use?▼

Use gerund form like creating-tickets or reviewing-prs, matching ^[a-z0-9-]+$ with a 64 character limit and no reserved words. Meta-skills whose surface is a tool concept may use action-noun form like create-skill or audit-skill.

How do I check if a skill already exists before creating one?▼

Grep the .claude/skills directory for every trigger phrase from your brief before writing anything. If an existing skill covers the workflow, stop and propose editing that skill instead of creating a near-duplicate.

What does the skill validator check?▼

validate_skill.py checks frontmatter delimiters, name-to-directory match, description length and trigger phrases, body under 500 lines, inline code blocks over 20 lines, nested reference depth, and time-stamped language. Errors exit 1; warnings are advisory.

When should I not create a new skill?▼

Skip skill creation for one-off prompts, personal memory entries, hook-based automation, or CLAUDE.md edits. Always-on guidance belongs in CLAUDE.md or rules files, not in a skill.