Official frontmatter fields recognized by OpenCode. Use these conventions for consistency across skills: Any field not listed here is ignored by OpenCode's skil
The Metadata Standard skill defines the official frontmatter fields recognized by OpenCode, ensuring consistent and valid metadata across skills. It enforces naming conventions like lowercase letters and hyphens for skill names and specifies required and optional YAML fields such as `name`, `description`, and a nested `metadata` block with keys like `license`, `author`, and `version`. This standard prevents invalid or ignored fields, maintaining clean, machine-readable metadata for better discoverability and interoperability.
By following this standard, marketers can guarantee that skill metadata aligns with platform expectations, enabling accurate categorization and filtering. This reduces errors in skill registration and improves the reliability of automated workflows dependent on metadata fields.
This skill is essential for growth leads and agency strategists managing multiple skills or campaigns on Metaflow who need to maintain metadata consistency at scale. SEO and PPC operators developing or integrating custom skills will benefit by understanding how to properly format skill metadata to avoid ingestion issues. It also suits performance marketers responsible for tagging and versioning skills to support clear tracking and update management.
In scenarios where teams collaborate on skill libraries or publish skills publicly, adherence to this standard simplifies coordination and reduces overhead in metadata validation.
Practitioners start by naming their skill folder and `name` field using the prescribed lowercase, hyphenated format, avoiding invalid characters or double hyphens. Next, they draft a concise `description` that clearly states the skill’s purpose and triggers, staying within the 1–1024 character limit. Then, they fill optional metadata fields like `author`, `license`, and `version` to provide additional context and compliance information.
Before publishing, marketers validate their frontmatter against the naming regex and required fields to ensure OpenCode compatibility. Finally, they review the metadata for accuracy to enable proper filtering and discovery in the public directory.
What happens if a skill includes metadata fields not listed in the standard? Any unrecognized fields are ignored by OpenCode and will not affect skill functionality but may cause loss of expected metadata.
Is the `name` field case-sensitive? Yes, the `name` must be lowercase and use hyphens only, matching the directory name exactly to pass validation.
Can I omit optional metadata fields like `license` or `author`? Yes, optional fields can be left out, but including them improves transparency and version control.
Attach the Metadata Standard skill to your Metaflow agent task by including the properly formatted frontmatter in your skill directory. The agent will parse and validate these fields automatically, flagging any invalid naming or missing required properties. This ensures your skill metadata aligns with OpenCode expectations and supports seamless integration. For detailed guidance on formatting and troubleshooting, consult the...
For broader context, see our roundup of claude marketing skills, and read Claude skills for SEO for related setup guidance.