CtrlK
BlogDocsLog inGet started
Tessl Logo

plan

Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate Codewhale’s native plan state; do not build a parallel planner.

61

Quality

72%

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/plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured instruction skill with a clear sequenced workflow and verification checkpoint; it only lacks a touch more prescriptive detail in the output shape.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete instructional steps ('Restate the goal and constraints', 'Write the plan into Codewhale's native plan/Work surface') with minor gaps — the output shape could be more prescriptive.

4 / 5

Workflow Clarity

A clearly ordered 5-step sequence with verification marking and an authorization checkpoint; just short of explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with well-organized sections and no need for external references, qualifying for the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

58%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 is specific and distinct, but it omits an explicit trigger ('Use when...') clause, leaving the 'when to use' only weakly implied and capping completeness.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when the task is understood enough to sequence steps into an implementation plan').

Include common synonyms a user might say, such as 'break down the task', 'sequence the work', or 'implementation plan'.

Lead with the concrete capability before the orchestration constraint so the what is immediately scannable.

DimensionReasoningScore

Specificity

Names the planning domain and several concrete actions ('ordered implementation plan with dependencies and verification', 'Orchestrate Codewhale's native plan state') with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant terms like 'implementation plan' and 'dependencies' appear, but it lacks the natural trigger phrases and synonyms a user would actually say when reaching for this skill.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to Codewhale's native plan/Work state and explicitly forbidding a parallel planner gives it a clear niche with only minor overlap risk.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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.