Name: status-hero
Rating: 56.8 (1 reviews)
Author: membranedev

status-hero

Status Hero integration. Manage data, records, and automate workflows. Use when the user wants to interact with Status Hero data.

Quality

65%

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

Quality

Content

67%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 body delivers strong executable CLI guidance with a well-sequenced connection workflow and clear sectioning. It is held back by a padded intro explaining concepts Claude already knows and by a lack of Status-Hero-specific action examples or post-run validation checkpoints.

Suggestions

Trim the opening descriptive paragraph about what Status Hero is and who uses it; Claude already knows this and it competes with context budget.

Add at least one concrete Status Hero action example (e.g. listing/running a check-in or report action) so guidance is product-specific rather than generic CLI usage.

Add a verification/check step after running actions or proxy requests for batch or destructive operations to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI snippets, but the opening paragraph explains what Status Hero is and who uses it (concepts Claude largely knows), and the proxy/agent-type sections include lightly padded explanatory prose that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands cover install, login, connection, action search/run, and proxy requests with a flag table; minor gaps include no worked example of an actual Status Hero action id or input payload.	4 / 5
Workflow Clarity	The connection setup is a clearly sequenced flow (ensure -> poll --wait -> handle clientAction states -> READY) with state-driven checkpoints and error branches; it lacks an explicit validate-after-run feedback loop for batch/destructive action results.	4 / 5
Progressive Disclosure	Content is well-sectioned with a clear overview, working-with section, popular actions, and best practices, and no bundle files are used so everything is one-level; the Status Hero Overview entity list and proxy flag table are slightly inlined reference material that could live separately.	4 / 5
	Total	15 / 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 identifies the product and includes an explicit Use-when trigger, satisfying the core completeness bar. It is weak on Status-Hero-specific action specificity and natural trigger-term synonyms, leaning on generic 'manage data, records, automate workflows' language.

Suggestions

Replace generic verbs with Status-Hero-specific actions, e.g. 'Retrieve check-ins, answers, goals, and reports; manage teams and users'.

Add natural user trigger phrases such as 'status updates', 'daily check-ins', 'standup reports', or 'team status'.

Make the 'when' clause concrete, e.g. 'Use when the user asks about daily check-ins, team status reports, or Status Hero records'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Status Hero integration') and a couple of concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not Status-Hero-specific, with no comprehensive coverage of what the integration actually does.	3 / 5
Completeness	It provides a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Status Hero data'); the 'when' is present but could be more specific about trigger scenarios.	4 / 5
Trigger Term Quality	'Status Hero data' is a relevant keyword, but natural synonyms a user would say (status updates, check-ins, daily standup, team reports) are missing, and the only trigger phrase is the generic 'interact with Status Hero data'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Status Hero) gives it a clear niche and low conflict risk with unrelated skills, though the generic 'manage data, records' phrasing leaves minor overlap with other data-integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/status-hero/SKILL.md
Commit: f484c82

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