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/README.md
View on GitHub# Evals — digitalocean
`cases.yaml` is a routing + capability fixture, not an auto-runner. To use it: feed each
`should_trigger` prompt to the skill router and confirm `digitalocean` fires; feed each
`should_not_trigger` prompt and confirm it does NOT fire but defers to the named `route_to`
sibling. For the `capability` case, run the scenario through the agent and judge the
resulting transcript against the `must_include` rubric — every item should be present and
correct (doctl auth, an app spec with a service + envs, the DB wired via `${db.*}`/VPC, the
validate→create/update flow, logs + spec-revert rollback, and a cost note). Score it by hand
or with an LLM judge; there is no pass/fail script here.
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 |