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

scaleway

Scaleway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scaleway 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/scaleway/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 a highly actionable, command-driven integration guide with a well-structured connection state machine and explicit feedback loops. Its main weakness is conciseness — a marketing-style intro and a few fluffy asides — plus a dangling "Step 2" reference that breaks the workflow numbering.

Suggestions

Delete or compress the opening marketing paragraph ("Scaleway is a European cloud provider... Developers and businesses use Scaleway..."); Claude already knows what Scaleway is.

Fix the dangling "skip to Step 2" reference by either labeling the downstream section "Step 2" or rewording it to point at a real heading.

Trim interpretive asides like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection."

Dimension	Reasoning	Score
Conciseness	The bulk is lean operational guidance, but the introductory marketing paragraph ("Scaleway is a European cloud provider... Developers and businesses use Scaleway...") and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — install, login, connection ensure, action list/run, proxy — plus a concrete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connection state machine is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the dangling "skip to Step 2" reference points to a section that is never labeled Step 2.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in SKILL.md, but it is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices) that are easy to navigate without needing external references.	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 correctly pairs a Scaleway-specific trigger with a "Use when" clause, but its capability list is generic verb-fluff ("manage data, records, automate workflows") rather than concrete Scaleway actions. Distinctiveness is solid thanks to the named provider, while specificity and trigger coverage are the weak spots.

Suggestions

Replace generic verbs with concrete Scaleway operations, e.g. "Provision instances and volumes, manage buckets and databases, deploy containers and functions."

Expand the trigger phrase to cover natural user requests, e.g. "Use when the user wants to manage Scaleway instances, buckets, databases, or networking."

Tighten "Manage data, records, and automate workflows" — "records" is ambiguous and adds no Scaleway-specific meaning.

Dimension	Reasoning	Score
Specificity	It names the domain (Scaleway) but the listed actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete Scaleway operations like provisioning instances or buckets.	2 / 5
Completeness	Both a "what" (Scaleway integration managing data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Scaleway data") are present, though the what is vague and the when could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Scaleway data" surfaces the core keyword "Scaleway" but misses the natural task phrases users actually say (instances, servers, buckets, databases).	3 / 5
Distinctiveness Conflict Risk	The Scaleway name and "interact with Scaleway data" trigger carve out a distinct niche, but the generic "manage data, records, and automate workflows" phrasing creates minor overlap risk with broad data/automation 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/scaleway/SKILL.md
Commit: f484c82

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