skill-creator

Create, validate, and package Claude skills with templates and scripts.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Dhanuzh/DCode-Core --skill skill-creator-dhanuzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Dhanuzh/DCode-Core/tree/main/crates/dcode-app/assets/builtin-skills/auto-inject/skill-creator
Command: npx skills add https://github.com/Dhanuzh/DCode-Core --skill skill-creator-dhanuzh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Creating a well-structured skill requires knowing the SKILL.md format, frontmatter rules, and packaging conventions. This Skill guides you through designing, initializing, validating, and packaging skills so they trigger correctly and stay concise. ## 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 keep skills lean and effective. - Validation & Packaging: Use package_skill.py to validate frontmatter, naming conventions, and structure, then bundle the result into a distributable .skill file. - Use Case: You want to build a pdf-editor skill. This Skill helps you gather usage examples, plan reusable scripts, scaffold the directory, write the SKILL.md, and package it for distribution. ## Quick Start Create a new skill named pdf-editor using the skill-creator workflow and initialize it in my skills directory.

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 generate a template directory containing SKILL.md plus example scripts, references, and assets folders. Then edit the SKILL.md frontmatter and body, customize resources, and package with package_skill.py.

What should go in a SKILL.md description field?

The description must state what the skill does and 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 I use scripts versus references in a skill?

Use scripts for deterministic, repeatedly rewritten code like file conversions that can execute without loading into context. Use references for documentation Claude should read on demand, such as schemas, API docs, or detailed workflow guides.

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-based .skill file only if validation passes.

Why does skill validation fail on my SKILL.md?

Validation fails when frontmatter is missing name or description, the name is not hyphen-case or exceeds 64 characters, the description contains angle brackets or exceeds 1024 characters, or unexpected frontmatter keys are present.