digital-ocean-integration_skill

Overview

This skill integrates Digital Ocean into your workflow, letting you manage droplets, volumes, load balancers, firewalls, domains, and other resources. It uses the Membrane CLI to handle authentication and API calls so you can focus on operations and automation. The skill exposes common actions for listing, retrieving, creating, and deleting resources, and supports raw proxy requests for custom API needs.

How this skill works

The skill connects to Digital Ocean through a Membrane connector. Membrane manages the OAuth/credential lifecycle, pagination, and error handling, and exposes actions you can run via the Membrane CLI. When built-in actions are insufficient, the skill allows forwarding arbitrary HTTP requests to the Digital Ocean API through Membrane's proxy with automatic auth injection.

When to use it

• List or inspect Digital Ocean resources (droplets, volumes, images, domains, firewalls, load balancers).
• Create or delete infrastructure objects programmatically from a script or automation pipeline.
• Run ad hoc Digital Ocean API calls not covered by pre-built actions.
• Build integrations that must avoid handling raw API keys or token refresh logic.
• Discover available actions and input schemas before writing custom calls.

Best practices

• Install and authenticate the Membrane CLI; let Membrane handle credentials instead of storing API keys locally.
• Use pre-built Membrane actions for common tasks to benefit from pagination and error handling.
• Run membrane action list with intent=QUERY to discover existing actions and input schemas before coding.
• Use membrane request for custom endpoints and rely on Membrane to inject authentication headers.
• Prefer structured JSON input when running actions to avoid parsing issues and ensure predictable behavior.

Example use cases

• Quickly list all droplets to inventory running servers during an incident.
• Create a droplet and attach a block volume as part of a deployment script.
• Retrieve details of a specific firewall or load balancer to verify settings.
• Delete unused volumes and snapshots to reclaim storage costs.
• Proxy a specialized Digital Ocean API endpoint to fetch metrics or region-specific data not exposed by built-in actions.