CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

50

Quality

53%

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 ./.cursor/skills/writing-plans/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 body is highly actionable and workflow-clear, with concrete templates and an explicit TDD validation loop. Its only weakness is minor repetition that slightly undercuts conciseness.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence ("DRY. YAGNI. TDD. Frequent commits."), but repeats the DRY/YAGNI/TDD/commits mantra in both the Overview and Remember sections, so it could be tightened rather than earning the fully-lean top anchor.

2 / 3

Actionability

It provides exact file paths ("Modify: exact/path/to/existing.py:123-145"), complete code blocks, and exact commands with expected output ("Run: pytest ... Expected: FAIL"), making the task template copy-paste ready.

3 / 3

Workflow Clarity

The Task Structure lays out a clear TDD sequence (write failing test → verify it fails → implement → verify it passes → commit) with explicit validation checkpoints and expected outputs, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the ~110-line skill is self-contained and organized into clearly-labeled sections (Overview, Bite-Sized Task Granularity, Plan Document Header, Task Structure, Remember, Execution Handoff), which is appropriate single-file organization.

3 / 3

Total

11

/

12

Passed

Description

22%

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 a well-formed trigger clause but is fundamentally incomplete because it never states what the skill does, leaving the 'what' half of its job unspecified. Its trigger terms are natural but thin on variation.

Suggestions

Lead with what the skill does, e.g. "Writes comprehensive, bite-sized implementation plans from a spec or requirements..." before the 'Use when' trigger.

Add a few natural trigger variations users might actually say, such as "spec", "requirements", "design doc", "plan an implementation", "break down a task".

Tighten distinctiveness by anchoring to the planning niche explicitly (e.g. "before any code is written") to reduce overlap with executing/brainstorming skills.

DimensionReasoningScore

Specificity

The description names no concrete actions at all — it is purely a trigger clause ("Use when you have a spec or requirements for a multi-step task, before touching code") and never says what the skill does, matching the 'vague or no actions' anchor.

1 / 3

Completeness

The 'when' is explicit and strong ("Use when..."), but the 'what does this do' is entirely absent — the description never mentions it writes plans — which matches the 'missing what OR when' anchor.

1 / 3

Trigger Term Quality

It includes natural terms a user might say ("spec", "requirements", "multi-step task", "touching code"), but coverage is limited with few common variations, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

"spec or requirements for a multi-step task, before touching code" carves a moderately specific niche, but it overlaps with adjacent planning/execution skills (the body itself references brainstorming and executing-plans), fitting the 'somewhat specific but could overlap' anchor.

2 / 3

Total

6

/

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
revokslab/ShipFree
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.