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

statuspal

Statuspal integration. Manage data, records, and automate workflows. Use when the user wants to interact with Statuspal 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/statuspal/SKILL.md

Quality

Content

76%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 executable commands and a clear connection workflow, well-organized into sections. Its main gap is the absence of validation/verification steps for destructive action runs against Statuspal.

Suggestions

Add a verification checkpoint after running actions or proxy POST/PUT/DELETE calls — e.g. re-fetch the resource or inspect the response status to confirm the change landed before reporting success.

Trim marketing-style phrasing ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten the token budget.

For destructive operations, include a brief confirm-or-preview step (such as a dry-run query before a destructive `action run`) to make the workflow safe and reversible.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal padding, but a few promotional sentences ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout — install, login, connection ensure, polling, action list/run, and proxy requests with a complete flags table — covering the common cases with real CLI syntax.	5 / 5
Workflow Clarity	The connection-readiness flow has clear state handling and a feedback loop, but the action-running and proxy workflows — where destructive/batch operations (incidents, services) occur — have no validation or verification of outcomes, which caps the score at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The ~140-line single-file body is well organized into clear sections with no nested references and content appropriately inline; with no bundle files there is no reference structure to navigate, and it exceeds the 50-line simple-skill threshold, so it falls just short of a 5.	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 states what the skill does and when to use it, anchored to a distinct product name. Its weakness is generic action language and a lack of the domain-specific trigger terms (incidents, status pages, outages) users would actually say.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Statuspal operations such as creating and updating incidents, managing services, and posting status updates.

Expand the trigger clause to name the natural terms users say — e.g. 'Use when the user wants to manage Statuspal incidents, services, status pages, or communicate outages and maintenance.'

Drop 'automate workflows' unless specific workflow actions are supported; it reads as templated filler that weakens specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (Statuspal) and lists several actions, but they are generic — 'Manage data, records, and automate workflows' applies to almost any integration rather than concrete Statuspal operations like creating incidents or managing status pages.	2 / 5
Completeness	It provides both a 'what' ('Statuspal integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Statuspal data.'), but the 'when' is vague and lacks concrete trigger phrases, keeping it below a 5.	4 / 5
Trigger Term Quality	The brand name 'Statuspal' and a 'Use when...' trigger are present, but coverage is thin — it misses the domain's natural vocabulary (incidents, status pages, services, outages) and the phrasing 'interact with Statuspal data' is not something users naturally say.	3 / 5
Distinctiveness Conflict Risk	The product name 'Statuspal' gives it a clear, distinct trigger with low conflict risk, but the surrounding 'manage data, records, automate workflows' language is templated and overlaps with sibling Membrane integration skills.	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/statuspal/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.