create-skill

Create OpenCode skills with SKILL.md and frontmatter metadata validation.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill create-skill-nullhack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/create-skill
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill create-skill-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a formal, repeatable method to craft OpenCode skills that adhere to the skill-definition standard, ensuring consistency across projects.

Core Features & Use Cases

  • Documentation-driven skill creation and onboarding for new skills
  • Frontmatter-driven metadata validation and lean body content
  • Step-by-step guidance aligned with OpenCode's research-backed workflows
  • Use Case: Quickly scaffold a new skill directory (.opencode/skills/<skill-name>/) with SKILL.md and optional resources

Quick Start

Create a new skill directory under .opencode/skills, add a SKILL.md with the required frontmatter and content, and ensure the repository recognizes it as a valid Skill Unit.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create an OpenCode skill that complies with repository standards?

To create an OpenCode skill, scaffold a new directory under .opencode/skills and add a SKILL.md file with required frontmatter and lean body content, ensuring metadata validation passes repository standards.

What is the required frontmatter schema for an OpenCode SKILL.md file?

The frontmatter schema for an OpenCode SKILL.md file requires strict metadata fields to validate the skill-definition standard, driving metadata validation and ensuring the repository recognizes the skill unit.

What's the best way to structure a new skill directory for OpenCode?

The best way to structure a skill directory is placing it under .opencode/skills/<skill-name>/ with a SKILL.md file and optional resource directories, following documentation-driven skill creation workflows.

Do I need markdown frontmatter to define an OpenCode skill?

Yes, you need markdown frontmatter to define an OpenCode skill, as it enforces strict metadata validation and repository standards compliance required for the skill-definition standard onboarding process.

Why does my OpenCode skill fail repository standards validation?

Your OpenCode skill fails validation if the SKILL.md file lacks the strict frontmatter schema, contains invalid metadata, or misses required safety checks defined by the skill-definition standard.

Can I include optional resources when scaffolding an OpenCode skill?

Yes, you can include optional resource directories when scaffolding an OpenCode skill under .opencode/skills, supplementing the required SKILL.md file and its frontmatter-driven metadata.