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 |
references/app-spec.md
View on GitHub# App Platform app spec — full reference
The app spec is the single source of truth for an App Platform app. Version it in
`.do/app.yaml`, validate, then `create`/`update`. Below is a multi-component spec with the
fields you'll actually reach for.
```yaml
name: my-platform
region: nyc
# --- HTTP service: gets a public URL + auto TLS ------------------------------
services:
- name: web
github:
repo: me/my-platform
branch: main
deploy_on_push: true
build_command: npm ci && npm run build
run_command: node dist/server.js
instance_size_slug: apps-s-1vcpu-1gb
instance_count: 2
http_port: 8080
routes:
- path: / # ingress route for this component
health_check:
http_path: /healthz
initial_delay_seconds: 10
period_seconds: 10
failure_threshold: 3
autoscaling: # optional: scale instances on CPU
min_instance_count: 2
max_instance_count: 5
metrics:
cpu:
percent: 70
envs:
- key: DATABASE_URL
value: ${db.DATABASE_URL}
scope: RUN_TIME
- key: STRIPE_SECRET
value: ${STRIPE_SECRET}
type: SECRET
scope: RUN_TIME
# --- background worker: no public route --------------------------------------
workers:
- name: queue-worker
github:
repo: me/my-platform
branch: main
deploy_on_push: true
run_command: node dist/worker.js
instance_size_slug: apps-s-1vcpu-1gb
instance_count: 1
envs:
- key: DATABASE_URL
value: ${db.DATABASE_URL}
scope: RUN_TIME
# --- static frontend: free (up to 3), served from the edge -------------------
static_sites:
- name: marketing
github:
repo: me/my-platform-web
branch: main
build_command: npm ci && npm run build
output_dir: dist
routes:
- path: /site
# --- one-off / pre-deploy job (e.g. migrations) ------------------------------
jobs:
- name: migrate
kind: PRE_DEPLOY # PRE_DEPLOY | POST_DEPLOY | FAILED_DEPLOY
github:
repo: me/my-platform
branch: main
run_command: npm run migrate
instance_size_slug: apps-s-1vcpu-1gb
envs:
- key: DATABASE_URL
value: ${db.DATABASE_URL}
scope: RUN_TIME
# --- managed database referenced by ${db.*} ----------------------------------
databases:
- name: db
engine: PG # PG | MYSQL | REDIS (Valkey)
production: true
# or attach an existing cluster:
# cluster_name: my-existing-cluster
# --- alerts ------------------------------------------------------------------
alerts:
- rule: DEPLOYMENT_FAILED
- rule: DOMAIN_FAILED
```
## Env scoping
| Field | Values | Use it for |
| --- | --- | --- |
| `scope` | `RUN_TIME`, `BUILD_TIME`, `RUN_AND_BUILD_TIME` | Keep build-only secrets out of the running container; runtime-only out of the build |
| `type` | (default plaintext), `SECRET` | `SECRET` for every token/password/key — encrypted at rest, hidden in dashboard |
| `value` | literal or `${...}` | `${db.DATABASE_URL}` / `${db.HOSTNAME}` from a `databases:` entry; `${OTHER_COMPONENT.HOSTNAME}` for inter-component |
## Instance size slugs (common)
| Slug | Class | Rough price |
| --- | --- | --- |
| `apps-s-1vcpu-0.5gb` / `apps-s-1vcpu-1gb` | Basic | from ~$5/mo per service |
| `apps-s-1vcpu-2gb` | Basic | ~$25/mo |
| `apps-d-1vcpu-2gb` / `apps-d-2vcpu-4gb` | Dedicated | ~$78/mo at the 2vcpu/4gb tier |
Start at the smallest basic slug. Move to dedicated only when shared-CPU contention shows up
in real metrics. Dynamic apps start at $5/mo per service; data-transfer overage is $0.02/GiB.
## Commands
```bash
doctl apps spec validate .do/app.yaml # offline structural lint
doctl apps create --spec .do/app.yaml # first deploy
doctl apps update <app-id> --spec .do/app.yaml # apply / roll back (re-apply prior spec)
doctl apps spec get <app-id> > .do/app.yaml # pull the live spec back into git
doctl apps logs <app-id> <component> --type run --follow
```
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 |