create-skill

Create a skill by building a SKILL.md file with YAML frontmatter (name, description, allowed-tools), a clear description of what the skill does, and supporting files organized in Unix-style relative paths. This structure enables Claude to discover and activate your skill automatically based on user context.

Include required fields: name, description, and optional allowed-tools. The description should be context-driven so Claude can autonomously identify when to activate your skill based on user prompts and the task at hand.

Yes, supporting files like scripts, templates, and documentation integrate into your skill structure. Organize them as relative paths within your skill directory to build complex, multi-component capabilities that activate together.

Write a focused, context-driven description that signals when your skill applies. When describing your skill's purpose clearly—for example, mentioning PDF work for a PDF processor skill—Claude recognizes the connection and activates it without explicit user instruction.

Project skills are shared within a codebase or team with specific directory layouts and version history guidelines; personal skills are individual templates with supporting files. Both follow the same SKILL.md format and frontmatter structure for consistency.

Basic familiarity with YAML and file structure helps, but the skill-creation process guides you through the template format and best practices. Most skills combine documentation, simple configuration, and optional supporting scripts.