CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-plans

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

Quality

69%

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

Quality

Content

88%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 an extremely lean pointer that delegates all substance to a shared skill file via a clear one-level reference, and the single instruction is unambiguous. The only weaknesses are the absence of any overview or fallback guidance and the reliance on an external path that is not part of the bundle.

DimensionReasoningScore

Conciseness

The body is two lines with zero padding and no explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

"Load and follow the shared skill at `~/.agents/skills/writing-plans/SKILL.md`" is a concrete, executable directive with a specific path, matching mostly-executable guidance. It is not 5 because there is no summary or fallback, and the referenced path is external to the bundle (and not present in this environment), leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-action skill — load and follow a referenced file — and that action is unambiguous, so the simple-skill exception applies. No destructive or batch operations are involved, so no validation cap is triggered.

5 / 5

Progressive Disclosure

The single reference is clearly signaled and exactly one level deep, matching good structure with minor gaps. It is not 5 because the body offers no overview of what the referenced skill contains, and the target path lies outside the bundle where its existence cannot be verified.

4 / 5

Total

18

/

20

Passed

Description

36%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 has a clear, explicit trigger clause but completely fails to state what the skill actually does, leaving a user unable to distinguish its capabilities from the trigger alone. Trigger terms are relevant but miss obvious synonyms like "plan". Adding one sentence of concrete capabilities would raise both completeness and specificity.

Suggestions

Add a 'what' clause naming the skill's concrete actions, e.g. "Creates step-by-step implementation plans with tasks, dependencies, and acceptance criteria" before the "Use when" clause.

Include natural trigger synonyms such as "plan", "implementation plan", or "break down requirements" so users phrasing the need differently still match.

Narrow the trigger from the broad "multi-step task" to something like "planning a coding task" to reduce overlap with general task-management skills.

DimensionReasoningScore

Specificity

"spec or requirements for a multi-step task, before touching code" names a concrete domain but contains no action verbs describing what the skill does, matching the anchor for domain named with minimal actions. It is above score 1 because the domain is specific rather than purely abstract, and below score 3 because no concrete capability is listed.

2 / 5

Completeness

The description has an explicit "Use when..." trigger but entirely omits what the skill does, exactly matching the anchor for only 'when' present without 'what'. It is not 3 because the 'what' is not weakly implied — it is missing altogether.

2 / 5

Trigger Term Quality

"spec", "requirements", and "multi-step task" are phrases users would naturally say, but common variations such as "plan", "implementation plan", or "design doc" are absent, matching the anchor for some relevant keywords with missing synonyms.

3 / 5

Distinctiveness Conflict Risk

The pre-code planning context ("before touching code") gives it some specificity, but "multi-step task" is broad and would overlap with other planning or task-management skills, matching the anchor for somewhat specific with residual overlap risk.

3 / 5

Total

10

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

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