skill-creator

Bootstrap new OpenCode skills with standardized SKILL.md structure and frontmatter.

Updated Nov 30, 2018
One-click install
npx skills add https://github.com/guygrigsby/dotfiles --skill skill-creator-guygrigsby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/guygrigsby/dotfiles/tree/main/opencode/skills/skill-creator
Command: npx skills add https://github.com/guygrigsby/dotfiles --skill skill-creator-guygrigsby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a standardized scaffold for new OpenCode skills, ensuring the correct frontmatter, structure, and organization so skills are discoverable and maintainable.

Core Features & Use Cases

  • Enforces required frontmatter fields (name, description, context) and matches directory naming.
  • Provides a canonical SKILL.md scaffold with sections for title, triggers, quick start, core content, examples, and references.
  • Guides the user to set up optional references/scripts/assets and to run validation checks before submission.

Quick Start

Follow the Quick Start to bootstrap a new skill by providing its name, purpose, use cases, and triggers, then generate the SKILL.md scaffold and optional references.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I scaffold a new OpenCode skill with the correct frontmatter and structure?

Scaffolding a new OpenCode skill requires providing the skill name, purpose, use cases, and triggers to generate a canonical SKILL.md file with correct frontmatter and organized optional references.

What frontmatter fields are required when creating a valid OpenCode skill?

Required frontmatter fields for a valid OpenCode skill include name, description, and context. The skill name must use kebab-case formatting and match the directory naming to ensure discoverability.

How do I validate an OpenCode skill before submitting it to a catalog?

Validating an OpenCode skill before submission involves running built-in validation checks to ensure the SKILL.md scaffold, frontmatter fields, and directory naming conform to the standardized structure.

What is the best way to organize optional scripts and references for a skill?

The best way to organize optional scripts and references is to follow the canonical SKILL.md scaffold, which guides setting up dedicated sections for references, scripts, and assets during the scaffolding process.

Why does my OpenCode skill fail discoverability checks in the catalog?

OpenCode skills fail discoverability checks when the directory naming does not match the kebab-case name in the frontmatter, or when required fields like name, description, and context are missing or malformed.

Can I use skill-creator to bootstrap an OpenCode skill without prior YAML knowledge?

Yes, you can bootstrap an OpenCode skill without prior YAML knowledge by providing the skill's purpose and triggers, which automatically generates the correctly formatted frontmatter and SKILL.md scaffold.