skill-making

Create Claude agent skills with SKILL.md templates and validation rules.

20|Updated Apr 14, 2016
One-click install
npx skills add https://github.com/binarin/nixos-config --skill skill-making
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-making
Source: https://github.com/binarin/nixos-config/tree/main/files/claude-skills/skill-making
Command: npx skills add https://github.com/binarin/nixos-config --skill skill-making

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to creating Claude agent skills, ensuring consistent templates, documentation, and quality gates for maintainable automation.

Core Features & Use Cases

  • Standardized Skill Template: Encourages a consistent SKILL.md frontmatter and markdown body for every skill.
  • Guided Workflow: Step-by-step guidance from skeleton to validation, including references and examples.
  • Self-contained structure: Encourages REFERENCE.md, EXAMPLES.md, and optional scripts/.
  • Quality gates: Enforces Unix line endings, progressive disclosure, and modular organization.

Quick Start

Start a new Claude skill by following the template: create SKILL.md with a name and description, optionally add REFERENCE.md and EXAMPLES.md, and place any tooling scripts under scripts/.

Frequently Asked Questions about skill-making

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

FAQPage Schema
How do I create a Claude skill that follows best practices?

Create a Claude skill by structuring it with a SKILL.md file containing YAML frontmatter (gerund-form name, max 64 characters, lowercase with hyphens) and markdown body, optionally adding REFERENCE.md and EXAMPLES.md files. Enforce Unix LF line endings, keep descriptions under 1024 characters, and organize supporting scripts in a scripts/ directory.

What are the technical requirements for Claude skill templates?

Claude skills require Unix LF line endings, YAML frontmatter with a gerund-form name (max 64 characters, lowercase letters, numbers, hyphens only), a description under 1024 characters with no XML tags, and a mandatory SKILL.md layout. Optional components include REFERENCE.md, EXAMPLES.md, and a scripts/ directory.

When should I use templates and documentation for skill structure?

Use structured templates and documentation when building new skills, refining existing ones, or learning skill conventions. Templates enforce consistent organization across single-piece and multi-piece setups, ensuring maintainability and enabling automatic activation through standardized quality gates.

Can I organize complex multi-piece skills with supporting files?

Yes. Multi-piece skills can be organized as self-contained structures with SKILL.md as the core, REFERENCE.md for domain knowledge, EXAMPLES.md for usage patterns, and a scripts/ directory for tooling. This modular approach supports complex setups intended for automatic activation.

What file structure and naming conventions must skills follow?

Skills must use SKILL.md as the primary file with gerund-form names (max 64 characters, lowercase letters, numbers, hyphens). Include optional REFERENCE.md and EXAMPLES.md for extended documentation. Use Unix LF line endings throughout and place any automation scripts in a scripts/ directory.