todo-management

Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.

Quality

74%

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 ./skills/todo-management/SKILL.md

Quality

Content

60%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 well-structured and actionable with clear sequenced workflows and properly signaled one-level-deep references. Its main weakness is verbosity: heavy repetition between the main sections and the Quick Reference recap inflates the document well past what Claude needs.

Suggestions

Remove the 'Quick Reference' section or reduce it to a single compact table — it duplicates the 8 operations, task states, and script commands already covered in full above, adding ~150 lines of padding.

Move the four 'Progress Tracking Formats', 'Common Mistakes', and 'Troubleshooting Quick Fixes' into the existing reference files so SKILL.md stays a lean overview.

Tighten abstract operation steps like 'Take Action' and 'Apply Strategies' into concrete sub-steps so every step is executable rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The ~670-line body is noticeably verbose with substantial repetition — the Quick Reference section restates the 8 operations, task states, and the script commands already detailed earlier in the document, padding the token budget without adding new information.	2 / 5
Actionability	Provides mostly executable guidance — concrete script commands ('python scripts/update-todos.py --init task-list.md') and copy-paste before/after markdown examples — though some operation steps remain abstract ('Take Action', 'Apply Strategies') without specifics.	4 / 5
Workflow Clarity	Each of the 8 operations is a clearly sequenced numbered process with checkpoints like 'Verify Completion: Output exists, quality checked' and 'Verify Completeness', plus a momentum checklist; minor validation gaps keep it just below a 5.	4 / 5
Progressive Disclosure	References to state-management-guide.md and progress-reporting-guide.md are clearly signaled with markdown links and one level deep (both files exist), and sections are well-organized; however, substantial content that could live in those references (4 tracking formats, common mistakes, troubleshooting) is inlined in SKILL.md.	4 / 5
	Total	14 / 20 Passed

Description

88%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.

A strong description that clearly states concrete capabilities and provides an explicit 'Use when' trigger clause. It is held back only slightly by trigger-term breadth and minor overlap risk with generic task-management phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (manages task states, updates, reports progress, identifies blockers, maintains momentum) and 'when' ('Use when tracking skill development, coordinating work, or reporting progress') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'tracking skill development', 'coordinating work', 'reporting progress' — but coverage is somewhat narrow and misses common synonyms/variants a user might naturally invoke.	4 / 5
Distinctiveness Conflict Risk	The skill-development tracking niche is mostly distinct, but broad triggers like 'coordinating work' and 'reporting progress' create minor overlap risk with general task-management skills.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (677 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/todo-management/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.