Name: statusio
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

statusio

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/statusio/SKILL.md

Quality

Content

75%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 highly actionable, executable Membrane CLI commands with a clear connection workflow and state-based validation, though it opens with background prose Claude doesn't need and has slightly inconsistent step numbering.

Suggestions

Trim the opening background paragraph ("Status.io is a status page system...") and the overview tree, which restate concepts Claude already knows.

Normalize the workflow numbering — label the action-running section as "Step 2" explicitly and reconcile the "1b" sub-step so the sequence reads cleanly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude doesn't need — e.g. the opening "Status.io is a status page system that allows companies to communicate incidents..." background and the overview tree — matching the score-3 anchor "Mostly efficient but includes some unnecessary explanation or could be tightened."	3 / 5
Actionability	The content is fully executable and copy-paste ready across install, login, connection ensure, action list/run, and proxy requests, with concrete flags and a JSON-input example — matching the score-5 anchor "Fully executable; copy-paste ready code or commands; specific examples cover the common cases."	5 / 5
Workflow Clarity	There is a clear install → auth → connect → search → run/proxy sequence with explicit state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the step numbering is inconsistent (references to "Step 2" and "1b" without clearly labeled matching sections), fitting score 4 rather than the cleanly-checkpointed score 5.	4 / 5
Progressive Disclosure	No bundle files exist, but the SKILL.md is well-organized with clear section headers and the content (CLI usage, proxy flags) is appropriately inline for a single-file integration skill — matching score 4 "Good structure; most content is appropriately placed" rather than score 5 (which expects well-signaled one-level-deep references) or score 3 (disorganized inline content).	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly identifies Status.io and includes an explicit "Use when" trigger, but the capability phrasing is generic ("manage data, records, and automate workflows") rather than naming concrete Status.io operations like incidents, components, or subscribers.

Suggestions

Replace generic verbs with concrete Status.io actions, e.g. "Create and update incidents and maintenance windows, manage components, metrics, and subscribers."

Expand the trigger clause with user-natural phrases and synonyms, e.g. "Use when the user wants to manage status pages, post incident updates, or work with Status.io components and metrics."

Tie the trigger more tightly to Status.io-specific concepts (incidents, maintenance, subscribers) to reduce overlap with other integration skills.

Dimension	Reasoning	Score
Specificity	The description names the Status.io domain but the actions "Manage data, records, and automate workflows" are minimal and generic, with no concrete operations like creating incidents or managing components — matching the score-2 anchor "Names the domain but actions are minimal or generic" rather than the score-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Status.io data") are present, but the "when" is generic and could be more specific, matching the score-4 anchor rather than score 3 (where "when" is missing) or score 5 (where triggers are concrete and varied).	4 / 5
Trigger Term Quality	The primary natural keyword "Status.io" is present ("Use when the user wants to interact with Status.io data"), but coverage is thin — missing common variations, synonyms, or related terms a user might say, fitting the score-3 anchor "Some relevant keywords but missing common variations or synonyms."	3 / 5
Distinctiveness Conflict Risk	Naming "Status.io" explicitly gives it a clear niche with minimal conflict risk, but the generic verb phrasing ("Manage data, records, and automate workflows") likely overlaps with sibling Membrane integration skills, placing it at score 4 rather than the fully-distinct score 5.	4 / 5
	Total	13 / 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/statusio/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.