skill-status

Show where you are in the workflow and what to do next — use for progress checks and orientation

Quality

72%

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 ./.claude/skills/skill-status/SKILL.md

Quality

Content

77%

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

The body is highly actionable with a clear phased workflow and explicit stop-checkpoint, but it is verbose due to repeated example/restatement blocks and makes no use of progressive disclosure despite its length. Splitting reference material into bundle files and trimming redundancy would raise both dimensions.

Suggestions

Move the three full Example dashboard outputs and the status/phase routing tables into a references/ file (e.g. EXAMPLES.md) and link to them one level deep to improve progressive disclosure.

Delete the Best Practices Good/Poor blocks and the redundant Example outputs that merely restate the Phase 4 template to recover tokens.

Consolidate the Red Flags, Quick Reference, and Bottom Line sections, which largely restate When to Use and The Process.

Dimension	Reasoning	Score
Conciseness	The body is actionable but padded: the Phase 4 dashboard template is restated in Example 1, 2, and 3, and the Best Practices Good/Poor blocks repeat steps already shown in The Process, so it is mostly efficient with notable redundancy rather than lean.	2 / 3
Actionability	It gives concrete executable commands ("./scripts/octo-state.sh read_state", git log invocations), explicit routing tables mapping status to suggestions, and copy-paste dashboard templates with placeholders, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The Process is a clearly sequenced Phase 1–6 flow with an explicit checkpoint in Phase 1 ("Stop here - do not proceed to Phase 2" when .octo/ is absent), and the read-only nature means missing destructive-validation loops is not penalized.	3 / 3
Progressive Disclosure	Sections are well organized, but the ~480-line SKILL.md is monolithic with no bundle files; large example outputs and routing tables that could be offloaded are inline, and the only referenced paths are runtime domain files rather than signaled one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 cleanly answers both what and when with an explicit trigger clause, but its action list and trigger vocabulary are narrow. It is solid but not maximally specific or distinctive.

Suggestions

Add concrete capabilities to the description (e.g., "displays phase, position, blockers, and next-action routing") to lift specificity toward level 3.

Broaden trigger terms to the natural phrasings users actually say ("status", "where am I", "what's next", "roadmap progress") to improve trigger coverage.

Tighten the niche by anchoring to the .octo/Double-Diamond workflow so it is less likely to fire for generic task-management requests.

Dimension	Reasoning	Score
Specificity	"Show where you are in the workflow and what to do next" names the domain and a couple of actions, but does not enumerate multiple concrete capabilities, so it falls short of the level-3 multi-action anchor.	2 / 3
Completeness	It states what the skill does ("Show where you are... and what to do next") and provides an explicit "use for progress checks and orientation" trigger clause, satisfying both what and when.	3 / 3
Trigger Term Quality	"progress checks", "orientation", and "what to do next" are natural phrases, but common variations a user would actually say ("status", "where am I") are missing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The workflow-status niche is real, but "progress checks" and "orientation" are generic enough to overlap with task-management or roadmap skills, so it is not a clearly conflict-free niche.	2 / 3
	Total	9 / 12 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: nyldn/claude-octopus
Path: .claude/skills/skill-status/SKILL.md
Commit: 9f39f0c

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