opencode-skills

To create modular agent skills, place a SKILL.md file with required name and description frontmatter under .opencode/skill or ~/.config/opencode/skill. You can optionally include directories for scripts, references, and assets to maintain consistent organization.

The required frontmatter schema for validating OpenCode skills mandates only the name and description fields. Optional directories support scripts, references, and assets, ensuring standardized discovery and permission patterns across project-scoped and global skill libraries.

Discovery paths and permission patterns control agent skill loading by defining project-scoped or global library locations under .opencode/skill or ~/.config/opencode/skill. Enforcing these paths ensures only authorized agents can discover and deploy the modular capabilities.

Yes, you can use optional scripting, references, and assets directories when building agent capabilities. These directories sit alongside the required SKILL.md frontmatter file, allowing developers to organize shared skill libraries and validate structure before deployment.

The best way to organize shared skill libraries is to standardize naming and structure using a consistent frontmatter schema. Group skills into project-scoped or global directories, validate the structure, and enforce permission patterns to control agent access.

Agent skill discovery fails when the SKILL.md file lacks the required name and description frontmatter, or when the skill is placed outside the defined .opencode/skill or ~/.config/opencode/skill discovery paths. Validate the structure and permissions before deployment.