todo-write

TodoWrite-driven plan that the agent commits to before generation.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/atoms/todo-write/SKILL.md

Quality

Content

100%Weight 40%Scale 1-3

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 concise, well-organized instruction skill with concrete behavioral rules and an implicit validation checkpoint tying completion to a landed artifact. It earns full marks as a simple, single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The ~16-line body is lean, assumes Claude's competence, and does not explain concepts Claude already knows; the only mild padding ('Open Design daemon', 'atom') is brief and clarifies tool-name flexibility, keeping it at the 'lean and efficient' anchor rather than score-2.	3 / 3
Actionability	As an instruction-only skill it gives concrete, specific behavioral rules ('one verb per todo', 'mark complete only after the matching artifact lands', 'surface blockers as todos — never silently skip'); per the scoring notes, absence of code is not penalized when guidance is this actionable.	3 / 3
Workflow Clarity	It is a simple single-purpose skill under 50 lines whose single action (commit to a numbered plan via TodoWrite before writing artifacts) is unambiguous, and 'mark complete only after the matching artifact lands' functions as a validation checkpoint; the simple-skills note allows a 3 here.	3 / 3
Progressive Disclosure	At under 50 lines with no external references needed and no bundle files present, the well-organized single-section body meets the 'under 50 lines, well-organized sections' allowance for a score of 3.	3 / 3
	Total	12 / 12 Passed

Description

35%Weight 40%Scale 1-3

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 identifies the skill's purpose and tool but lacks any explicit 'use when' trigger guidance and relies on a technical term rather than natural user keywords. It is moderately specific but not complete or well-triggered.

Suggestions

Add an explicit trigger clause, e.g. 'Use when starting any non-trivial multi-step workflow before generating artifacts.'

Replace tool jargon with natural user language such as 'plan', 'task list', or 'break down the work' so it triggers on what users actually say.

Name a second concrete action (e.g. tracking progress against the plan) to lift specificity beyond a single described behavior.

Dimension	Reasoning	Score
Specificity	It names the domain (planning) and tool (TodoWrite) and a concrete act ('a numbered plan that the agent commits to before generation'), but it does not list multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the vague score-1 or the multi-action score-3.	2 / 3
Completeness	It states what the skill does (commit to a plan before generation) but has no 'Use when...' trigger clause, which the guidelines cap at 2; it is not the score-1 because a 'what' is present, and not score-3 because 'when' is entirely absent.	2 / 3
Trigger Term Quality	The only keyword is 'TodoWrite', a tool/technical term a user would not naturally utter; there are no natural user phrases ('help me plan this task', 'make a todo list'), so it matches the 'no natural keywords; technical jargon' anchor.	1 / 3
Distinctiveness Conflict Risk	'Planning' is generic enough to overlap with other skills, though the explicit TodoWrite/tool tie gives it a partial niche; it sits at the 'somewhat specific but could still overlap' anchor rather than a clearly-conflict-free score-3.	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: plugins/_official/atoms/todo-write/SKILL.md
Commit: f2760fd

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.