skill-status

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

Quality

63%

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

63%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 content is highly actionable with a clear phased workflow and concrete commands, but it is padded with redundant sections and keeps all material inline with no progressive disclosure. Trimming duplication and splitting examples/reference material into separate files would materially raise the score.

Suggestions

Remove the redundant 'Example Outputs' section (it duplicates the Phase 1 and Phase 4 templates) and the 'Quick Reference' table (it restates 'When to Use') to cut padding.

Move the routing tables, phase-specific guidance, and best-practices/red-flags material into separate reference files linked one level deep from SKILL.md.

Collapse 'Best Practices' and 'Red Flags - Don't Do This' into a single concise do/don't list to eliminate overlap.

Dimension	Reasoning	Score
Conciseness	The ~500-line body is noticeably verbose: 'Example Outputs' duplicates the Phase 1 dashboard, 'Quick Reference' restates 'When to Use', and 'Best Practices'/'Red Flags' overlap — several padded, redundant sections beyond what Claude needs.	2 / 5
Actionability	Guidance is fully executable: concrete commands (`./scripts/octo-state.sh read_state`, `cat .octo/ROADMAP.md`, `git log --oneline --since="7 days ago"`), specific slash-command routing, and worked output templates cover the common cases copy-paste ready.	5 / 5
Workflow Clarity	Phases 1-6 are clearly sequenced with an explicit .octo/ existence checkpoint ('Stop here - do not proceed to Phase 2'), but there is no validate->fix->retry feedback loop, which keeps it just below the top anchor.	4 / 5
Progressive Disclosure	Sections are well-headed, but no bundle files exist and everything (routing tables, examples, best practices, quick reference) is inlined in one ~500-line file rather than split into one-level-deep references, matching the anchor for good structure with content that should be separate kept inline.	3 / 5
	Total	14 / 20 Passed

Description

62%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 is clear and covers what and when at a solid level, but it is light on concrete trigger phrases and only names a couple of actions. Adding natural user phrases ("status", "what's next", "where am I") and one more concrete capability would lift specificity and trigger quality.

Suggestions

Add natural trigger phrases users say — e.g. 'Use when the user asks "status", "what's next", or "where am I"' — to improve trigger_term_quality.

Expand the action list to mention the dashboard, blockers, and next-action routing so specificity reaches comprehensive coverage.

Tighten the when clause from 'progress checks and orientation' to explicit trigger conditions for a stronger completeness score.

Dimension	Reasoning	Score
Specificity	The description names the domain ("where you are in the workflow") and two concrete actions ("show where you are", "what to do next") but omits dashboard, blockers, roadmap, and routing — matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Show where you are in the workflow and what to do next") and when ("use for progress checks and orientation"), but the when could list concrete trigger phrases — matching the anchor where both are present yet when could be more explicit.	4 / 5
Trigger Term Quality	"progress checks and orientation" plus "where you are" give some natural keywords, but common variations users actually say ("status", "what's next", "where am I") are absent from the description, fitting the anchor for some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The status/orientation niche is mostly distinct, but "what to do next" overlaps with task-management and routing skills, fitting the anchor for mostly distinct with minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (504 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-status/SKILL.md
Commit: bc76e7c

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.