ericrisco/rsc-harness / skills/digitalocean
digitalocean
UnverifiedUse when deploying or operating a workload on DigitalOcean — Droplet vs App Platform vs Functions, doctl, app spec YAML, Managed Postgres/MySQL/Valkey on the VPC, S3-compatible Spaces + CDN. NOT host-agnostic CI/CD or rollback strategy (that is `deployment`), NOT a bare Hetzner VPS (that is `hetzner`), NOT another managed PaaS (that is `railway`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| evals/README.md | markdown | 716 B |
| evals/cases.yaml | config | 2.3 KB |
| references/app-spec.md | markdown | 4.0 KB |
| references/droplet-ops.md | markdown | 3.3 KB |
| scripts/verify.shexecutable | script | 3.2 KB |
evals/cases.yaml
View on GitHubskill: digitalocean
should_trigger:
- prompt: "Deploy my Node API to DigitalOcean App Platform"
why: Direct request to ship a service to App Platform — the skill's core compute decision and app spec flow.
- prompt: "Droplet or App Platform for my Rails app — which is cheaper to run?"
why: DO-specific compute decision (Droplet vs App Platform) with a pricing axis the decision table answers.
- prompt: "Write me a DigitalOcean app spec yaml that runs a web service with a managed postgres"
why: Asks for the checkable artifact (app spec YAML) with a ${db.*}-wired Managed Database.
- prompt: "Subir mi web a DigitalOcean con doctl"
why: Spanish trigger — deploying a site to DO via doctl is squarely this skill.
- prompt: "I need an S3-compatible bucket with a CDN on DigitalOcean"
why: Non-obvious — the user never says "Spaces", but S3-compatible object storage + CDN on DO is exactly Spaces.
should_not_trigger:
- prompt: "Design my GitHub Actions deploy pipeline with rollback gating"
route_to: deployment
why: Host-agnostic CI/CD pipeline and rollback strategy, not where-on-DO-it-runs.
- prompt: "Is Hetzner cheaper than DO for a 16GB VPS?"
route_to: hetzner
why: The decision tilts to the other host's economics; Hetzner owns its own VPS sizing/pricing.
- prompt: "Optimize this slow Postgres query with a better index"
route_to: postgresdb
why: Database internals (query/index tuning), not provisioning a DO cluster.
- prompt: "Write the Dockerfile for my app"
route_to: docker
why: Containerizing the app itself; this skill consumes an image, it doesn't author one.
capability:
- scenario: "Ship a Node web service plus a managed Postgres to App Platform from scratch."
must_include:
- "doctl auth init with an API token from cloud.digitalocean.com/account/api/tokens"
- "An app spec YAML with a services entry (github repo, http_port, instance_size_slug) and envs"
- "DB wired via ${db.DATABASE_URL} (and/or trusted source over the VPC private host)"
- "doctl apps spec validate, then doctl apps create --spec / doctl apps update --spec"
- "Logs via doctl apps logs and rollback by re-applying the prior spec"
- "A cost/sizing note (basic from $5/mo, $0.02/GiB transfer overage, or unassigned reserved IP charge)"
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: 322k | 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: 198k | 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: 119k | 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: 118k | Updated | Claude CodeCodex | Verified | Install |