create-plugin

Create an OpenCode plugin for iPolloWork. 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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/create-plugin/SKILL.md

Quality

Content

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

Highly actionable content with executable, copy-paste-ready examples and a tight key-rules section that captures the non-obvious API details. The main weakness is the scaffold workflow, which lacks any verification step to confirm the plugin loaded correctly after session restart.

Suggestions

Add a validation step to the scaffold workflow, e.g. after restart, confirm the plugin loaded by checking that its tools are available (or by inspecting OpenCode's plugin load output) before telling the user it is done.

Move the full hooks listing and/or the Anthropic compatibility table into a one-level-deep reference file (e.g. references/hooks.md) and keep only the most common hooks inline in SKILL.md.

Trim the "Available hooks" block to the hooks most plugins actually use, since tool-execute and event hooks are already exercised by the multi-tool example.

Dimension	Reasoning	Score
Conciseness	The key-rules list and code examples are dense with little padding and no explanation of concepts Claude already knows, but the Anthropic compatibility table and inline hooks listing could each be trimmed.	4 / 5
Actionability	Two complete copy-paste TypeScript examples (minimal shape and multi-tool plugin) plus both file-path and npm registration JSON cover the common cases fully.	5 / 5
Workflow Clarity	The "Scaffold workflow" section lists a clear 3-step sequence (create file, register in opencode.json, restart session) but includes no validation checkpoint such as verifying the plugin actually loaded after restart.	3 / 5
Progressive Disclosure	The single-file body is well-sectioned with no buried references or nesting, but at ~160 lines with an inline hooks API listing it is somewhat past the size where a split reference file would improve organization.	4 / 5
	Total	16 / 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 that clearly states both capability and trigger conditions in third person with concrete, natural trigger phrases. It is only marginally short of the top anchors on specificity and trigger coverage, and the generic "plugin" trigger leaves slight conflict risk with other plugin-creation skills.

Dimension	Reasoning	Score
Specificity	"Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration" names several concrete actions, though "correct API shape" is slightly abstract and coverage has minor gaps.	4 / 5
Completeness	It explicitly answers what ("Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration") and when ("Use when the user asks to 'create a plugin'...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	The quoted triggers "create a plugin", "write a plugin", and "make a plugin that does X" are natural user phrases, but common synonyms like "add a tool" or "extend OpenCode" are missing.	4 / 5
Distinctiveness Conflict Risk	The OpenCode/iPolloWork niche is mostly distinct, but the generic trigger "create a plugin" carries minor overlap risk with skills for other plugin formats (e.g., Anthropic plugins).	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: Devin-AXIS/iPolloWork
Path: .opencode/skills/create-plugin/SKILL.md
Commit: dada31d

Reviewed: 12 hours 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.