create-plugin

Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable skill body: executable examples dominate, guidance is non-obvious where it needs to be (the .shape gotcha, env vars, in-process fetch), and structure is easy to navigate. The only weaknesses are a missing verification step in the scaffold workflow and modest reference material that could be split out.

Dimension	Reasoning	Score
Conciseness	The body is efficient — file locations, key rules, and executable snippets with no padding about concepts Claude already knows. Anchor 5 ('every token earns its place') isn't quite met: the Anthropic-compatibility table and the Key rules list partly restate what the code comments already show ('NOTE: .shape, not the ZodObject').	4 / 5
Actionability	Fully executable, copy-paste-ready code: the minimal plugin shape, a complete two-tool example with system-prompt hook, exact opencode.json registration snippets, and a concrete scaffold workflow. These cover the common cases, matching anchor 5; it is well above anchor 4's 'minor gaps'.	5 / 5
Workflow Clarity	The 'Scaffold workflow' gives a clear numbered sequence (create the plugin file, add to opencode.json, restart session). Anchor 5 is not met because there is no verification checkpoint (e.g., confirming the tool loads or the plugin compiles), but this is not a destructive/batch operation, so no cap applies.	4 / 5
Progressive Disclosure	Well-sectioned with clear headers (When to use, Plugin API, hooks, registration, compat, example, workflow) and no bundle files exist, so everything lives appropriately in SKILL.md with easy navigation — matching anchor 4. It falls short of anchor 5 only because reference-style material (the hooks API listing and the Anthropic compatibility section) is inlined where a references/ split could keep SKILL.md leaner.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete capabilities, and an explicit 'Use when...' clause with natural trigger phrasings. Only minor gaps — a few missing synonyms and slight overlap risk with other 'plugin' requests.

Dimension	Reasoning	Score
Specificity	"Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration" names the domain and three concrete actions. It falls short of anchor 5 because coverage has minor gaps (e.g., registering in opencode.json, adapting Anthropic plugins) and is clearly above anchor 3's 'not comprehensive' level.	4 / 5
Completeness	The 'what' is explicit ("Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration") and the 'when' is explicit with concrete trigger phrases ("Use when the user asks to..."). This matches anchor 5 exactly; anchor 4's 'when could be more explicit' does not apply.	5 / 5
Trigger Term Quality	The trigger clause quotes natural user phrasings — "'create a plugin', 'write a plugin', or 'make a plugin that does X'" — plus "OpenCode plugin" and "OpenWork". Not anchor 5: a few natural synonyms are missing (e.g., 'extend OpenCode', 'add a custom tool'), but it is well above anchor 3's 'missing common variations'.	4 / 5
Distinctiveness Conflict Risk	The niche is distinct — 'OpenCode plugin for OpenWork' — and unlikely to grab unrelated skills, matching anchor 4. Not anchor 5: generic phrasings like "make a plugin" could overlap with other plugin ecosystems (VS Code extensions, Anthropic plugins), a minor conflict risk the body itself acknowledges.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: different-ai/openwork
Path: .opencode/skills/create-plugin/SKILL.md
Commit: 417244c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.