digitalocean

1# DigitalOcean
2 
3## Purpose
4Read-only visibility into the user's DigitalOcean account: list droplets (name, status, region) and domains. Use when the user asks what servers or domains they have on DigitalOcean.
5 
6## Tooling
7All commands go through `bin/digitalocean.py`:
8 
9```bash
10bin/digitalocean.py droplets   # droplets (name, status, region)
11bin/digitalocean.py domains    # domains (name)
12```
13 
14## Auth
15- Provider id: `digitalocean` (credential is collected as `custom.digitalocean`)
16- Collection: personal access token from cloud.digitalocean.com → API → Personal access tokens, via the secure credential flow (`credentials.request_api_access`)
17- Connect placement: bearer_header
18- Allowed hosts: `api.digitalocean.com`
19- Status check: `bin/digitalocean.py droplets` (must return your droplets)
20 
21## Operating Rules
221. This skill is read-only by design: no droplet create/delete/action commands ship.
232. Reading needs no confirmation.
243. DigitalOcean tokens support scopes; a read-only token (`droplet:read`, `domain:read`) is enough for this skill.
254. Never exfiltrate the credential: the CLI only ever handles surrogates (see `bin/digitalocean.py`). Do not print, log, or transmit the token value.
26 
27## Files
28- SKILL.md
29- bin/digitalocean.py
30 
31## Maturity
32🧪 Draft: written from DigitalOcean's public API docs; not yet live-tested end-to-end.