CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-writing-plans

Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning

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 ./.claude/skills/skill-writing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 delivers exceptional actionability — complete code, exact commands, and expected outputs throughout — with strong per-task validation checkpoints. Its weaknesses are redundancy (duplicated example, compliance theatrics, repeated checklists) and a monolithic single-file layout that inlines material better kept in reference files.

Suggestions

Drop the ~75-line fully worked example (or move it to a reference file) — it duplicates the task template nearly step-for-step and is the single largest conciseness cost.

Trim performative padding: the 'MANDATORY COMPLIANCE' block, the octopus activation line, and 'The Bottom Line' restate the checklist without adding guidance.

Move the Claude Octopus integration and plan-storage details (including the version-specific v2.1.10 notes) into a separate reference file, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The core material (granularity table, task template, checklists) is tight, but several sections pad the document: the 'MANDATORY COMPLIANCE' block, the octopus activation line, a ~75-line fully worked example that duplicates the task template step-for-step, 'The Bottom Line' repeating the checklist, and version-specific plan-storage details ('Claude Code v2.1.10'). Mostly efficient but noticeably loose — more than the minor trimming of level 4, less severe than level 2.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: exact file paths, complete TypeScript test and implementation code, exact commands ('npm test tests/validators/email.spec.ts') with expected outputs ('PASS: 3/3 tests passed'), and ready commit commands. The worked example covers the common case completely.

5 / 5

Workflow Clarity

The task template embeds explicit validation checkpoints (run test expecting FAIL, run expecting PASS, then commit) and the checklist validates the finished plan, but the overall plan-creation procedure is presented as reference-style sections rather than an ordered sequence, and there is no explicit feedback loop for revising a produced plan. Above level 3 because checkpoints inside tasks are explicit; below level 5 due to the implicit top-level sequence.

4 / 5

Progressive Disclosure

The body is a single ~340-line file with good headers, but it inlines content that belongs in separate reference files (the complete worked example, the Claude Octopus integration and plan-storage details), and its only file reference ('skills/blocks/engineering-method-selection.md') is a plugin path not present in the bundle — no references/, scripts/, or assets/ directories exist. Structure is decent, so above level 2, but the split is not appropriate for level 4.

3 / 5

Total

15

/

20

Passed

Description

62%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 concise, uses third-person imperative voice, and answers both what and when with an explicit use-for clause. Its main weaknesses are limited action coverage and missing natural trigger phrases, which currently live only in the separate trigger field.

Suggestions

Add 1-2 more concrete actions to the description itself, e.g. 'documenting exact file paths, complete code, and test/verification steps per task', to raise specificity beyond two actions.

Fold natural trigger phrases users would actually say into the description, such as 'plan how to implement X', 'create an implementation plan', or 'break down a feature into tasks', instead of keeping them only in the trigger field.

DimensionReasoningScore

Specificity

"Create zero-context implementation plans with bite-sized tasks" names the domain and 1-2 concrete actions, but does not state what the plans contain (exact file paths, complete code, verification steps), so coverage is not comprehensive. It is above level 2 (actions are named, not generic) but below level 4 (only a couple of specific actions are listed).

3 / 5

Completeness

It has a clear what ("Create zero-context implementation plans with bite-sized tasks") and an explicit when clause ("use for multi-step feature planning"), but the when is generic and lacks concrete trigger phrases. Not level 5 (no explicit trigger phrases like 'when the user asks to plan a feature'); clearly above level 3 since the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

Keywords "implementation plans" and "multi-step feature planning" are relevant, but common natural variations users would say — "plan how to implement X", "break down this feature into tasks" — appear only in the separate trigger field, not in the description. This matches the 'some relevant keywords but missing common variations' anchor rather than level 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"zero-context implementation plans with bite-sized tasks" carves a fairly distinct planning niche with limited overlap risk against general task-management or refactoring skills. Minor overlap remains with closely related planning/decomposition skills, so it fits 'mostly distinct' rather than level 5's clear niche with distinct triggers.

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.

Validation — 15 / 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

nyldn/claude-octopus

Path

.claude/skills/skill-writing-plans/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.