skill-creation

Define and validate OpenCode skills with consistent frontmatter and folder structure.

11|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill skill-creation-the-perfect-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creation
Source: https://github.com/the-perfect-developer/the-perfect-opencode/tree/main/.opencode/skills/skill-creation
Command: npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill skill-creation-the-perfect-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a repeatable, standards-compliant process for creating OpenCode skills, ensuring consistent frontmatter, directory structure, and resource organization to improve discovery and maintenance.

Core Features & Use Cases

  • Frontmatter validation: guarantees each skill has a valid name and description that match its directory.
  • Structured layout guidance: explains where SKILL.md sits relative to references/, examples/, and scripts/.
  • Progressive disclosure planning: outlines how content is split between SKILL.md and bundled resources to optimize context usage.
  • Validation tooling: provides a built-in checklist and example scripts to verify skill structure. Use cases include creating a new skill from scratch, upgrading an existing skill to the standard layout, and educating teammates on OpenCode skill authoring.

Quick Start

Follow this approach: create .opencode/skills/skill-name, add SKILL.md with proper frontmatter, and optionally add references/, examples/, and scripts/ as needed to support the skill.

Frequently Asked Questions about skill-creation

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

FAQPage Schema
How do I create a new OpenCode skill from scratch?

OpenCode skill creation starts by making a directory under .opencode/skills/, adding a SKILL.md file with valid frontmatter, and optionally using references/ and examples/ folders for supplementary resources.

What is progressive disclosure in OpenCode skill documentation?

Progressive disclosure splits content between a concise SKILL.md file and bundled directories like references/ and examples/, optimizing context usage by preventing the core file from bloating with detailed information.

Why does frontmatter validation fail when upgrading an existing skill?

Frontmatter validation fails if the skill name and description do not match its directory structure, requiring you to align the metadata fields with the official specification for reliable discovery and loading.

Can I use scripts to validate OpenCode skill folder structure?

Yes, you can use built-in example scripts to verify the skill folder structure, ensuring that SKILL.md and optional directories like scripts/ align with the official specification before deployment.

What's the best way to organize OpenCode skill resources without bloating the core file?

The best way to organize resources is placing detailed content in optional references/, examples/, and scripts/ directories, keeping SKILL.md concise while ensuring reliable skill discovery and loading.