task-management

Manage Joel's task system in Todoist. Triggers on: 'add a task', 'create a todo', 'what's on my list', 'today's tasks', 'what do I need to do', 'remind me to', 'inbox', 'complete', 'mark done', 'weekly review', 'groom tasks', 'what's next', or when actionable items emerge from other work. Also triggers when Joel mentions something he needs to do in passing — capture it.

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable and well-structured task management skill with excellent CLI examples, clear decision frameworks, and thoughtful workflow design including the human/machine surface separation. Its main weakness is verbosity in the philosophy section and the monolithic structure — at ~250 lines with no bundle files, it consumes significant context window space where the reference tables and methodology background could be split out.

Suggestions

Condense the Philosophy section to 3-5 bullet points of actionable principles, removing the book summaries (e.g., 'Capture everything immediately. Process to next physical action. < 2 min = do it now. Weekly review is sacred.').

Extract the Todoist Filters, Priority Convention table, and Schedule Mapping table into a separate TODOIST-REFERENCE.md file, referenced from the main skill.

Dimension	Reasoning	Score
Conciseness	The philosophy section (GTD, Shape Up, Tiny Habits) is verbose and explains concepts that are general knowledge rather than actionable specifics. The 'What This Means In Practice' section is more useful but the theoretical framing adds ~40 lines of context that could be condensed to a few bullet points. The rest of the skill (CLI commands, agent behaviors, SOPs) is reasonably efficient.	2 / 3
Actionability	Excellent concrete CLI commands throughout — every operation has a copy-paste-ready example. The priority table with API inversion is a critical detail. Agent behaviors have specific scripts and confirmation patterns. The ADR→Tasks SOP is step-by-step with clear decision criteria.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced: inbox processing has a 5-option decision tree, weekly review has numbered steps with specific actions, ADR→Tasks has a clear loop with cross-referencing. The 'Could the agent just do this?' checkpoint before task creation is an effective validation gate. The capture→confirm pattern provides feedback.	3 / 3
Progressive Disclosure	The skill is a monolithic document at ~250 lines. The philosophy section, Todoist filter reference, priority/schedule mapping tables, and the ADR→Tasks SOP could each be separate referenced files. No bundle files exist to offload this content, and no references to external files are provided for the detailed subsections.	2 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that the 'what it does' portion is somewhat thin — 'Manage Joel's task system in Todoist' is a high-level summary without listing specific concrete capabilities. The extensive trigger phrases partially compensate by implying capabilities, but explicit action listing would strengthen it.

Suggestions

Expand the opening sentence to list specific concrete actions, e.g., 'Create tasks, mark tasks complete, list tasks by date/project, perform weekly reviews, and groom the inbox in Joel's Todoist system.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Todoist task management) and implies actions like adding tasks, completing tasks, and reviewing, but doesn't explicitly list concrete capabilities like 'create tasks, mark tasks complete, list tasks by date, perform weekly reviews.' The actions are mostly embedded in trigger phrases rather than stated as capabilities.	2 / 3
Completeness	The description answers both 'what' (manage Joel's task system in Todoist) and 'when' with extensive explicit trigger guidance including specific phrases and even the proactive trigger of capturing actionable items mentioned in passing. The 'Triggers on:' clause serves as a clear 'Use when' equivalent.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say: 'add a task', 'create a todo', 'what's on my list', 'today's tasks', 'remind me to', 'mark done', 'weekly review', 'what's next'. These are highly natural phrases that cover many variations of how a user would express task-related needs.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — it's specifically tied to Todoist, a named user (Joel), and task management. The trigger terms are clearly task/todo-oriented and unlikely to conflict with other skills like document processing, coding, or general productivity tools.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: joelhooks/joelclaw
Commit: 2ca3686

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