skill-creator

Create, validate, and package Claude skills with structured SKILL.md templates and scripts.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/hkw2028/toy-project --skill skill-creator-hkw2028
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/hkw2028/toy-project/tree/main/.agents/skills/skill-creator
Command: npx skills add https://github.com/hkw2028/toy-project --skill skill-creator-hkw2028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Building a well-structured skill requires knowing the SKILL.md frontmatter format, resource organization, and packaging rules, which is easy to get wrong without guidance. This Skill provides the complete methodology and tooling to design, initialize, validate, and package skills correctly. ## Core Features & Use Cases - Skill Initialization: Run init_skill.py to scaffold a new skill directory with a SKILL.md template and example scripts, references, and assets folders. - Design Guidance: Apply progressive disclosure principles, workflow patterns, and output patterns from bundled reference files to write concise, effective instructions. - Validation & Packaging: Run package_skill.py to validate frontmatter, naming conventions, and structure, then produce a distributable .skill zip file. - Use Case: You want to build a pdf-editor skill. Use this Skill to plan reusable resources, scaffold the directory, write the SKILL.md, and package it into pdf-editor.skill for distribution. ## Quick Start Create a new skill called pdf-editor using the skill-creator workflow and package it into a distributable .skill file.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a new Claude skill from scratch?

Run init_skill.py with a hyphen-case skill name and output path to scaffold the directory. Then edit the generated SKILL.md frontmatter and body, customize the example scripts, references, and assets, and package the result with package_skill.py.

What should go in a SKILL.md description field?

The description must state what the skill does and exactly when to use it, including specific trigger scenarios, file types, or tasks. It is the primary triggering mechanism, so all when-to-use information belongs there, not in the body.

When should a skill include scripts versus references?

Use scripts for deterministic, repeatedly rewritten code like file converters. Use references for detailed documentation such as schemas or API guides that Claude loads only when needed, keeping SKILL.md under 500 lines.

How do I package a skill into a .skill file?

Run package_skill.py with the skill folder path and an optional output directory. It validates the frontmatter, naming conventions, and structure first, then creates a zip-format .skill file only if validation passes.

Why does skill validation fail on the name field?

Validation fails if the name is not hyphen-case, starts or ends with a hyphen, contains consecutive hyphens, or exceeds 64 characters. The name must also match the skill directory name exactly.