ericrisco/rsc-harness / skills/render
render
VerifiedUse when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire with its data. NOT the generic ship and release flow (that is `deployment`), NOT another PaaS such as `railway` or `fly-io`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| evals/README.md | markdown | 834 B |
| evals/cases.yaml | config | 3.7 KB |
| references/blueprint-reference.md | markdown | 6.7 KB |
| scripts/verify.shexecutable | script | 5.5 KB |
evals/cases.yaml
View on GitHubskill: render
should_trigger:
- prompt: "Write a render.yaml that deploys my Express API plus a background worker and a Postgres database."
why: "Core Blueprint authoring across multiple service types (web + worker + Postgres) — the central job this skill owns."
- prompt: "My Render deploy keeps failing with 'no open ports detected'. What's wrong?"
why: "Non-obvious symptom phrasing that maps directly to the port-binding trap (must bind 0.0.0.0:$PORT) — the #1 first-deploy failure this skill leads with."
- prompt: "How do I run a nightly cleanup job on Render?"
why: "Service-type selection: a scheduled run-and-exit job is a `type: cron` with a `schedule:`, not a worker — a decision this skill teaches without naming the type."
- prompt: "Wire DATABASE_URL from my Render Postgres into both my web service and my worker without hardcoding it."
why: "Cross-service env reference via fromDatabase — the wiring rule (never hardcode the URL) is a signature concern of this skill."
- prompt: "Mi web service en Render devuelve 502 después del primer deploy, ¿qué pasa?"
why: "Spanish trigger; first-deploy 502 is the port-binding / no-open-ports symptom this skill diagnoses."
- prompt: "Should this email-sending job be a Render worker or a cron job?"
why: "Non-obvious worker-vs-cron boundary; the answer hinges on the 12h cron kill and run-then-exit semantics, both core to this skill."
- prompt: "Why does my free Render service take 30 seconds to respond after no one's hit it for a while?"
why: "Free-tier spin-down / cold-start trap described by symptom, not by name — squarely a free-tier mechanic this skill explains."
should_not_trigger:
- prompt: "Deploy this app to Fly.io with a Dockerfile and set up volumes."
route_to: "fly-io"
why: "A different PaaS — Fly.io has its own config surface and sibling skill; this skill is Render-specific."
- prompt: "Write the Dockerfile for my Node app with a small multi-stage runtime image."
route_to: "docker"
why: "Container authoring. Render only consumes a Dockerfile via runtime: docker; writing it is docker's job."
- prompt: "Design our blue/green release and rollback strategy across staging and production."
route_to: "deployment"
why: "Platform-agnostic release flow and promotion strategy belongs to deployment; this skill is Render config and mechanics."
- prompt: "Optimize this slow Postgres query and add the right indexes."
route_to: "postgresdb"
why: "Schema and query tuning is postgresdb; this skill only provisions and connects Render's managed Postgres."
- prompt: "Point my custom domain's DNS A and CNAME records at the host at my registrar."
route_to: "domains-dns"
why: "Registrar-side DNS records belong to domains-dns; only the Render domains: block stays here."
capability:
- scenario: "Given a Python FastAPI repo with a Celery worker and a job that must email users every 5 minutes, produce a render.yaml and fix the start command so it deploys correctly on Render."
must_include:
- "Web service binds 0.0.0.0 and reads $PORT (e.g. gunicorn/uvicorn --bind 0.0.0.0:$PORT), not a hardcoded port"
- "The Celery process declared as type: worker (no port binding)"
- "The 5-minute email job declared as type: cron with a schedule: expression (e.g. */5 * * * *)"
- "DATABASE_URL wired via fromDatabase (and Redis via fromService), never a hardcoded connection string"
- "Secrets handled with sync: false or generateValue: true rather than literal value: strings"
- "Migrations placed in preDeployCommand, not startCommand"
- "Calls out the 12h cron kill (use a worker for longer jobs) and the free-Postgres 30-day expiry trap"
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 |