Start with a real task.
Turn a repeatable job into a structured skill with clear instructions and supporting examples.
SKILL.md + referencesA skill + plugin for OpenCode
Good skills aren’t
a guessing game.
Create, evaluate, and improve your OpenCode skills. Go from a first draft to a version you have a reason to trust.
Open sourceApache-2.0 pluginBuilt for OpenCode
skill-creator / workflowOPENCODE
>Create a skill for reviewing
Docker Compose files.
↳
Define the taskWhat to review. When to use it.
↳
Draft SKILL.mdInstructions, context, and examples.
↳
Build an eval setShould trigger + should not trigger.
>Test where this skill belongs.
And where it doesn’t.
↳
Label real requestsPositive cases and near misses.
↳
Run skill_evalInspect false positives and negatives.
↳
Keep a holdout setCheck more than the training examples.
>Make the next description
a decision, not a guess.
↳
Read the failure patternsClarify the intended task boundary.
↳
Compare candidatesEvaluate against the saved baseline.
↳
Review actual outputsChoose the revision with evidence.
Illustrative workflowSee the real example
INSTALL / OPENCODE V2
npx opencode-skill-creator install --globalLess intuition. More iteration.A workflow for the work
A workflow for the work
behind a good skill.
A draft is a starting point. Give it structure, find out when it triggers, and compare what it actually produces.
Test the boundary.
Check the requests that should activate your skill—and the nearby ones that shouldn’t.
skill_evalKeep what works better.
Refine descriptions, compare candidates, and review outputs against a baseline.
skill_optimize_loopThe development loopMake the next version
Make the next version
an informed choice.
The skill brings the process. The plugin brings the tools. You stay in the loop for the decisions that matter.
01 →
Describe the job.
Tell OpenCode what the skill should do, when it should be used, and what a useful result looks like.
02 →
Give it a fair test.
Use positive cases, negative cases, and held-out examples. Read the failures before changing the description.
03 →
Walk through the workflow Compare the actual work.
Review paired outputs with and without the skill. A better trigger score is useful; better work is the point.
From the blog
Build a little understanding.
Getting started
Create your first OpenCode skill
From a repeatable task to a skill you can actually evaluate.
Read the guideEvaluationTest when your skill should trigger
Give your skill a test set that includes the times it should stay quiet.
Read the guideOptimizationBetter descriptions. Fewer guesses.
Use failures, baselines, and held-out cases to guide the next revision.
Read the guideYour next skill starts here.
Bring a repeatable task. Leave with a way to improve it.