<skill-name>

You can use a front-matter-driven blueprint to define a standardized Skill unit template, ensuring predictable behavior during workflow planning, implementation, and validation. This enforces a strict YAML contract for name and description to enable reliable discovery.

Safe discovery and activation require strict YAML frontmatter that enforces a minimal contract on the name and description fields. This front-matter-driven blueprint ensures self-contained Skill units can be reliably loaded and executed.

The three-mode lifecycle guides deterministic automation by sequentially planning a topic, implementing the defined resources, and verifying the results. Running rh-skills plan generates a plan artifact for human review before implementation proceeds.

Yes, the blueprint defines an optional resource model allowing you to include scripts, references, and assets directories. These resources support the plan, implement, and verify workflows within your self-contained Skill unit.

The best way to structure self-contained Skill units is using a standardized blueprint with YAML frontmatter. This enforces a minimal contract on name and description, ensuring repeatable activation and predictable behavior across different topics.