CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-creator

Scaffold a local Codewhale plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review.

64

Quality

76%

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 ./crates/tui/assets/skills/plugin-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is a tight, highly actionable workflow with explicit validation checkpoints and a complete manifest example, held back from a perfect conciseness score only by repeated time-sensitive version pinning outside a deprecated section.

Suggestions

Move the 'v0.9.1' version pinning into a clearly labeled 'Version constraints' or 'Deprecated/old patterns' section, or state the behavior without hard-coding the version, so conciseness is not penalized for time-sensitive detail.

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable, but it repeatedly pins a time-sensitive version number ('Codewhale v0.9.1') outside any 'old patterns' or 'deprecated' section, which the guideline says should penalize conciseness; it does not reach the 'every token earns its place' anchor.

2 / 3

Actionability

It provides concrete, copy-paste-ready commands ('/plugin validate <plugin-name>', '/plugin show', '/plugin enable', '/plugin trust', '/skills inspect', '/plugin list') and a complete executable plugin.toml example, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The 8-step Workflow is clearly sequenced with explicit validation checkpoints (validate → show → enable → run the shown trust confirmation → enable again → verify via /skills inspect and /plugin list), including a feedback loop for error recovery.

3 / 3

Progressive Disclosure

The skill is under roughly 50 lines, has no need for external references, and is well-organized into clear sections ('# Plugin Creator', '## Workflow'), which the guideline says lets progressive disclosure score 3 with just well-organized sections; no bundle files exist so no nested references to verify.

3 / 3

Total

11

/

12

Passed

Description

67%

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 is specific and occupies a clear niche, but it omits an explicit 'when to use' trigger and leans on technical terms over natural user phrasing, capping completeness and trigger quality.

Suggestions

Add an explicit trigger clause such as 'Use when a user wants to create a local Codewhale plugin bundle' to raise completeness to 3.

Include natural phrasings a user might say (e.g. 'create a plugin', 'package Skills', 'Codewhale plugin') alongside the technical terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Scaffold a local Codewhale plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does but lacks any 'Use when...' clause or equivalent trigger, and the guideline explicitly caps completeness at 2 when explicit trigger guidance is missing.

2 / 3

Trigger Term Quality

Terms like 'plugin bundle', 'versioned manifest', 'namespaced Skills', and 'trust review' are relevant but fairly technical/jargon-heavy and miss common natural variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The niche — local Codewhale plugin bundle scaffolding with trust review — is specific and clearly distinguishable, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

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
Hmbown/CodeWhale
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.