skill-creator

Create, validate, and package Claude skill directories with SKILL.md frontmatter.

2|2|Updated Jun 28, 2015
One-click install
npx skills add https://github.com/camercu/dotfiles --skill skill-creator-camercu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/skill-creator
Command: npx skills add https://github.com/camercu/dotfiles --skill skill-creator-camercu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing a well-structured skill requires knowing the SKILL.md format, frontmatter rules, and packaging conventions; this Skill guides the entire creation workflow from planning to a distributable .skill file. ## Core Features & Use Cases - Skill Scaffolding: Run init_skill.py to generate a template skill directory with SKILL.md frontmatter and example scripts, references, and assets folders. - Validation and Packaging: Use quick_validate.py and package_skill.py to check naming, description trigger cues, and Overview sections, then bundle the result into a .skill zip file. - Design Guidance: Apply progressive disclosure principles and workflow/output patterns from the bundled references to keep skills concise and effective. - Use Case: When asked to "package this workflow as a skill", follow the six-step process to understand usage examples, plan reusable resources, initialize the directory, write SKILL.md, and package the validated result. ## Quick Start Create a new skill named pdf-rotator 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 scripts/init_skill.py with the skill name and output path to generate a template directory containing SKILL.md and example scripts, references, and assets folders. Then edit SKILL.md, customize the resources, and package with package_skill.py.

What should go in a SKILL.md description field?▼

The description carries trigger cues only, written as "Use when ..." with concrete situations and literal user phrasings. What the skill does belongs in the body's Overview section, since the description alone decides whether the skill triggers.

How do I validate and package a skill into a .skill file?▼

Run scripts/package_skill.py with the skill folder path. It first validates frontmatter, naming conventions, and description quality via quick_validate.py, then creates a zip-format .skill file if validation passes.

When should a skill include scripts, references, or assets?▼

Include scripts for deterministic or repeatedly rewritten code, references for documentation loaded into context as needed, and assets for files used in output like templates or fonts. Delete any example directories the skill does not need.

Why does skill validation fail on the Overview section?▼

Validation fails when a body over 25 lines does not open with a non-empty "## Overview" section. Bodies of 25 lines or fewer are exempt because they are read whole in one glance.