opencode-skill-creation

Standardize OpenCode skill creation with frontmatter and naming conventions.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-skill-creation-open-hax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-skill-creation
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-skill-creation
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-skill-creation-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes the creation of OpenCode skills to ensure they are validated, load reliably, and adhere to repository conventions.

Core Features & Use Cases

  • Guides skill authors to follow a consistent template and structure.
  • Enforces frontmatter alignment with folder names for reliable discovery.
  • Helps teams scale the OpenCode skill catalog by providing a reusable authoring workflow.

Quick Start

Follow the Skill Authoring template to create a new skill under .opencode/skills and ensure the directory name matches the SKILL.md frontmatter.

Frequently Asked Questions about opencode-skill-creation

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

FAQPage Schema
How do I standardize OpenCode skill creation to ensure reliable loading?

Standardize OpenCode skill creation by following a consistent template under .opencode/skills, enforcing frontmatter alignment with folder names, and validating directory structure for reliable discovery.

What frontmatter structure is required for an OpenCode skill?

The required frontmatter structure must align with the skill folder name to ensure reliable discovery and loading within the local agent environment and OpenCode skill catalog.

How do I create a new skill under the .opencode/skills directory?

Create a new skill under .opencode/skills by using the Skill Authoring template, ensuring the directory name exactly matches the SKILL.md frontmatter for valid discovery.

Does OpenCode skill discovery require specific naming conventions?

Yes, OpenCode skill discovery requires naming conventions where the directory name matches the SKILL.md frontmatter, and optional component directories must be present for proper validation.

Why does my OpenCode skill fail to load in the local agent environment?

OpenCode skills fail to load when frontmatter structure and folder names are misaligned, preventing the local agent environment from validating and discovering the skill correctly.

What is the best way to scale an OpenCode skill catalog for a team?

Scale an OpenCode skill catalog by applying a reusable authoring workflow that enforces frontmatter structure, naming conventions, and component directory presence for team consistency.