skill-task-management

Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress

Quality

58%

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

Quality

Content

57%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 actionable with well-structured native-tool examples and clear intent sequences, but it is over-long for its scope, omits validation around destructive git checkpoints, and bundles migration/integration material inline with no progressive-disclosure split. Tightening, adding a validate-before-commit step, and extracting peripheral sections would materially raise the score.

Suggestions

Add a validation checkpoint before the WIP commit (e.g. run `git status`/tests and confirm no unintended files staged) so the destructive/batch git path can score above 3 on workflow clarity.

Extract the migration-from-task-plan-tool and integration-with-other-skills sections into separate reference files linked from the body to reduce the monolithic length and fix the dangling references.

Collapse the three near-identical checkpoint TaskCreate examples into one canonical example plus a short template, and drop the Benefits checklist and closing taglines to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete examples, but padded sections recur — the Benefits checklist, repeated full checkpoint examples (three near-identical TaskCreate blocks), and tagline closers like 'Track everything. Checkpoint frequently.' could be trimmed without losing information.	3 / 5
Actionability	Provides concrete, near copy-paste-ready TaskCreate/TaskUpdate/TaskList calls with realistic field values across adding, checkpointing, resuming, and proceeding; minor gaps are placeholder task IDs and omitted error handling.	4 / 5
Workflow Clarity	Multi-step processes (save, resume, proceed) are clearly sequenced, but the destructive/batch git steps — 'git add .' and WIP commits — run with no validation checkpoint, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Single ~660-line monolithic SKILL.md with no references/ scripts/ assets bundle; sections that read like separate docs (migration guide, integration patterns, full-workflow example) are inlined rather than split out, and in-body references point to nonexistent paths (e.g. skills/blocks/codex-host-adapter.md).	3 / 5
	Total	13 / 20 Passed

Description

58%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 conveys a clear, specific purpose and reasonable distinctiveness, but lacks an explicit 'Use when...' trigger clause and relies on a thin set of natural trigger phrases. Adding concrete trigger conditions and common user phrasings would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to add items to a todo list, save/checkpoint progress, resume previous work, or move to the next step in a workflow.'

Expand natural trigger terms to include phrasings users actually say: 'add to my todos', 'save my progress', 'pick up where I left off', 'what's next'.

Tighten 'delegate work' into a more concrete capability (e.g. 'assign tasks to subagents') or drop it to avoid a slightly vague claim.

Dimension	Reasoning	Score
Specificity	Quotes 'track TODOs, delegate work, and monitor progress' — names the task-management domain with several concrete actions, though 'delegate work' is somewhat generic and coverage of checkpoint/resume actions lives only in the body, not the description.	4 / 5
Completeness	Provides a clear 'what' (manage tasks, track, delegate, monitor) but no explicit 'Use when...' trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes the natural phrase 'track TODOs' but misses common variations users actually say ('add to my todos', 'save my progress', 'resume where I left off') and any file extensions, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Scoped to task/todo management and orchestration, mostly distinct from sibling skills with only minor overlap risk against finish-branch/workflow skills.	4 / 5
	Total	14 / 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
skill_md_line_count	SKILL.md is long (660 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: skills/skill-task-management/SKILL.md
Commit: 242e51d

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