Name: statuscake
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

statuscake

Statuscake integration. Manage Tests, ContactGroups, Users. Use when the user wants to interact with Statuscake data.

Quality

73%

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

Quality

Content

73%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 is action-oriented with a strong, well-validated connection workflow and clean section structure. Its main weaknesses are a padded introductory paragraph that explains monitoring concepts Claude already knows and minor command redundancy.

Suggestions

Cut the introductory paragraph explaining what website monitoring is and who uses it; Claude already knows this, so lead with the integration specifics.

Dedupe the 'membrane action list' invocations into one canonical form and reference it, instead of repeating the command across sections.

Add one worked end-to-end example that chains connection ensure -> action list -> action run with concrete IDs to close the placeholder gap.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but opens by explaining what website monitoring is ('checks websites for downtime and performance issues... ensure their sites are always online') and repeats the 'action list' invocation three times in slightly different forms.	3 / 5
Actionability	Provides copy-paste ready executable commands for install, login, connection ensure, action discovery, action run, and proxy requests, plus a flag reference table; the minor gap is that placeholders like <actionId> and CONNECTION_ID are never tied together in a single worked end-to-end example.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll -> act -> poll feedback loop, which is a textbook validation/error-recovery pattern.	5 / 5
Progressive Disclosure	Well-organized into clear headed sections with no nested references and no monolithic wall of text, though at ~145 lines the proxy flag table and auth details could plausibly live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

73%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 covers what and when with an explicit trigger clause and a distinct niche, scoring well on completeness and distinctiveness. It is held back by a generic action verb and the absence of natural synonyms users might say.

Suggestions

Replace the generic verb 'Manage' with specific operations, e.g. 'Create, update, and list Tests, ContactGroups, and Users'.

Expand the 'Use when' clause with concrete trigger phrases users actually say, e.g. 'Use when the user wants to manage Statuscake uptime tests, pagespeed checks, SSL tests, or contact groups'.

Add natural synonyms and file/extension cues (e.g. 'uptime monitoring', 'downtime alerts') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Statuscake domain and three concrete entity types ('Manage Tests, ContactGroups, Users'), but the verb 'Manage' is generic rather than listing several distinct specific actions, so it is not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' (Statuscake integration managing Tests, ContactGroups, Users) and 'when' ('Use when the user wants to interact with Statuscake data'), though the 'when' clause is generic rather than carrying concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the primary natural keyword 'Statuscake' and an explicit 'Use when the user wants to interact with Statuscake data' trigger, but misses common synonyms a user might say such as 'monitoring', 'uptime', or 'downtime checks'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear proper-noun niche ('Statuscake') with distinct triggers, making overlap with other skills minimal.	5 / 5
	Total	16 / 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/statuscake/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.