task-list

List tasks by directory with progress and visual indicators

Quality

40%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/product-design/skills/task-list/SKILL.md

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive specification for a task listing command with good structure and clear output examples. However, it lacks executable code for the actual implementation and includes some verbose sections that explain concepts Claude already understands. The workflow is clear but the content could be more actionable with actual parsing code.

Suggestions

Add executable Python/shell code for parsing task file headers and scanning directories instead of abstract descriptions

Remove or condense the 'Implementation Tips for Claude Code' section - Claude knows about caching and sorting

Move the detailed output format examples to a separate FORMATS.md file and reference it

Add a reference to where the task file format/schema is documented

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary sections like 'Implementation Tips for Claude Code' that explain caching and sorting concepts Claude already knows. The extensive output format examples could be condensed.	2 / 3
Actionability	Provides clear execution instructions and examples, but lacks actual executable code. The 'Execution Instructions for Claude Code' section describes what to do abstractly rather than providing concrete implementation. No actual parsing code or file system operations are shown.	2 / 3
Workflow Clarity	Clear 5-step execution sequence with explicit directory scanning order. Error handling section provides recovery guidance. For a listing/display command, the workflow is appropriately simple and unambiguous.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in one file when the detailed output format examples could be referenced separately. No external references are provided for related commands or task file format specifications.	2 / 3
	Total	9 / 12 Passed

Description

17%

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 description is too terse and lacks critical context for skill selection. It fails to explain what 'tasks' means (todos? build tasks? async operations?), provides no trigger guidance for when Claude should select it, and uses abstract terminology instead of natural user language.

Suggestions

Add a 'Use when...' clause with specific trigger terms like 'show tasks', 'list todos', 'project progress', 'task status by folder'

Clarify what 'tasks' refers to (e.g., 'TODO comments in code', 'project task files', 'build tasks') to reduce ambiguity

Include natural keywords users would say, such as file extensions (.todo, .tasks), common phrases ('what needs to be done', 'pending items'), or tool names if applicable

Dimension	Reasoning	Score
Specificity	Names a domain (tasks/directories) and some actions (list, progress, visual indicators), but lacks comprehensive detail about what specific actions can be performed or what 'tasks' means in this context.	2 / 3
Completeness	Only addresses 'what' at a surface level and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger guidance, which per rubric caps this at maximum 2, but the 'what' is also weak.	1 / 3
Trigger Term Quality	Uses technical/abstract terms like 'visual indicators' and 'progress' without natural keywords users would say. Missing common variations like 'todo', 'task list', 'show tasks', 'project status', or file extensions.	1 / 3
Distinctiveness Conflict Risk	'Tasks by directory' provides some specificity, but 'progress' and 'visual indicators' are vague enough to potentially overlap with project management, file listing, or status reporting skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: jpoutrin/product-forge
Commit: 0ebe7ae

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