write-skill

Validate SKILL.md YAML frontmatter and required sections for skill documentation.

20|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill write-skill-herbertjulio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-skill
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/skills/write-skill
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill write-skill-herbertjulio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill Unit standardizes how new or updated skills are defined, validated, and discoverable by enforcing a YAML frontmatter entry point (SKILL.md) and a structured workflow.

Core Features & Use Cases

  • Enforces frontmatter requirements (name, description) and mandatory discovery metadata.
  • Provides a reproducible workflow for writing, testing, and validating skills (RED-GREEN-REFACTOR, validation checklist).
  • Ensures optional resources (scripts/, references/, assets/) are correctly associated and discoverable.
  • Useful for skill authors who need consistent documentation, auditors who verify skill integrity, and tooling that indexes skills for discovery.

Quick Start

Draft, test, and validate a new or updated skill using the RED-GREEN-REFACTOR cycle before deployment.

Frequently Asked Questions about write-skill

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

FAQPage Schema
How do I validate YAML frontmatter in SKILL.md documentation?

To validate YAML frontmatter in SKILL.md documentation, ensure required name and description fields are present, then run a validation checklist to verify mandatory discovery metadata and optional resource associations like scripts and assets.

What is the RED-GREEN-REFACTOR cycle for skill writing?

The RED-GREEN-REFACTOR cycle for skill writing is a standardized testing workflow that drafts, tests, and validates new or updated skills iteratively to ensure consistent documentation and structural integrity before deployment.

Does skill metadata validation require dependencies to check optional components?

Skill metadata validation requires no external dependencies to check optional components, as the validation process inherently detects and verifies associated resource directories like scripts, references, and assets directly.

What's the best way to standardize skill structure for repository discovery?

The best way to standardize skill structure for repository discovery is enforcing a YAML frontmatter entry point in SKILL.md, ensuring mandatory metadata fields and correctly associating optional resources for tooling indexing.

Why does my skill validation fail when optional components are incorrectly associated?

Skill validation fails when optional components are incorrectly associated because the standardized workflow requires directories like scripts, references, and assets to be properly linked and discoverable within the SKILL.md documentation structure.