skill-creator

Guide creation of modular Opencode skills with templates and validation scripts.

6|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/trevin-j/dots --skill skill-creator-trevin-j
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/trevin-j/dots/tree/main/opencode/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/trevin-j/dots --skill skill-creator-trevin-j

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps authors and maintainers create consistent, discoverable Opencode skills by providing templates, conventions, and a step-by-step process so skills are token-efficient, easy to validate, and easy to extend.

Core Features & Use Cases

  • Frontmatter & discovery: Clear requirements for name and description to ensure skills are discoverable and correctly triggered.
  • Resource organization: Guidance on when to include scripts, references, and assets and how to reference them without bloating context.
  • Tooling & validation: Example initializer and quick validator scripts to bootstrap a skill and check frontmatter and structure before use.
  • Use Case: An engineer wants to add a PDF-processing skill; they initialize a new skill, add a deterministic script for parsing PDFs, add reference docs for APIs, update SKILL.md with triggers and examples, then run the validator to verify structure.

Quick Start

Initialize a new skill with the provided init_skill.py to create the directory, edit SKILL.md to add name and description, and add only the scripts/references/assets you actually need.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create and validate Opencode skills with YAML frontmatter?

Opencode skill creation involves initializing a directory with templates, writing YAML frontmatter in SKILL.md, and running validation scripts to verify structure. This process ensures skills remain token-efficient and easy to discover.

What is progressive disclosure when authoring Opencode skills?

Progressive disclosure is an Opencode skill authoring pattern that prevents context bloat by referencing scripts, references, and assets externally rather than embedding them. This keeps the skill token-efficient and discoverable.

How do I initialize a new Opencode skill directory and add scripts?

You initialize a new Opencode skill by running the provided init_skill.py script to generate the directory. Afterward, you edit SKILL.md to define the name and description, and add only the required scripts, references, or assets.

Do I need pyyaml to validate Opencode skill frontmatter?

Yes, pyyaml is required to parse and validate the YAML frontmatter in Opencode skills. The provided quick_validate.py script depends on this library to verify frontmatter validity and structural correctness.

What's the best way to organize references and assets in an Opencode skill?

The best way to organize references and assets in an Opencode skill is to include only necessary files and reference them externally in SKILL.md. This modular convention prevents context bloat and maintains token efficiency.

Why does my Opencode skill fail to trigger or get discovered?

Opencode skills fail to trigger when the YAML frontmatter lacks clear name and description fields. Running the quick_validate.py script checks frontmatter validity and structure to ensure the skill meets discovery requirements.