skill-create-rule

Validate SKILL.md files against frontmatter, header, and section rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nowonbun/nowonbun-harness --skill skill-create-rule
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-create-rule
Source: https://github.com/nowonbun/nowonbun-harness/tree/main/codex-skills/skill-management_skill-create-rule
Command: npx skills add https://github.com/nowonbun/nowonbun-harness --skill skill-create-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents ambiguous or non-executable SKILL.md files by enforcing a strict frontmatter, header order, section presence, language rules, and completion gate so skill documents remain machine-actionable and reviewable.

Core Features & Use Cases

  • Frontmatter enforcement: Requires YAML frontmatter at file top with only name and description.
  • Structural validation: Enforces header order, mandatory sections (# Must, # Must NOT, # Definition of Done) and list formatting rules.
  • Governance & completion: Defines completion gate, verification, monitoring rules, and source-of-truth references for publishing skills.
  • Use Case: An author preparing a SKILL.md for publication runs a checklist to ensure the file meets repository governance and automation requirements.

Quick Start

Create or update a SKILL.md to follow the frontmatter, header order, section, language, and completion artifact rules defined in this document.

Frequently Asked Questions about skill-create-rule

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

FAQPage Schema
How do I validate YAML frontmatter in a SKILL.md file?▼

YAML frontmatter validation for SKILL.md files requires only `name` and `description` fields at the file top. This strict enforcement prevents ambiguous documents and keeps skill files machine-actionable for automated publication workflows.

What sections are required when authoring skill documentation?▼

Required sections for skill documentation include `# Must`, `# Must NOT`, and `# Definition of Done`. Structural validation enforces header order and list formatting rules to ensure documents remain executable and reviewable.

Why does my skill document fail governance checks during publication?▼

Skill documents fail governance checks during publication when missing required sections like `# Definition of Done`, violating header order, or containing invalid frontmatter. Verification monitors structural consistency and completion artifacts.

Can I add custom metadata fields to SKILL.md frontmatter?▼

No, custom metadata fields are not permitted in SKILL.md frontmatter. Strict enforcement allows only `name` and `description` in the YAML block to maintain machine-actionable consistency across skill publication workflows.

What is the best way to structure skill documents for automated verification?▼

Structure skill documents for automated verification by enforcing strict YAML frontmatter, maintaining header order, including mandatory sections like `# Definition of Done`, and providing completion artifacts. This ensures governance and reviewability.