Name: ovhcloud
Rating: 59.2 (1 reviews)
Author: membranedev

ovhcloud

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

Quality

68%

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/ovhcloud/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 delivers strong, copy-paste-ready CLI guidance organized into a clear workflow with connection-state checkpoints, but it opens with unnecessary background prose and could offload reference material into bundle files.

Suggestions

Trim or remove the introductory paragraph about OVHcloud being a European provider and the sparse 'OVHcloud Overview' bullet list; Claude does not need this background to run the integration.

Add an explicit validation/verification checkpoint after running actions or proxy requests (e.g. check the `output`/response status and surface errors before proceeding), which would lift workflow clarity.

Move the proxy request flag table and action-run details into a `references/` file referenced from SKILL.md to improve progressive disclosure and reduce inline reference bulk.

Dimension	Reasoning	Score
Conciseness	The bulk is tight, executable commands, but the opening paragraph ('European cloud provider... data sovereignty and competitive pricing') and the sparse 'OVHcloud Overview' list explain context Claude largely does not need, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Commands are copy-paste ready throughout (install, login, connection ensure, action list/run, request with a full flag table) and cover the common cases with appropriate placeholders, matching 'fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→poll→search→run sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but actual API operation results lack an explicit validation checkpoint.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-sectioned with clear headers and a one-level external docs link, though the proxy/action reference material could be split into separate files.	4 / 5
	Total	16 / 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 answers both 'what' and 'when' with a clear OVHcloud-scoped trigger, but its action language is generic boilerplate rather than concrete OVHcloud capabilities, and trigger keyword coverage is thin.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete OVHcloud capabilities drawn from the body, e.g. 'Manage dedicated servers, IPs, load balancers, and orders; run and automate OVHcloud API workflows.'

Broaden the trigger clause to include service-level terms users would actually say, e.g. 'Use when the user wants to manage OVHcloud dedicated servers, IPs, load balancers, or place and track orders.'

Add a file/extension or product-name synonym where natural (e.g. 'OVH' / 'ovh.com') to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the OVHcloud domain plus a few action categories ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete OVHcloud capabilities, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Both 'what' (OVHcloud integration, manage data/records, automate workflows) and 'when' (Use when the user wants to interact with OVHcloud data) are explicit, but the single trigger scenario and generic 'what' keep it below the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The natural keyword 'OVHcloud' appears in an explicit 'Use when' clause, but there is essentially one term with no synonyms or service-level variations, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'OVHcloud integration' is a clearly brand-scoped niche with minimal conflict risk, though the generic action verbs ('manage data, records, automate workflows') create minor overlap with other cloud-provider skills.	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/ovhcloud/SKILL.md
Commit: f484c82

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