Agent skill · writing content · aiskillstore
skill-builder
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
Why this skill is useful
Provides specific guidance on creating Claude Code Skills, including YAML formatting and directory structure that the AI wouldn't reliably generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Skill Builder What This Skill Does Creates production-ready Claude Code Skills with proper YAML frontmatter, progressive disclosure architecture, and complete file/folder structure. This skill guides you through building skills that Claude can autonomously discover and use across all surfaces (Claude.ai, Claude Code, SDK, API). Prerequisites Claude Code 2.0+ or Claude.ai with Skills support Basic understanding of Markdown and YAML Text editor or IDE Quick Start Creating Your First Skill --- Complete Specification 📋 YAML Frontmatter (REQUIRED) Every SKILL.md must start with YAML frontmatter containing exactly two required fields: Field Requirements name (REQUIRED): Type: String Max Length: 64 characters Format: Human-friendly display name Usage: Shown in skill lists, UI, and loaded into Claude's system prompt Best Practice: Use Title Case, be concise and descriptive Examples: ✅ "API Documentation Generator" ✅ "React Component Builder" ✅ "Database Schema Designer" ❌ "skill-1" (not descriptive) ❌ "This is a very long skill name that exceeds sixty-four characters" (too long) description (REQUIRED): Type: String Max Length: 1024 characters Format: Plain text or minimal markdown Content: MUST include: 1. What the skill does (functionality) 2. When Claude should invoke it (trigger conditions) Usage: Loaded into Claude's system prompt for autonomous matching Best Practice: Front-load key trigger words, be specific about use cases Examples: ✅ "Generate OpenAPI 3.0 documentation from Express.js routes. Use when creating API docs, documenting endpoints, or building API specifications." ✅ "Create React functional components with TypeScript, hooks, and tests. Use when scaffolding new components or converting class components." ❌ "A comprehensive guide to API documentation" (no "when" clause) ❌ "Documentation tool" (too vague) YAML Formatting Rules Critical: Only name and description are used by Claude. Additional fields are ignored. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/skill-builder--7eb84b