skill-creator

Create, test, and iteratively improve SKILL.md skill files with optimized trigger descriptions.

507|40|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/waybarrios/opencode-power-pack --skill skill-creator-waybarrios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/waybarrios/opencode-power-pack/tree/main/skills/skill-creator
Command: npx skills add https://github.com/waybarrios/opencode-power-pack --skill skill-creator-waybarrios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a reusable AI skill that triggers reliably and produces consistent results is hard: descriptions under-trigger, instructions overfit to test cases, and drafts go untested. This Skill guides you through the full lifecycle of drafting, testing, evaluating, and refining SKILL.md files. ## Core Features & Use Cases - Guided Skill Authoring: Interviews you about intent, trigger contexts, and output formats, then drafts a complete SKILL.md with proper frontmatter (name, description, license) and imperative-style body instructions. - Test-Driven Iteration: Generates realistic test prompts, runs the draft skill against them, reads transcripts for wasted effort, and refines instructions without overfitting. - Description Optimization: Builds trigger-eval query sets (should-trigger and near-miss should-not-trigger) and iterates the description field against held-out test queries for accurate activation. - Use Case: You just walked an AI through a multi-step workflow and want to reuse it. Ask to turn the conversation into a skill, and it extracts the steps, drafts the SKILL.md, tests it on realistic prompts, and iterates until it works reliably. ## Quick Start Turn the workflow we just completed into a reusable skill and test it on a few realistic prompts.

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 skill with a SKILL.md file?▼

Define what the skill should do and when it should trigger, then write a SKILL.md with YAML frontmatter containing a name and description followed by imperative Markdown instructions. Test the draft on 2-3 realistic prompts and iterate based on the results.

How do I write a skill description that triggers accurately?▼

Include both what the skill does and specific contexts for when to use it, since all triggering information lives in the description field. Make it slightly pushy by listing related phrases and scenarios, then validate against a mix of should-trigger and near-miss should-not-trigger queries.

What is the required format for a SKILL.md file?▼

A SKILL.md requires YAML frontmatter with a name (lowercase alphanumeric with single hyphens, matching the directory name) and a description, followed by a Markdown body of instructions. Optional scripts, references, and assets directories can sit alongside it.

How long should a SKILL.md file be?▼

Keep the SKILL.md body under 500 lines so it stays efficient when loaded into context. If you approach the limit, move detailed content into reference files and point to them with clear guidance on when to read each one.

When should a skill include test cases?▼

Skills with objectively verifiable outputs like file transforms, data extraction, or fixed workflow steps benefit from test cases. Skills with subjective outputs such as writing style or art often do not, so qualitative review is enough.

Why does my skill keep failing on new prompts after testing?▼

The skill is likely overfitted to its test cases with rigid rules. Generalize the instructions, explain the reasoning behind each step instead of adding absolute MUSTs, and re-run earlier test prompts to confirm nothing regressed.