opencode-skill-creator

Create, test, evaluate, and optimize OpenCode skills through iterative benchmark-driven workflows.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/CliffVale/opencode-free-setup --skill opencode-skill-creator-cliffvale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-skill-creator
Source: https://github.com/CliffVale/opencode-free-setup/tree/main/skills/opencode-skill-creator
Command: npx skills add https://github.com/CliffVale/opencode-free-setup --skill opencode-skill-creator-cliffvale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing an OpenCode skill that triggers reliably and produces good output is hard to get right on the first try. This Skill guides you through a structured create-test-evaluate-iterate loop so skills are validated against real prompts and quantitative benchmarks instead of guesswork. ## Core Features & Use Cases - Guided Skill Authoring: Runs a mandatory intake interview, then drafts SKILL.md files with proper frontmatter, progressive disclosure structure, and staged temp-directory workspaces. - Paired Eval Runs & Benchmarking: Spawns with-skill and baseline runs in parallel, grades outputs against assertions, aggregates pass rates, timing, and token usage into benchmark reports, and serves an interactive review viewer. - Description Optimization: Generates realistic trigger/no-trigger eval queries and runs an automated optimization loop with train/test splits to improve skill triggering accuracy. - Use Case: You want a skill that formats weekly sales spreadsheets. This Skill interviews you about the workflow, drafts the skill, runs test prompts with and without it, shows you side-by-side results in a browser viewer, and iterates until the outputs meet your bar. ## Quick Start Ask the agent to help you create a new OpenCode skill for your workflow and let it interview you, draft the skill, and run evaluation loops on your test prompts.

Frequently Asked Questions about opencode-skill-creator

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

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

Start with an intake interview covering what the skill should do, when it should trigger, and the expected output quality. Then draft a SKILL.md with name and description frontmatter, write 2-3 realistic test prompts, and iterate based on evaluation results.

How do I test whether my OpenCode skill actually improves outputs?▼

Run each test prompt twice in parallel: once with the skill and once without as a baseline. Grade both outputs against assertions, aggregate pass rates and timing into a benchmark, and review the comparison in the skill_serve_review viewer.

How do I improve skill triggering accuracy in OpenCode?▼

Write about 20 realistic trigger and near-miss no-trigger queries, review them with the eval-review HTML template, then run the skill_optimize_loop tool. It splits queries into train and test sets and iteratively rewrites the description, selecting by held-out test score.

Where do I install an OpenCode skill after creating it?▼

Install project-level skills at .opencode/skills/<skill-name>/SKILL.md or global skills at ~/.config/opencode/skills/<skill-name>/SKILL.md. The directory name must match the name field in the SKILL.md frontmatter.

What makes a good skill description for triggering?▼

Include both what the skill does and specific contexts for when to use it, since all triggering decisions come from the description. Make it slightly pushy with concrete trigger phrases, because OpenCode tends to undertrigger skills on borderline prompts.

When should a skill not use quantitative test assertions?▼

Skills with subjective outputs like writing style or design quality are better evaluated qualitatively through human review. Assertions work best for objectively verifiable outputs such as file transforms, data extraction, and fixed workflow steps.