skill-status

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

Quality

78%

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

Quality

Content

77%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, validated multi-phase workflow, but it is monolithic (no bundle files despite referencing ./scripts/octo-state.sh) and carries redundant example reproductions that pad the token budget.

Suggestions

Move the three full dashboard examples and phase-specific routing tables into a separate references/ file, keeping only one representative example inline in SKILL.md.

Provide the referenced ./scripts/octo-state.sh (or a stub) in a scripts/ bundle so the cited executable guidance actually exists, or drop the script reference in favor of inline state parsing.

Trim the Good/Poor comparison blocks in Best Practices, since the Red Flags table and process already convey the same anti-patterns.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and routing tables, but three full dashboard example outputs plus redundant Good/Poor pairs restate material already shown in the process, adding avoidable tokens.	3 / 5
Actionability	Concrete executable bash snippets, explicit routing tables mapping status to suggestions, and copy-ready example dashboards give fully actionable, specific guidance across common cases.	5 / 5
Workflow Clarity	Six phases are clearly sequenced with an explicit validation checkpoint (verify .octo/ exists, "Stop here - do not proceed to Phase 2") and error-routing guidance for the blocked state.	5 / 5
Progressive Disclosure	No references/scripts/assets bundle exists, so the entire ~300-line skill is a single monolithic file with phase-specific routing and examples inlined that could live in separate referenced files.	3 / 5
	Total	16 / 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.

The description is concise, third-person, and explicitly covers both what the skill does and when to use it. It is solid but could name more concrete capabilities (roadmap progress, blockers, routing) and a few more natural trigger terms.

Suggestions

Expand specificity by listing the concrete outputs the skill produces (e.g., roadmap progress, blockers, next-action suggestions) rather than just 'where you are' and 'what to do next'.

Add common trigger synonyms users say aloud, such as 'status', 'what's the status', or 'what have I been working on', to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Show where you are in the workflow and what to do next" names the domain and 1-2 concrete actions but does not enumerate the full set of capabilities (roadmap progress, blockers, next-action routing) covered in the body.	3 / 5
Completeness	Both halves are explicit: "what" ("Show where you are in the workflow and what to do next") and "when" ("use for progress checks and orientation"), satisfying the trigger-clause requirement.	5 / 5
Trigger Term Quality	"progress checks", "orientation", "where you are", "what to do next" are natural user phrases, though common synonyms like "status" or "what's the status" are not explicitly listed.	4 / 5
Distinctiveness Conflict Risk	The workflow-status/orientation niche is mostly distinct with low conflict risk, though it could overlap slightly with general status or task-management 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: nyldn/claude-octopus
Path: skills/skill-status/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.