write-a-skill

To create a valid OpenCode skill, define a SKILL.md entry point at the skill root containing YAML frontmatter with matching name and descriptive description fields, followed by a body with concrete rules and output expectations.

The required structure for an OpenCode SKILL.md file includes YAML frontmatter with mandatory name and description fields, and a body that provides concrete operational rules and clear output expectations for deployment behavior.

To audit existing OpenCode skills, apply validation across config/skills directories to ensure the required frontmatter shape and body structure are present, checking that name and description metadata are predictable and correctly matched.

Yes, you can use YAML templates to automate OpenCode skill scaffolding by enforcing a standard frontmatter shape across config/skills directories, guiding the creation, editing, and packaging of skills with predictable metadata.

OpenCode skill validation fails when frontmatter is missing because the system enforces a mandatory SKILL.md entry point requiring both a matching name and a descriptive description to ensure consistent deployment behavior.