cloudthinker-ai/CloudSkills / skills/connections/managing-digitalocean
managing-digitalocean
VerifiedUse when working with Digitalocean — digitalOcean infrastructure management via the doctl CLI. Covers Droplets, databases, load balancers, firewalls, domains, and account billing. Use when managing DigitalOcean resources, checking Droplet health, or reviewing infrastructure costs.
Managing DigitalOcean
Manage DigitalOcean infrastructure using the doctl CLI.
MANDATORY: Discovery-First Pattern
Always discover available resources before performing analysis.
Phase 1: Discovery
#!/bin/bash
echo "=== Account Info ==="
doctl account get --format Email,DropletLimit,Status --no-header
echo ""
echo "=== Droplets ==="
doctl compute droplet list --format ID,Name,Region,Size,VCPUs,Memory,Disk,Status,PublicIPv4 --no-header | head -30
echo ""
echo "=== Databases ==="
doctl databases list --format ID,Name,Engine,Version,Region,Status,Size,NumNodes --no-header | head -20
echo ""
echo "=== Load Balancers ==="
doctl compute load-balancer list --format ID,Name,Region,Status,IP --no-header | head -10
echo ""
echo "=== Volumes ==="
doctl compute volume list --format ID,Name,Region,Size,DropletIDs --no-header | head -20
echo ""
echo "=== Firewalls ==="
doctl compute firewall list --format ID,Name,Status --no-header | head -10
Phase 2: Analysis
#!/bin/bash
echo "=== Droplet Details ==="
DROPLET_ID="${1:?Droplet ID required}"
doctl compute droplet get "$DROPLET_ID" --format ID,Name,Region,Size,VCPUs,Memory,Disk,Status,PublicIPv4,Created
echo ""
echo "=== Droplet Bandwidth (Recent) ==="
doctl monitoring droplet bandwidth get "$DROPLET_ID" --start "$(date -u -v-1H +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -d '1 hour ago' +%Y-%m-%dT%H:%M:%SZ)" --end "$(date -u +%Y-%m-%dT%H:%M:%SZ)" 2>/dev/null || echo "Bandwidth metrics not available"
echo ""
echo "=== Droplet CPU (Recent) ==="
doctl monitoring droplet cpu get "$DROPLET_ID" --start "$(date -u -v-1H +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -d '1 hour ago' +%Y-%m-%dT%H:%M:%SZ)" --end "$(date -u +%Y-%m-%dT%H:%M:%SZ)" 2>/dev/null || echo "CPU metrics not available"
echo ""
echo "=== Balance & Billing ==="
doctl balance get --format MonthToDateBalance,AccountBalance,MonthToDateUsage --no-header
Output Format
RESOURCE_TYPE ID NAME REGION STATUS
droplet 12345678 web-01 nyc1 active
droplet 12345679 web-02 nyc1 active
database abc-123 pg-main nyc1 online
Safety Rules
- Use read-only commands:
list,get - Never run
delete,destroy,removewithout explicit user confirmation - Always use
--no-headerand--formatfor clean output - Limit output with
| head -Nto stay under 50 lines
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--helpoutput. - NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |