CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-creator

Create OpenCode plugins and know where to load them.

53

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/plugin-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 compact, well-organized reference with concrete paths and config, but the plugin template is placeholder code with no working hook example or explicit creation/verification workflow, leaving the user to assemble the steps themselves.

Suggestions

Replace the placeholder template with one complete, executable plugin example showing a real hook (e.g. a working hook name and handler from the OpenCode API).

Add a short ordered workflow: create the file in the appropriate directory (from the paths listed), implement hooks, and verify the plugin loads on startup.

Trim filler such as the '(Already Configured)' heading qualifier and 'Use the docs as the escape hatch when unsure' to tighten the body further.

DimensionReasoningScore

Conciseness

The body is lean and fact-dense (paths, load order, cache location), with only minor trimmable bits such as 'Use the docs as the escape hatch when unsure', the '(Already Configured)' heading, and the Reference line duplicating the Notes section — anchor 4, not quite 'every token earns its place'.

4 / 5

Actionability

Plugin paths and the opencode.json snippet are concrete, but the plugin template is a placeholder — '// Hook implementations go here' with no actual hook names or working example — so the core artifact is not executable as written, matching anchor 3.

3 / 5

Workflow Clarity

The body lists where plugins live and how they load, but there is no ordered create-a-plugin sequence (where to save the template, how to confirm it loaded) and no verification checkpoints; the content reads as reference facts rather than a workflow — anchor 3.

3 / 5

Progressive Disclosure

Under 50 lines, no bundle files needed, well-organized sections, and a clearly signaled one-level-deep external reference (official docs URL); the simple-skill exception applies.

5 / 5

Total

15

/

20

Passed

Description

53%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.

The description states a clear, platform-specific capability but omits any 'when to use' trigger guidance and lacks natural keyword variations, capping its usefulness for skill selection.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when creating or configuring OpenCode plugins, adding npm plugin packages, or setting up plugin directories.'

Include natural trigger terms and synonyms users would say: 'plugin', 'hook', 'npm plugin', 'opencode.json', '.opencode/plugins'.

Expand the 'what' into a couple more concrete actions (e.g. 'create plugins, configure npm plugin packages, place plugins in project or global directories') to lift specificity.

DimensionReasoningScore

Specificity

"Create OpenCode plugins" names the domain and one concrete action, but "know where to load them" is a knowledge state rather than an action, so coverage of concrete actions is not comprehensive — matching anchor 3 rather than anchor 4.

3 / 5

Completeness

The 'what' is clear (create plugins, know where to load them) but there is no 'Use when...' clause or equivalent trigger guidance; the rubric explicitly caps completeness at 3 for this, matching anchor 3 exactly.

3 / 5

Trigger Term Quality

Relevant keywords exist ("OpenCode plugins", "create", "load") but common natural variations users would say — "plugin", "hook", "npm plugin", file paths/extensions — are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"OpenCode" pins the skill to a specific platform with a clear niche, leaving only minor overlap risk with generic or other-platform plugin skills — anchor 4 rather than 5 since the term 'plugin' alone is broad.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
trackdubllc/Babel-Player-Alpha
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.