Name: uptime-robot
Rating: 64 (1 reviews)
Author: membranedev

uptime-robot

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

Quality

76%

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/uptime-robot/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 is highly actionable with ready-to-run CLI commands and a solid connection workflow, but it is slightly verbose in explaining the product and lacks explicit validation feedback loops around batch/destructive operations.

Suggestions

Trim the introductory 'Uptime Robot is a website monitoring service...' paragraph since Claude already knows the product; lead with the integration task.

Add an explicit validate-and-retry checkpoint before running batch or destructive actions (e.g. dry-run or confirm count before 'action run' / proxy DELETE).

Reconcile the 'Step 2' / 'Step 1b' numbering, which references a non-existent 'Step 1a'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but sections like 'Uptime Robot is a website monitoring service...' explain what the product is, and the connection-state branching is verbose relative to what Claude needs.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, with concrete flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks and polling (BUILDING -> READY / CLIENT_ACTION_REQUIRED), but there are no explicit validation checkpoints for the destructive/batch actions accessible via 'action run' and proxy DELETE requests.	4 / 5
Progressive Disclosure	Well-organized into clear sections (install, auth, connect, actions, proxy, best practices) with no bundle files present, so all content is appropriately inline; minor gaps are the duplicated action-discovery commands and the orphaned 'Step 2' reference with no Step 1a.	4 / 5
	Total	16 / 20 Passed

Description

78%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 is product-specific, uses third person, and supplies both capabilities and an explicit 'Use when' trigger. It is concise and avoids fluff, though the trigger language and action list are slightly generic.

Suggestions

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to check uptime, manage monitors, or configure alert contacts.'

Replace generic 'Manage data, records, and automate workflows' with Uptime-Robot-specific actions like 'create monitors, manage alert contacts, and review uptime logs.'

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('Manage data, records, and automate workflows'), which lists several specific activities with only minor gaps in coverage.	4 / 5
Completeness	Has both a clear 'what' and an explicit 'Use when the user wants to interact with Uptime Robot data' trigger, though the 'when' is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Includes natural user-facing terms like 'Uptime Robot', 'data', 'records', and 'workflows', though it lacks common synonyms or variants users might say.	4 / 5
Distinctiveness Conflict Risk	The product-specific name 'Uptime Robot' creates a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/uptime-robot/SKILL.md
Commit: f484c82

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