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

72

Quality

88%

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

77%

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

A highly actionable skill body with executable examples and a clear scaffold workflow, held back only by mild verbosity and a single-file structure that could offload tangential detail to references.

Suggestions

Move the 'Anthropic / Claude plugin compatibility' section into a reference file and link to it, keeping the core scaffold flow in SKILL.md.

Trim the second full code example to focus on the new concept (system.transform hook + multiple tools) rather than re-demonstrating the zod args pattern already shown in the minimal shape.

Add a verification checkpoint to the scaffold workflow (e.g., 'restart the session and confirm the tool appears') to close the loop on plugin loading.

DimensionReasoningScore

Conciseness

Mostly lean with no basic-concept padding, but the two overlapping full code examples (minimal shape and multi-tool) and the tangential Anthropic-compatibility table add length that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready executable TypeScript/zod examples, concrete file locations, and explicit opencode.json snippets — fully actionable rather than descriptive.

3 / 3

Workflow Clarity

The 'Scaffold workflow' gives a clear three-step sequence (create file, register in opencode.json, restart session) and this scaffolding task is not a destructive/batch operation requiring feedback loops.

3 / 3

Progressive Disclosure

Single well-sectioned file with clear headings, but at ~160 lines with no external references the compatibility section and long multi-tool example are content that could be split into reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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, concise description that names concrete actions, supplies explicit natural-language triggers, and pins down a distinct niche. It answers both 'what' and 'when' without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration' — matching the top anchor rather than the partial 'names domain and some actions' level below.

3 / 3

Completeness

Explicitly answers both what ('Create an OpenCode plugin... Scaffolds the plugin file...') and when ('Use when the user asks to...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Quotes natural user phrasings — 'create a plugin', 'write a plugin', or 'make a plugin that does X' — giving good coverage of terms a user would actually say, not jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (OpenCode plugin for OpenWork) with distinct 'create/write/make a plugin' triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

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.