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

Blog Docs Log in Get started

vultr

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

Quality

62%

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/vultr/SKILL.md

Quality

Content

67%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 well-structured and gives concrete, executable CLI guidance with a solid connection-state workflow, but it carries some redundant or background explanation and stays monolithic where a reference file could offload detail.

Suggestions

Trim the introductory 'what Vultr is / similar to AWS' paragraph and de-duplicate the action-list command between 'Popular actions' and 'Searching for actions'.

Fix the dangling 'skip to Step 2' reference by labeling the discovery/run sections as explicit numbered steps, and add a verify step after running actions.

Move the proxy flag table and detailed clientAction field reference into a separate reference file, linked once from the body, to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ('Vultr is a cloud hosting provider... It's similar to AWS or Digital Ocean') plus redundancy between the 'Popular actions' and 'Searching for actions' sections, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, executable commands for every stage (install, login, connection ensure/get, action list/run, request) plus a flag table, but examples rely on placeholders (CONNECTION_ID, <actionId>, QUERY) rather than a fully copy-paste-ready real invocation, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear state-driven sequence with a feedback loop (poll until READY, retry after CLIENT_ACTION_REQUIRED), but the dangling 'skip to Step 2' reference (no labeled Step 2) and absence of a unified end-to-end checklist are minor validation/sequencing gaps.	4 / 5
Progressive Disclosure	The body is well-organized with clear section headers and no nested references, but at ~150 lines it keeps detail inline (the proxy flag table, the full clientAction sub-bullets) with no one-level-deep references to split content, so it does not reach the 'clear overview with well-signaled references' anchor.	4 / 5
	Total	15 / 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 clear and distinct thanks to the named Vultr platform and an explicit trigger clause, but its capabilities are stated generically rather than as concrete Vultr actions, and it lacks natural keyword variations users would say.

Suggestions

Replace generic verbs with concrete Vultr capabilities, e.g. 'Deploy and manage virtual machines, block storage, bare metal servers, and Kubernetes clusters'.

Expand the trigger phrase with natural synonyms users say, e.g. 'Use when the user wants to manage Vultr virtual machines, VPS instances, block storage, or DNS.'

Avoid the vague 'Manage data, records, and automate workflows' phrasing, which over-claims and overlaps with unrelated skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Vultr integration') but the actions it lists — 'Manage data, records, and automate workflows' — are generic verbs rather than concrete Vultr capabilities (e.g. deploy VMs, manage block storage), matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vultr data') are present; the 'when' is explicit but could be more specific, fitting the 'has both what and when; when could be more explicit' anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	It includes the natural product keyword 'Vultr' and an explicit 'Use when' trigger, but misses common variations and synonyms a user might actually say (virtual machines, VPS, cloud servers, instances, block storage).	3 / 5
Distinctiveness Conflict Risk	The named platform 'Vultr' gives it a clear, distinct trigger unlikely to fire for unrelated skills, but the generic 'data, records, workflows' wording leaves minor overlap risk with other cloud-provider integration 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/vultr/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.