Names the domain (task/todo management) and lists some actions (create, organize, track) with attributes (priorities, due dates), but doesn't comprehensively list specific operations like 'mark complete', 'set reminders', 'categorize', or 'archive'.

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, and since the 'when' is entirely absent, this scores 1.

Includes natural terms like 'task', 'todo list', 'priorities', 'due dates' that users might say, but misses common variations like 'to-do', 'checklist', 'reminders', 'deadlines', or 'action items'.

Somewhat specific to task management but could overlap with project management skills, calendar skills, or general productivity tools. The mention of 'priorities and due dates' helps narrow scope but isn't distinctive enough.

The content is extremely lean with no unnecessary explanations. It lists features and usage examples without explaining what tasks or todos are, respecting Claude's intelligence.

The skill provides no concrete implementation guidance—no code, no commands, no specific instructions on HOW to create tasks, set priorities, or interact with any system. The usage examples show user inputs but not what Claude should do.

There is no workflow defined. No steps for task creation, no process for managing todos, no validation or feedback loops. It's purely a feature list without any operational guidance.

The content is well-organized with clear sections (Features, Usage Examples), but there are no references to additional documentation for implementation details that would clearly be needed for a functional skill.