build-skill

To create an OpenCode skill with proper YAML frontmatter, use scaffolding templates that enforce required name and description fields, ensuring consistent skill discovery and standardized SKILL.md files across project installations.

The best way to validate OpenCode skill folder structures is to use automated validation workflows that check YAML frontmatter requirements and verify optional references, scripts, and assets directories to catch errors early.

Skill scaffolding for team-based OpenCode projects works by generating standardized directory structures and starter templates, ensuring consistent naming conventions and frontmatter validation across both global and project-scoped installations.

Yes, you can use skill templates for both global and project-scoped OpenCode installations, as the scaffolding and validation workflows are designed to support team environments with consistent folder structures and frontmatter requirements.

OpenCode skill validation fails without frontmatter because the system enforces mandatory YAML fields, specifically name and description, to maintain consistent skill discovery and standardized SKILL.md formatting across teams.

When building an OpenCode skill, the required components are YAML frontmatter containing name and description fields, while optional components include references, scripts, and assets directories that support the validation workflow.