Name: leaseweb
Rating: 55.2 (1 reviews)
Author: membranedev

leaseweb

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

Quality

63%

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/leaseweb/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 delivers strong, executable Membrane CLI guidance with a clearly sequenced connection workflow and explicit state-based checkpoints. Its weaknesses are a padded intro/category list that inflates tokens and a monolithic structure with no reference files splitting off the bulky product catalog.

Suggestions

Trim the introductory 'Leaseweb is a cloud hosting provider...' paragraph and move the 35-item product-category bullet list into a references file (e.g. CATALOG.md) linked from the overview.

Add explicit error-handling guidance for `membrane action run` failures (e.g. inspect the error field, retry, or fall back to `membrane request`) so the run step has its own feedback loop.

Integrate 'Searching for actions' and 'Popular actions' into the main connect-then-run sequence so the end-to-end workflow reads as one coherent path.

Dimension	Reasoning	Score
Conciseness	The operational CLI guidance is efficient, but the opening paragraph explaining what Leaseweb is and the ~35-item inline product-category bullet list are padding Claude largely does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, polling, action list/run, request with a flag table), covering the common cases concretely, but some are templated placeholders (<id>, CONNECTION_ID, QUERY) leaving minor gaps versus a 5.	4 / 5
Workflow Clarity	The connect-to-ready flow is well sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop after the user acts, but error handling after running actions and the loosely attached 'Popular actions' section leave minor gaps.	4 / 5
Progressive Disclosure	Headers provide reasonable structure, but no bundle files exist and the long product-category list is inlined in SKILL.md rather than split out, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly states a distinct Leaseweb niche with an explicit 'Use when' trigger, but its capability verbs are generic ('manage data, records, automate workflows') rather than concrete. Tightening the action list with specific Leaseweb operations would raise specificity and trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Leaseweb actions, e.g. 'List dedicated servers, manage Private Clouds, open support tickets, and fetch invoices'.

Expand trigger terms with synonyms users actually say, such as 'dedicated servers', 'vLeaseweb VMs', 'colocation', or 'Leaseweb API'.

Keep the explicit 'Use when...' clause but pair it with the concrete actions so the 'what' matches the strength of the 'when'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Leaseweb integration') and lists a few action phrases ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, so it sits at the 'domain plus 1-2 actions, not comprehensive' anchor rather than a 4.	3 / 5
Completeness	It supplies both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' clause ('Use when the user wants to interact with Leaseweb data'); the 'when' is present and reasonably explicit but the 'what' is generic, so it is not a 5.	4 / 5
Trigger Term Quality	It surfaces the natural term 'Leaseweb' and a usable trigger phrase ('Use when the user wants to interact with Leaseweb data'), but offers few synonyms or variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named provider ('Leaseweb') gives it a clear niche with low conflict risk, but the generic verb phrases ('manage data, records, automate workflows') leave minor overlap risk, keeping it just below a 5.	4 / 5
	Total	14 / 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/leaseweb/SKILL.md
Commit: f484c82

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