skill-creation-guide

Guides creation of Claude Skills in SKILL.md format with frontmatter rules, evals, and guard scripts.

5|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/PatriotAi/ai-lab --skill skill-creation-guide-patriotai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creation-guide
Source: https://github.com/PatriotAi/ai-lab/tree/main/melania-skills-ecosystem/skills/skill-creation-guide
Command: npx skills add https://github.com/PatriotAi/ai-lab --skill skill-creation-guide-patriotai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing a well-structured Claude Skill requires knowing YAML frontmatter rules, description trigger patterns, token limits, eval design, and packaging constraints. This Skill provides a step-by-step guide so new SKILL.md files are correctly structured, trigger reliably, and stay under platform limits. ## Core Features & Use Cases - SKILL.md authoring rules: Enforces mandatory YAML frontmatter (name, description with ALWAYS/DO NOT triggers), the 500-line body limit, and the 1024-character description cap. - Spec-driven TDD workflow: Guides writing a compact spec, deriving evals.json test cases with concrete assertions, and following a RED-GREEN-REFACTOR cycle before creating or updating a skill. - Decision Gate and anti-patterns: Provides an update-vs-create decision table, a catalog of common mistakes, and a pre-packaging checklist including validation and safety gates. - Use Case: When asked to create a new skill for invoice processing, it produces a complete SKILL.md template with Ukrainian-first triggers, 4-6 eval cases, a guard script, and packaging instructions. ## Quick Start Ask the assistant to create a new skill and write its SKILL.md file, and this guide will walk through frontmatter, body structure, evals, and packaging step by step.

Frequently Asked Questions about skill-creation-guide

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

FAQPage Schema
How do I create a Claude Skill with a SKILL.md file?▼

Create a directory containing SKILL.md with YAML frontmatter holding a kebab-case name and a pushy description with ALWAYS use when and DO NOT use for triggers. Keep the body under 500 lines, move details to references/, and add 4-6 evals.json test cases with concrete assertions.

What should a SKILL.md description field contain?▼

The description must stay under 1024 characters and include what the skill does, an ALWAYS use when clause with concrete trigger phrases, synonyms in both languages, and a DO NOT use for exclusion list. It is the only text the router sees when deciding to activate the skill.

When should I update an existing skill instead of creating a new one?▼

Default to updating the existing skill whenever the change fits its purpose without breaking it. Create a new skill only when the need logically fits no existing skill, proven by a coverage scan of the skill registry, or when the skill would exceed 500 lines.

Why are my evals missing after installing a .skill package?▼

The packager strips the evals/ directory from .skill archives, so installing from a .skill file never carries test cases. Keep source copies of evals separately in git or your Claude Code setup to avoid losing them on each install.

What is the correct structure of a .skill archive?▼

SKILL.md must sit at the root of the .skill archive, not nested in a subfolder like name/name/SKILL.md. Package by zipping the directory contents from inside the skill folder rather than zipping the folder itself.