Name: updownio
Rating: 53.6 (1 reviews)
Author: membranedev

updownio

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

Quality

60%

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

Quality

Content

63%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 highly actionable, with executable Membrane CLI commands and a well-structured connection workflow that includes polling-based validation and error-state feedback loops. Its weaknesses are some introductory padding and a monolithic layout with no progressive disclosure to separate reference files.

Suggestions

Trim the intro paragraph and prose like 'so you can focus on the integration logic rather than auth plumbing' to respect the token budget.

Move the proxy flag table and detailed clientAction state handling into a separate reference file, keeping SKILL.md as a concise overview with one-level-deep links.

Add at least one fully worked end-to-end example (connect → discover → run) with concrete values to lift actionability toward copy-paste completeness.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense and efficient, but the intro paragraph ('Updown.io is a website monitoring service... used by developers, system administrators, and DevOps engineers') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation that could be trimmed. It is not a 4 because the padding is noticeable rather than minor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a flag table. It is not a 5 because the 'Popular actions' section is thin and some examples rely on placeholders without a fully worked end-to-end example.	4 / 5
Workflow Clarity	The connection setup is a clear sequenced workflow with explicit validation via `--wait` polling and a state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) including a re-poll feedback loop. It is not a 5 because step numbering is loose (an unlabeled 'Step 2' is referenced and a '1b' subsection breaks the sequence).	4 / 5
Progressive Disclosure	The body is well-sectioned with headers but is a single monolithic file with everything inline and no bundle-file references (the proxy flag table and detailed state handling could live in separate reference files). It is not a 4 because, at ~140 lines, no content is split out to one-level-deep references.	3 / 5
	Total	14 / 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 pairs a 'what' with a 'when' clause and anchors triggers to the specific Updown.io product, giving it reasonable completeness and distinctiveness. Its main weakness is vague, generic capability language with none of the natural monitoring/uptime terms users would actually say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Updown.io actions such as 'monitor website uptime, review downtimes, and inspect SSL/metrics'.

Add natural trigger terms users actually say, e.g. 'Use when the user wants to monitor uptime, check downtime, or review website performance with Updown.io'.

Mention the core domain (website/uptime monitoring) so the description is distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Updown.io integration') but its actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete capabilities like monitoring uptime or managing checks. It is not a 3 because no specific concrete actions are listed.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Updown.io data'), matching the score-4 anchor of having both with a somewhat generic 'when'. It is not a 5 because neither the 'what' nor the 'when' is concrete or specific.	4 / 5
Trigger Term Quality	It includes the product name 'Updown.io' and the term 'data', but omits the natural terms users would actually say such as 'uptime monitoring', 'website monitoring', 'downtime', or 'checks'. It is not a 4 because several common natural synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the specific named service 'Updown.io' makes it mostly distinct with minimal conflict risk. It is not a 5 because the generic capability phrasing ('manage data, records, automate workflows') leaves minor overlap risk with other data-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/updownio/SKILL.md
Commit: f484c82

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