create-skill

Enforce YAML frontmatter and SKILL.md structure for Skill Units.

21|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/siviter-xyz/dot-agent --skill create-skill-siviter-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/siviter-xyz/dot-agent/tree/main/skills/create-skill
Command: npx skills add https://github.com/siviter-xyz/dot-agent --skill create-skill-siviter-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill Unit provides a standardized blueprint for authoring Skills, ensuring frontmatter, structure, and reference organization follow best practices to enable fast activation and predictable behavior.

Core Features & Use Cases

  • Structured metadata: Enforces YAML frontmatter with required name and description.
  • Progressive disclosure guidance: Encourages segmenting long content into references to keep SKILL.md concise.
  • Reference organization: Demonstrates how to place developer references under references/ for on-demand loading.
  • Creator workflow: Serves as an onboarding guide for anyone designing or updating Skills.

Quick Start

To create a new Skill Unit, name the directory and add a SKILL.md with the required frontmatter and body. Then place extended guidance, examples, and references in the references/ directory and, if needed, the scripts/ directory for deterministic tasks. This Skill Unit can be used by agents to load and validate new Skills efficiently.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I structure SKILL.md frontmatter and references when authoring a new skill?

To structure SKILL.md for skill authoring, include YAML frontmatter with required name and description fields, keep the body under 200 lines, and place extended guidance in a references directory for on-demand loading.

What is progressive disclosure in skill authoring and when should I use it?

Progressive disclosure in skill authoring is the practice of segmenting long content into separate reference files to keep the main SKILL.md concise. Use it whenever your skill documentation exceeds the 200-line body limit.

What metadata fields are required in YAML frontmatter for a valid Skill Unit?

Required YAML frontmatter fields for a valid Skill Unit are name and description. Optional metadata fields include dependencies, keywords, and category to ensure fast activation and predictable behavior.

How do I organize scripts and developer references when creating a skill?

To organize scripts and developer references when creating a skill, place extended guidance and examples under the references directory, and put deterministic tasks in a scripts directory for on-demand loading.

Are there line limitations or content boundaries for the SKILL.md body?

Yes, the SKILL.md body has a strict limitation of 200 lines. Content boundaries are enforced by moving extended guidance, examples, and references into the references directory to maintain conciseness.

Can I use optional component directories when updating an existing skill?

Yes, you can use optional component directories when updating an existing skill. This skill authoring guide applies to both new and existing skills, covering frontmatter validation and reference organization.