skill-creator
Create new OpenCode skills with the standard scaffold.
Best for Creating new OpenCode skillsWorks with GitHubLow risk
⌘source
- author
@different-ai- language
- TypeScript
★14kstars
1.4kforks
Apr 28, 2026
✦overview.md
Key Features
- ·Creates standard skill scaffold
- ·Generates .env.example without credentials
- ·Adds .gitignore ignoring .env
- ·Prompts to store credentials safely
- ·Includes reusable scripts directory
- ·Documents config and script usage
Use Cases
- →User executes a flow and asks to create a skill for it
- →User requests a new skill and is guided to perform task first
Best for
- ✓Creating new OpenCode skills
- ✓Skill authors
Not ideal for
- !Editing existing skills
- !Skills with complex dependencies
FAQs
apps/server-v2/.openwork-server-v2-test/workspaces/ws_65a41c1c5f7f/config/.opencode/skills/openwork-managed/skill-creator/SKILL.md
name
skill-creator
description
Create new OpenCode skills with the standard scaffold.
Skill creator helps create other skills that are self-buildable.
The best way to use it is after a user already executed a flow and says: create a skill for this. Alternatively, if the user asks for a skill to be created, suggest they do the task first and ask for skill creation at the end.
This should trigger this scaffold:
- If the user needed to configure things, create a
.env.examplewithout credentials and include all required variables. - Ask the user if they want to store credentials. If yes, write them to a
.envfile in the skill, and suggest rotating keys later. - Always add a
.gitignorein the skill that ignores.env, and verify.envis not tracked. - If the user needed to interact with an API and you created scripts, add reusable scripts under
scripts/. - New skills should explain how to use the
scripts/and that.env.exampledefines the minimum config. - Skills should state that they infer what they can do from the available config.
Trigger phrases (critical)
The description field is how Claude decides when to use your skill. Include 2-3 specific phrases that should trigger it.
Bad example: "Use when working with content"
Good examples:
$install
1-click copynpx skills add different-ai/openwork --skill skill-creatorSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.