example-standard-skill

To structure an OpenCode skill unit, include a SKILL.md file with required name and description frontmatter, optional support directories for references, and metadata fields like tagline, keywords, dependencies, and components. This standard-skill blueprint provides a ready-to-copy template.

A standard skill for OpenCode projects should include metadata such as a tagline, keywords, dependencies, and components. These fields support skill discovery and onboarding by enabling progressive disclosure and modular content organization within the skill unit.

You document and validate a standard skill structure by creating a SKILL.md entry with frontmatter, adding optional references, and including example artifacts. This demonstrates a reusable blueprint for OpenCode contributors seeking consistent skill units across projects.

Yes, you can use optional references and example artifacts to demonstrate progressive disclosure in an OpenCode skill. This modular content approach organizes detailed information separately from the core SKILL.md, improving education and collaboration for new contributors.

No, dependencies are not required to create a standard skill blueprint. The example standard skill has an empty dependencies list, meaning you can document and validate a basic skill structure using only SKILL.md frontmatter and optional references.

Use a standard skill template when you need consistent skill units across OpenCode projects and want to streamline contributor onboarding. Building a custom structure is only necessary if your skill requires specialized organization beyond the standard frontmatter, references, and example artifacts framework.