Name: digital-ocean
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

digital-ocean

Digital Ocean integration. Manage Accounts. Use when the user wants to interact with Digital Ocean data.

Quality

57%

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

Quality

Content

57%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 highly actionable with concrete, copy-paste-ready Membrane CLI commands and a clear connection workflow including state-polling checkpoints. Its weaknesses are an unnecessary introductory explanation of what Digital Ocean is, a lack of validation guidance around destructive delete operations, and a monolithic structure that inlines content which could live in reference files.

Suggestions

Remove or trim the opening paragraph explaining what Digital Ocean is; Claude already knows this and it wastes tokens.

Add a validation/feedback step for destructive operations, e.g. confirm-before-delete guidance or a dry-run pattern for delete-* actions, to lift the workflow_clarity cap.

Move the long resource overview and popular-actions table into a reference file (e.g. references/actions.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient concrete CLI commands and tables, but the opening paragraph explains what Digital Ocean is ("cloud infrastructure provider that offers virtual servers, storage, and networking services... popular among developers") which Claude already knows, fitting the mostly-efficient anchor with some unnecessary explanation.	3 / 5
Actionability	The skill provides many copy-paste-ready bash commands covering install, auth, connection, polling, action search/run, and proxy requests, but real action invocations with meaningful parameters (e.g. actually creating a droplet) are only shown generically with `--input '{"key": "value"}'`, leaving minor gaps.	4 / 5
Workflow Clarity	The connection workflow (install → auth → ensure → poll state → search → run) is sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive delete-* actions are listed in the table with no validation or feedback-loop guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The file has clear section headers and is self-contained with no bundle files, but at ~170 lines the large resource taxonomy and 20-row action table are inlined monolithically with no external reference files, fitting the some-structure / could-be-better-organized anchor.	3 / 5
	Total	13 / 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 in third person, names a clear niche, and includes an explicit "Use when" trigger, but its action statement ("Manage Accounts") is vague and trigger terms lack synonyms or resource-specific keywords. It is functional but thin compared to strong examples.

Suggestions

Replace the generic "Manage Accounts" with concrete actions, e.g. "Manage Droplets, volumes, firewalls, domains, and load balancers."

Expand trigger terms with natural variations users say, such as "DigitalOcean", "DO", "droplets", or "Digital Ocean API".

Make the "when" clause more specific, e.g. "Use when the user wants to manage Digital Ocean infrastructure (droplets, volumes, networking, firewalls)."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Digital Ocean integration") but the only action stated is the generic "Manage Accounts", matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" (Digital Ocean integration, Manage Accounts) and an explicit "when" ("Use when the user wants to interact with Digital Ocean data") are present, though the "when" is generic and could be more specific, matching the anchor for both present with improvable "when".	4 / 5
Trigger Term Quality	"Digital Ocean" and "Digital Ocean data" are relevant natural terms a user would say, but common variations, synonyms, or specific resource names (droplets, volumes) are missing, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Digital Ocean integration" is a clearly distinct niche brand unlikely to trigger for unrelated skills, with only minor overlap risk against other cloud-provider skills, fitting the mostly-distinct anchor.	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/digital-ocean/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.