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

upcloud

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/upcloud/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 content is highly actionable with executable Membrane CLI commands and a well-structured connection workflow including a state-machine with validation. It loses points mainly for some unnecessary background explanation and minor workflow-numbering inconsistencies.

Suggestions

Remove the introductory paragraph explaining what UpCloud is; Claude already knows this and it competes with the token budget.

Fix the step numbering so the 'Step 2' reference resolves to a labeled Step 1, and reconcile the '1b' subsection with the surrounding numbered flow.

Add a verify step before running actions (e.g. confirm the action's inputSchema/outputSchema before invocation) to strengthen the workflow's validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ('UpCloud is a cloud service provider that offers virtual servers...') and padded phrasing like 'so you can focus on the integration logic rather than auth plumbing', matching anchor 3 ('Mostly efficient but includes some unnecessary explanation').	3 / 5
Actionability	It provides copy-paste-ready executable CLI commands throughout (login, connection ensure, action list/run, request) with explicit flags, JSON parameters, and a flag table, matching anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with an explicit state-machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling checkpoints, matching anchor 4 ('Clear sequence with most checkpoints present'); not 5 because of a numbering inconsistency ('Step 2' referenced without a labeled Step 1, section '1b') and the search/run steps lack a verify-before-run checkpoint.	4 / 5
Progressive Disclosure	The single-file skill is well organized into clearly labeled sections (Overview, Connecting, Searching, Running actions, Proxy, Best practices) with easy navigation, matching anchor 4 ('Good structure; most content is appropriately placed'); not 5 because at ~155 lines with an inlined resource/action list it is longer than the simple-skill threshold and could offload detail to reference files.	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 is short and includes an explicit 'Use when...' trigger with a named provider, which gives it a clear niche. Its main weakness is vague capability language ('Manage data, records, and automate workflows') that lacks concrete actions and trigger-term variety.

Suggestions

Replace generic verbs with concrete UpCloud actions, e.g. 'Create and manage servers, firewall rules, storage, and managed databases'.

Add trigger-term synonyms such as 'virtual servers', 'VPS', 'floating IPs', and 'UpCloud API' to broaden natural-language matching.

Tighten the 'when' clause to mention specific intents, e.g. 'Use when the user wants to manage UpCloud servers, networks, or storage'.

Dimension	Reasoning	Score
Specificity	It names the UpCloud domain but the actions 'Manage data, records, and automate workflows' are minimal and generic, matching anchor 2 ('Names the domain but actions are minimal or generic') rather than 3 since no concrete operations like creating servers or firewalls are listed.	2 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with UpCloud data'), matching anchor 4 ('Has both what and when; when could be more explicit'); it falls short of 5 because the 'what' is vague rather than concrete.	4 / 5
Trigger Term Quality	It surfaces the natural keyword 'UpCloud' in the trigger clause 'Use when the user wants to interact with UpCloud data', but offers only one relevant term with no synonyms, file extensions, or common variations, fitting anchor 3 ('Some relevant keywords but missing common variations or synonyms').	3 / 5
Distinctiveness Conflict Risk	Naming the specific provider 'UpCloud' gives it a clear niche with minimal conflict risk, fitting anchor 4 ('Mostly distinct; minor overlap risk'); not 5 because the generic 'manage data, records' phrasing could weakly overlap with other data 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/upcloud/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.