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

80%

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

Quality

Content

65%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 highly actionable with concrete CLI commands and well-sequenced SOPs, but it carries padding (known-framework philosophy, credits) and is a monolithic file with no progressive disclosure or validation checkpoints for destructive/batch task operations.

Suggestions

Move the GTD/Shape Up/Tiny Habits philosophy into a short reference file or condense to one line each, since Claude already knows these frameworks.

Add an explicit confirm-before-delete checkpoint and a verify step to the inbox-triage and delete workflows so destructive/batch operations have validation.

Extract the Todoist Adapter CLI reference and filter syntax into a separate REFERENCE.md, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational guidance, but the Philosophy section explains GTD, Shape Up, and Tiny Habits — frameworks Claude already knows — and the Credits section adds padding that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready `todoist-cli` commands, priority/schedule mapping tables, and concrete SOPs cover the common cases comprehensively.	5 / 5
Workflow Clarity	Inbox processing and weekly review are clearly numbered, but destructive (delete) and batch (inbox triage) operations lack explicit validation/confirmation checkpoints, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Good section headers provide structure, but the skill is a ~270-line monolith with no reference files; the lengthy CLI/filter reference material is inlined rather than split into one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

95%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 is strong: third-person voice, explicit what-and-when, and an exhaustive set of natural trigger phrases tied to a clearly scoped personal Todoist workflow. The only minor gap is that concrete capabilities are expressed as trigger terms rather than a dedicated action list.

Dimension	Reasoning	Score
Specificity	Names the domain ("Manage Joel's task system in Todoist") and lists several concrete actions via triggers ("add a task", "complete", "mark done", "weekly review", "groom tasks"), though they are framed as triggers rather than a comprehensive capability list, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("Manage Joel's task system in Todoist") and when ("Triggers on: ...") with concrete trigger phrases, satisfying the top anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural phrases users would actually say ("what's on my list", "what do I need to do", "remind me to", "today's tasks") plus synonyms and a passive-capture condition, matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	Scoped to a named person and a specific tool ("Joel's task system in Todoist") with highly specific triggers, giving a clear niche and minimal conflict risk.	5 / 5
	Total	19 / 20 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: joelhooks/joelclaw
Path: skills/task-management/SKILL.md
Commit: d952451

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