skill-creator

Creates, tests, and improves OpenCode Skills following SKILL.md frontmatter conventions.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/voiddreamz/dotfiles --skill skill-creator-voiddreamz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/voiddreamz/dotfiles/tree/main/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/voiddreamz/dotfiles --skill skill-creator-voiddreamz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-structured SKILL.md that actually triggers reliably is hard: descriptions must contain both the action and trigger words, folder names must match the skill name, and bodies must stay concise. This Skill codifies those rules so new OpenCode Skills are created correctly the first time. ## Core Features & Use Cases - SKILL.md Authoring Guidance: Enforces the required frontmatter (name, description), naming rules (1-64 chars, lowercase with hyphens), and a body under 500 lines with overflow moved to references/. - Trigger Optimization: Explains how to write descriptions that combine what the skill does with concrete trigger phrases to maximize activation rate. - Creation Workflow: Walks through confirming scope with the user, writing the SKILL.md, creating the folder under ~/.config/opencode/skills/{name}/, and verifying via the skill tool after restart. - Use Case: You have a repeatable code review workflow and want it as a reusable skill. This Skill guides you to produce a compliant SKILL.md with a high-trigger description and proper directory placement. ## Quick Start Ask the assistant to turn your current workflow into a new OpenCode skill with a proper SKILL.md file.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a new OpenCode skill?▼

Write a SKILL.md file with YAML frontmatter containing a name and description, then place it in ~/.config/opencode/skills/{name}/ where the folder name exactly matches the skill name. Restart OpenCode and verify with the skill tool.

How do I write a good skill description for better triggering?▼

Combine what the skill does with concrete trigger words, for example stating it reviews code for bugs and activates when users ask to review code or check a PR. Vague descriptions like 'code review tool' trigger far less reliably.

What is the required structure of a SKILL.md file?▼

It needs YAML frontmatter with name (1-64 lowercase hyphenated characters matching the folder) and description (1-1024 characters), followed by a Markdown body with usage triggers, detailed instructions, and examples kept under 500 lines.

When should I use references or scripts directories in a skill?▼

Use references/ for supplementary material loaded only when needed, keeping the main body under 500 lines. Use scripts/ for helper scripts that perform deterministic tasks the skill invokes.

Why is my OpenCode skill not being triggered?▼

The most common cause is a description that lacks explicit trigger words or a folder name that does not exactly match the skill name in the frontmatter. Also verify the file is named SKILL.md and restart OpenCode after creation.