Name: statuspage-io
Rating: 55.2 (1 reviews)
Author: membranedev

statuspage-io

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

Quality

62%

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/statuspage-io/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 content is a solid, actionable CLI integration guide with good sequencing and a genuine validation/feedback loop for connection readiness. Its main weaknesses are a small amount of unnecessary background, placeholder-only examples, and inconsistent step cross-references.

Suggestions

Remove the opening background paragraph about what Statuspage.io is, since Claude already knows this, and trim the 'auth plumbing' commentary.

Fix the broken workflow cross-references: define 'Step 2' (or relabel it to the 'Searching for actions' section) and rename '1b' to a consistent step number.

Add one fully-worked example with a real connection id and a concrete intent query (e.g. creating an incident) so the placeholders become copy-pasteable.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete CLI commands, but opens with background Claude already knows ('Statuspage.io is a service that allows companies to communicate incidents...') and includes light commentary ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands across install, login, connection, action discovery, action execution, and proxying, plus a concrete flags table; minor gaps remain since CONNECTION_ID, actionId, and QUERY are placeholders without a worked end-to-end example.	4 / 5
Workflow Clarity	There is a clear install -> authenticate -> connect -> discover -> run sequence with an explicit state-branching feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, check CONFIGURATION_ERROR), but cross-reference labels are inconsistent ('skip to Step 2' with no Step 2, '1b' with no '1a').	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clearly headed sections with no nested references, though at ~140 lines some material (the full clientAction spec, the proxy flag reference table) could be split into reference files to keep the overview lean.	4 / 5
	Total	15 / 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 identifies the product niche clearly and includes an explicit 'Use when' trigger, but its capability language is generic and lacks concrete Statuspage.io-specific actions or richer trigger synonyms. It reads as a templated integration description rather than a tailored one.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Statuspage.io actions such as 'create and update incidents, manage components, and schedule maintenance'.

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'when the user mentions incidents, maintenance windows, components, or status updates'.

Add file/term synonyms (e.g. 'status page', 'incident updates') to broaden natural-language matching.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Statuspage.io integration') but the actions are minimal and generic ('Manage data, records, and automate workflows') with no concrete Statuspage.io operations such as creating incidents or scheduling maintenance.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Statuspage.io data') are present, though the 'when' could be more specific about incident/maintenance scenarios.	4 / 5
Trigger Term Quality	The product name 'Statuspage.io' appears as the main keyword, but common natural variations and synonyms a user might say (incidents, maintenance, components, status updates) are missing.	3 / 5
Distinctiveness Conflict Risk	The 'Statuspage.io' product name gives it a clear niche with minimal conflict risk, but the generic 'manage data, records, and automate workflows' phrasing overlaps with sibling Membrane integration skills that follow the same template.	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/statuspage-io/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.