todo-tracker

Persistent TODO scratch pad for tracking tasks across sessions. Use when the user asks to add, list, complete, remove, or summarize tasks in a portable workspace Markdown file. Uses stable task IDs and exact matching; heartbeat reporting is opt-in and count-only.

Quality

100%

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

Quality

Content

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

A tightly written, action-oriented skill body with executable commands, an explicit approval-gated destructive workflow, and clean one-level-deep reference to the bundled script. No padding and no missing validation steps.

Dimension	Reasoning	Score
Conciseness	The body is lean: it states runtime requirements and operational rules without explaining what a TODO list is, and the dense prose (counter bootstrapping, fail-closed checks, lock handling) is non-obvious domain detail that earns its tokens.	5 / 5
Actionability	Every command is concrete and copy-paste ready, e.g. 'TODO_FILE="$PWD/TODO.md" bash "{baseDir}/scripts/todo.sh" add high "Review launch checklist"', and the file format is shown as a runnable Markdown block covering the common cases.	5 / 5
Workflow Clarity	The Remove flow is an explicitly sequenced destructive workflow with a validation checkpoint: preview without removing, surface the stable ID, then run only after approval with '--confirm T000001', plus lock-stale recovery guidance.	5 / 5
Progressive Disclosure	The body is a well-sectioned overview (File and Script, Stable Identity, Commands, Heartbeat, File Format) that delegates execution to one clearly-signaled, one-level-deep bundle file (scripts/todo.sh, present and referenced via {baseDir}).	5 / 5
	Total	20 / 20 Passed

Description

100%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, third-person description that concretely states capabilities and provides an explicit trigger clause matching natural user phrasing. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete actions — 'add, list, complete, remove, or summarize tasks' — plus the mechanics ('stable task IDs and exact matching'), giving comprehensive coverage of what the skill does.	5 / 5
Completeness	It explicitly answers 'what' ('Persistent TODO scratch pad for tracking tasks across sessions ... stable task IDs and exact matching; heartbeat reporting is opt-in and count-only') and 'when' ('Use when the user asks to add, list, complete, remove, or summarize tasks') with concrete triggers.	5 / 5
Trigger Term Quality	'asks to add, list, complete, remove, or summarize tasks' are exactly the natural phrases a user would say, covering the full verb set a user invokes for a todo tracker.	5 / 5
Distinctiveness Conflict Risk	The niche is specific (portable Markdown task file with stable IDs and exact matching, opt-in count-only heartbeat) with distinct triggers, giving minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jdrhyne/agent-skills
Path: clawdbot/todo-tracker/SKILL.md
Commit: 439cd3a

Reviewed: 3 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.