skill-writer

A Claude Skill requires a SKILL.md file with frontmatter (name, description, optional allowed-tools), followed by structured sections: Overview, Quick Start, Instructions, Examples, Best Practices, Requirements, and Advanced Usage. The frontmatter enforces character limits and naming rules; the content structure ensures discoverability and correct activation.

Required: SKILL.md with valid frontmatter. Optional: reference.md, examples.md, scripts/ directory, templates/ directory. Names must follow strict conventions with character limits. Proper naming and file structure ensure your Skill is discoverable and activates correctly when invoked by Claude Code.

Skill activation and discoverability depend on correct SKILL.md structure, valid frontmatter fields, adherence to naming conventions, and proper content organization. Use the validation checklist to diagnose missing sections, malformed descriptions, or structural errors that prevent recognition by Claude Code.

Yes. Convert prompts into Skills by extracting the core logic into a SKILL.md file with frontmatter, organizing instructions into the standard content sections, defining allowed-tools if needed, and validating the structure against the schema. This transforms ad-hoc prompts into reusable, discoverable Skills.

Descriptions must be concise, keyword-rich, and front-load the core task or problem the Skill solves. Include relevant domain vocabulary (automation, prompt engineering, AI development) and state the outcome clearly. Clear descriptions improve search ranking and help users understand fit before activation.

Examples and best practices are optional files but strongly recommended. examples.md demonstrates real-world usage patterns, while best practices guide users toward effective deployment. Including both improves Skill adoption, reduces debugging time, and ensures users activate your Skill correctly from the start.