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.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 — it says 'manage Joel's task system' but doesn't explicitly enumerate the concrete capabilities (create, complete, list, review, groom). The trigger terms effectively compensate by implying these actions, but explicit capability listing would strengthen it.
Suggestions
Add explicit capability statements before the triggers, e.g., 'Creates tasks, marks tasks complete, lists tasks by date/project, performs weekly reviews and grooming in Todoist.'
| 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 contextual triggers like 'when actionable items emerge from other work' and 'when Joel mentions something he needs to do in passing'. | 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 and cover many common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it's specifically tied to Todoist and a specific user (Joel), with task-management-specific trigger terms. Very unlikely to conflict with other skills given the clear niche of personal task management in Todoist. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 strong, highly actionable skill with excellent workflow clarity and concrete CLI examples. Its main weakness is verbosity in the philosophy section, which explains frameworks Claude already knows, and the monolithic structure that could benefit from splitting into referenced sub-files. The operational content — CLI commands, priority conventions, agent behaviors, anti-patterns, and the ADR→Tasks SOP — is exemplary.
Suggestions
Remove or drastically condense the GTD/Shape Up/Tiny Habits summaries — keep only the 'What This Means In Practice' bullets, which are the actionable distillation.
Consider splitting the CLI reference (Read/Write/Filters) into a separate TODOIST-CLI.md reference file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The philosophy section explaining GTD, Shape Up, and Tiny Habits is largely unnecessary — Claude knows these frameworks. The 'What This Means In Practice' distillation is useful, but the framework summaries themselves are verbose padding. The operational sections (CLI commands, agent behaviors, SOPs) are well-written and efficient. | 2 / 3 |
Actionability | Excellent executable guidance throughout: complete CLI commands with flags, concrete examples of good vs bad tasks, specific decision trees for inbox processing, clear priority mapping table with API inversion noted, and copy-paste ready filter queries. The ADR→Tasks SOP is fully concrete. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with validation checkpoints: inbox processing has a 5-option decision tree per item, weekly review has explicit ordered steps, ADR→Tasks has a clear loop with cross-referencing. The 'Could the agent just do this?' gate before task creation is an effective checkpoint. The capture→confirm→schedule flow is well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a long monolithic file (~250 lines of substantive content). The philosophy section, CLI reference, agent behaviors, and SOPs could benefit from being split into separate referenced files. However, sections are well-signaled and navigable within the single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
ce9ca8e
- Reviewed
Table of Contents
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.