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/README.md
View on GitHub# render evals
These cases are routing-and-capability fixtures, not an automated test runner. Feed
`cases.yaml` through the repo's eval harness, which uses an LLM judge. `should_trigger`
and `should_not_trigger` check that the SKILL.md `description` routes the right prompts in
(Render deploys, render.yaml authoring, the port/502/cron/free-tier traps) and the wrong
ones out to the named sibling (`fly-io`, `docker`, `deployment`, `postgresdb`,
`domains-dns`). The `capability` case is graded against its `must_include` rubric to confirm
the SKILL.md body actually produces a correct, trap-free `render.yaml` — right service
types, `0.0.0.0:$PORT` binding, referenced (not hardcoded) env vars, and the cron/Postgres
warnings. There is nothing to `npm test` here; the judge reads SKILL.md and scores the
output against the rubric.
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 |