CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

87

1.53x
Quality

83%

Does it follow best practices?

Impact

95%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 — 'Manage Joel's task system in Todoist' is a single high-level statement rather than a list of specific capabilities. The extensive trigger list partially compensates by implying capabilities, but explicit action statements 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.'

DimensionReasoningScore

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 triggers. The 'Triggers on:' clause serves as a clear equivalent to 'Use when...' and covers numerous scenarios including the proactive capture case.

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 someone would interact with a task system.

3 / 3

Distinctiveness Conflict Risk

Very distinct — it's specifically about Todoist task management for a named user (Joel), with highly specific trigger terms like 'inbox', 'weekly review', 'groom tasks'. This is unlikely to conflict with other skills due to the narrow, well-defined niche.

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 CLI examples, clear workflows, and well-structured decision trees for agent behavior. Its main weakness is verbosity in the philosophy section, which explains well-known productivity frameworks Claude doesn't need taught, and the monolithic structure that could benefit from splitting reference material into separate files. The Todoist-specific content (priority inversion, filter syntax, adapter commands) is genuinely valuable and well-presented.

Suggestions

Trim the Philosophy section to 2-3 sentences of practical principles rather than explaining GTD/Shape Up/Tiny Habits frameworks — Claude knows these. Keep only the 'What This Means In Practice' bullets.

Split the Todoist CLI reference (Read/Write commands, filters, priority table) into a separate TODOIST_REFERENCE.md and link to it, keeping SKILL.md as an overview with the most common commands inline.

DimensionReasoningScore

Conciseness

The philosophy section (GTD, Shape Up, Tiny Habits explanations) is verbose and explains concepts Claude already knows. The 'Credits' section adds no value. However, the Todoist adapter sections and agent behaviors are reasonably efficient with good use of tables and code blocks.

2 / 3

Actionability

Excellent executable CLI commands throughout, with concrete examples for every operation. The priority table with API inversion detail, filter syntax examples, and specific behavioral rules (capture immediately, process inbox decision tree) are all copy-paste ready and highly specific.

3 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with explicit decision points: inbox processing has a 5-option decision tree, weekly review has numbered steps, ADR→Tasks has a clear loop with cross-referencing. The 'Could the agent just do this?' checkpoint and max-7-items-today rule serve as validation guardrails.

3 / 3

Progressive Disclosure

Content is well-organized with clear headers and logical sections, but it's a monolithic file that could benefit from splitting out the philosophy section, the Todoist CLI reference, and the ADR→Tasks SOP into separate referenced files. At ~200 lines, the inline detail is heavy for a SKILL.md overview.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
joelhooks/joelclaw
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.