skill-authoring

Create and validate OpenCode skill definitions with standardized YAML frontmatter.

6|Updated Mar 11, 2026

Search Tags:#documentation #conventions #opencode #yaml-frontmatter #skill-authoring #agent-workflows

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill skill-authoring-open-hax

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/skill-authoring
Command: npx skills add https://github.com/open-hax/opencode-skills --skill skill-authoring-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain reusable, well-scoped, and loadable skill definitions for OpenCode, reducing duplication and improving consistency across projects.

Core Features & Use Cases

Provides a standardized SKILL.md frontmatter template with required fields (name, description) and a consistent body structure.
Validates skill directories for optional components (scripts, references, assets) and promotes discoverability in the skill catalog.
Guides contributors through a lightweight authoring workflow, including publishing updates to AGENTS.md and local OpenCode visibility.

Quick Start

Create a new skill under .opencode/skills/your-skill-name and write SKILL.md with the required frontmatter and a concise, actionable body.

Frequently Asked Questions about skill-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create reusable OpenCode skills with standard YAML frontmatter?▼

To create OpenCode skills, write a SKILL.md file under .opencode/skills/your-skill-name with required YAML frontmatter fields like name and description, plus a concise actionable body structure.

What is the required structure for a SKILL.md file in OpenCode?▼

A SKILL.md file requires YAML frontmatter with name and description fields, alongside a body containing goal, inputs, steps, and output sections. Optional fields include license, compatibility, and metadata.

How do I validate skill directories for optional components like scripts and references?▼

You validate skill directories by checking for optional components like scripts, references, and assets, enforcing conventions to ensure proper structure and promote discoverability within the skill catalog.

Can I use optional metadata fields when standardizing skill structure across repositories?▼

Yes, you can use optional frontmatter fields like license, compatibility, and metadata when standardizing skill structure across repositories, ensuring required name and description fields remain present.

What is the best way to coach contributors to follow OpenCode skill conventions?▼

The best way to coach contributors is using a lightweight authoring workflow that provides a standardized SKILL.md frontmatter template and publishes updates to AGENTS.md for local OpenCode visibility.

Why does my OpenCode skill need sections for goal, inputs, steps, and output?▼

Your OpenCode skill needs goal, inputs, steps, and output sections to enforce required documentation, ensuring the skill is well-scoped, loadable, and consistent across projects while reducing duplication.