Digital Ocean
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a legitimate DigitalOcean integration, but it can grant persistent delegated cloud access and exposes create/delete infrastructure actions without clear confirmation boundaries in the provided text.
Install only if you trust Membrane with your DigitalOcean account connection. Use least-privileged access where possible, pin or verify the CLI before installing, and require explicit confirmation for any action that creates, changes, or deletes cloud resources.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or overly broad agent action could create costs, delete infrastructure, or cause service downtime in the user's DigitalOcean account.
The skill exposes cloud provisioning and deletion actions. In the provided text, these high-impact operations are not paired with explicit user confirmation, scope limits, or recovery guidance.
| Create Droplet | create-droplet | Create a new Droplet. | ... | Delete Droplet | delete-droplet | Delete an existing Droplet by ID |
Require explicit user approval before any create, update, or delete action; scope actions to specific projects/resources; and prefer read-only use unless the user clearly requests a change.
Granting the connection may allow ongoing access to DigitalOcean resources through Membrane until revoked.
The integration relies on delegated DigitalOcean access managed by Membrane. This is purpose-aligned, but it is sensitive account authority that may persist.
Membrane handles authentication and credentials refresh automatically
Use the least-privileged DigitalOcean access available, review the granted scopes, and revoke the Membrane/DigitalOcean connection when no longer needed.
Future package changes or a compromised package source could affect what the CLI does on the user's machine.
The setup uses a global npm install with the moving latest tag, so the installed CLI version and code are not pinned or reviewed in the supplied artifacts.
npm install -g @membranehq/cli@latest
Install only from trusted sources, consider pinning a known CLI version, and avoid running the install with unnecessary administrator privileges.
DigitalOcean account metadata, action requests, and results may pass through or be mediated by Membrane's service.
DigitalOcean actions and authentication are routed through Membrane's CLI/account connection flow. This is disclosed and purpose-aligned, but it introduces a third-party gateway for sensitive cloud operations.
Requires network access and a valid Membrane account ... membrane connection ensure "https://www.digitalocean.com/" --json
Review Membrane's security and privacy terms before connecting production DigitalOcean accounts, and avoid sending unnecessary sensitive data through the integration.