CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Create or improve codewhale skills. Use when the user wants a new skill, wants to update an existing skill, or needs guidance on when a skill should be a skill versus MCP, hooks, tools, or a plugin scaffold.

Quality

84%

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

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

The body is a lean, well-structured instructional skill with concrete templates, an explicit decision rubric for skill-vs-MCP-vs-plugin, and a real validation step and checklist. Its remaining headroom is an error-recovery loop after validation and a worked example of a complete skill.

Suggestions

Add a short feedback loop after the Validation Checklist spelling out what to do when a check fails (fix, re-run the failing check, re-load via /skills), which would lift workflow_clarity to the top anchor.

Include one compact worked example of a finished small skill (frontmatter plus a few body lines) to make the guidance fully copy-paste-ready and lift actionability.

If the skill grows, move the discovery-path precedence list and plugin-bundle mechanics into a references/ file referenced at exactly the point they matter.

DimensionReasoningScore

Conciseness

The body is lean and operational (discovery paths, minimum-shape template, writing rules, workflow, checklist) with no general-concept padding; even the explanatory parts are runtime-specific facts Claude cannot know elsewhere, so every token earns its place.

5 / 5

Actionability

Guidance is mostly executable — a copy-paste-ready SKILL.md template, a concrete surface-choice decision list, and specific checklist items like "`SKILL.md` starts with `---`" — but a worked example of a finished real skill is absent, leaving a minor gap to fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

The numbered Creation Workflow includes an explicit validation step ("Validate by loading the skill through `/skills` or by running the relevant skill discovery tests") plus a Validation Checklist, but there is no error-recovery feedback loop for what to do when checks fail, which keeps it below the top anchor.

4 / 5

Progressive Disclosure

Sections are well organized, no content is inlined that clearly belongs in separate files, and the body correctly instructs deferring bulky detail to references/scripts/assets; with no actual bundle files and minor remaining organization headroom (e.g., the discovery-path list could become a reference if the skill grows), it sits at good structure with minor gaps.

4 / 5

Total

17

/

20

Passed

Description

82%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 cleanly answers both what the skill does and when to use it, with explicit trigger phrases and good niche separation from MCP/hooks/plugins. The only weakness is moderate action specificity — just two verbs — leaving the capability list less comprehensive than the strongest examples.

DimensionReasoningScore

Specificity

"Create or improve codewhale skills" names the domain with exactly two concrete actions, matching the anchor for domain plus 1-2 actions that is not comprehensive; it does not list several specific actions, so it stays below the next level.

3 / 5

Completeness

A clear what ("Create or improve codewhale skills") is paired with an explicit "Use when..." listing three concrete trigger situations, clearly answering both what and when; it is not merely a present-but-could-be-more-explicit when clause.

5 / 5

Trigger Term Quality

Natural phrases like "new skill", "update an existing skill", and the ecosystem terms "MCP, hooks, tools, or a plugin scaffold" give good coverage, but common variations such as "make a skill" or "SKILL.md" are missing, so it is one step below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"codewhale skills" is a clear niche and the description explicitly distinguishes the skill surface from MCP, hooks, tools, and plugin scaffolds, giving distinct triggers with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Hmbown/Codewhale

Path

crates/tui/assets/skills/skill-creator/SKILL.md

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.