work-status

Shows WORK progress and TASK status. Use when the user asks about WORK list, WORK progress, TASK status, or pipeline status (e.g., "WORK list", "WORK-01 progress", "show status").

Quality

82%

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

Quality

Content

86%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.

A tight, well-organized simple skill that gives concrete file paths and a clear output template without padding. The main gaps are implicit connections: how to compute the status counts shown in the display format, and an explicit step tying the reads to the formatted output.

Suggestions

Add a brief note on how the display counts are derived (e.g., count TASKs in PROGRESS.md to produce "5/5 completed" and the emoji state).

Add an explicit final step linking the read phase to the output, e.g. "Format the gathered data per the Display Format section below."

Clarify what the emoji states (✅/🔄/⬜) map to in terms of the Status Values table so output is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; every section (How to Check, Status Values, Display Format, Arguments) earns its place.	5 / 5
Actionability	Concrete file paths (works/WORK-LIST.md, works/WORK-NN/PROGRESS.md, works/WORK-NN/TASK-NN_result.md) and a display template make guidance executable, but how to derive the count/emoji summaries (e.g. "5/5 completed") is left implicit.	4 / 5
Workflow Clarity	The three read steps are clearly sequenced by escalating detail (index -> WORK -> TASK), but the link between gathering the data and producing the Display Format output is implicit rather than stated as a step.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external bundle references (none exist), organized into clear well-labeled sections, which satisfies the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

78%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.

A concise, well-structured description that clearly answers both what the skill does and when to trigger it, with natural user-facing trigger phrases. The only weakness is a somewhat generic action verb and one term ("pipeline status") with minor overlap risk.

Dimension	Reasoning	Score
Specificity	"Shows WORK progress and TASK status" names the domain and one concrete action (showing status/progress), but the action is generic and coverage is not comprehensive.	3 / 5
Completeness	Clearly states what it does ("Shows WORK progress and TASK status") and when to use it with concrete trigger phrases, explicitly answering both what and when.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("WORK list", "WORK progress", "TASK status", "pipeline status", "show status") including quoted example phrases a user would say, though a few variants like "task list" are missing.	4 / 5
Distinctiveness Conflict Risk	The WORK-NN/TASK-NN framing and file-based status niche is mostly distinct, though the term "pipeline status" carries minor overlap risk with CI/CD-related skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: davepoon/buildwithclaude
Path: plugins/agents-uc-taskmanager/skills/work-status/SKILL.md
Commit: c9856ea

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