CtrlK
BlogDocsLog inGet started
Tessl Logo

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

68

Quality

81%

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

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.

A highly actionable, well-structured skill with copy-paste-ready examples. The main weakness is the scaffold workflow's lack of a validation/verification step before declaring the plugin ready.

Suggestions

Add a verification checkpoint to the Scaffold workflow, e.g. 'After restart, confirm the tool appears / runs a no-op call before telling the user it works.'

Consider moving the Anthropic-compatibility comparison table and the full multi-tool example into a separate reference file to keep SKILL.md lean.

Trim the small explanatory phrasing around the minimal shape so every token earns its place.

DimensionReasoningScore

Conciseness

Mostly lean with terse key rules and a compact comparison table, but the Anthropic-compatibility section and a fully worked multi-tool example add mild over-explanation that could be trimmed, fitting anchor 4 rather than 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript (minimal shape, available hooks, multi-tool example with real fs/promises logic) covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The Scaffold workflow gives a clear 3-step sequence but lacks any validation checkpoint (e.g., verify the plugin loads after restart), and the skill performs file writes and config edits, matching anchor 3 with its implicit-checkpoint gap.

3 / 5

Progressive Disclosure

Well-organized into clearly signaled sections in a single file with no bundle references; minor gaps because the full multi-tool example and Anthropic-compat table could be externalized, fitting anchor 4 rather than 5.

4 / 5

Total

16

/

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, specific description that clearly communicates what the skill does and when to trigger it, with concrete user-facing phrases. Minor room to add synonyms and file-extension triggers for broader coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration') with only minor coverage gaps, fitting anchor 4 rather than 5 which demands a more comprehensive enumeration.

4 / 5

Completeness

Explicitly states both what it does (scaffold plugin with API shape, tools, hooks) and when to use it with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('create a plugin', 'write a plugin', 'make a plugin that does X') but omits synonyms like 'extend' or file-extension triggers, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('OpenCode plugin for iPolloWork') with distinct create/write/make-a-plugin triggers and minimal overlap with other skills.

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
Devin-AXIS/iPolloWork
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.