CtrlK
BlogDocsLog inGet started
Tessl Logo

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'.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 well-structured, highly actionable scaffolding skill with complete executable examples and clear key rules. The main improvements are adding a post-restart verification checkpoint and optionally splitting the API/compatibility detail into reference files.

Suggestions

Add a validation step to the workflow, e.g. 'After restart, confirm the tool appears / runs a smoke call before telling the user it works'.

Consider moving the Anthropic/Claude compatibility table and full hook reference into a references/ file, keeping SKILL.md a lean overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is code-forward and largely lean with high-density 'Key rules', but the Anthropic/Claude compatibility comparison table and adaptation steps are somewhat expansive for a scaffolding skill, keeping it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Provides two complete, copy-paste-ready TypeScript examples (minimal shape and multi-tool) plus concrete opencode.json snippets, covering the common cases at the top anchor.

5 / 5

Workflow Clarity

The 'Scaffold workflow' is a clear 3-step sequence for a single-purpose task, but lacks any validation checkpoint confirming the plugin loaded after restart, matching 'clear sequence with minor validation gaps'.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections with no nesting, but everything is inlined in one ~160-line file with no split-out references for the API detail or compatibility guide, matching 'good structure; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

87%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 that clearly pairs a concrete capability statement with explicit, natural trigger phrases in third-person voice. The only minor gap is specificity/trigger breadth — it could mention file-location or distribution variants for fuller coverage.

Suggestions

Consider adding a distribution synonym or path cue (e.g., '.opencode/plugins/' or 'npm plugin') to broaden trigger-term coverage.

Optionally mention one more concrete capability (e.g., 'registers the plugin in opencode.json') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

"Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration" lists three concrete actions but stops short of comprehensive coverage (e.g., file placement, registration), matching the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

Explicitly states both the what (scaffolds plugin with API shape, tools, hooks) and a concrete when ("Use when the user asks to 'create a plugin'..."), matching the top anchor for both elements with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ("create a plugin", "write a plugin", "make a plugin that does X") with good variation, but lacks synonym/extension breadth that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

"OpenCode plugin for OpenWork" carves a clear niche with distinctive triggers and minimal overlap risk with other skills, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
different-ai/openwork
Reviewed

Table of Contents

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.