ericrisco/rsc-harness / skills/cloudflare
cloudflare
VerifiedUse when working on Cloudflare's edge platform — wrangler.jsonc bindings, choosing between D1/KV/R2/Durable Objects/Queues, deploying a Worker or SPA via Static Assets, or designing around a Workers runtime limit. NOT generic CI/release (that is `deployment`), NOT Next.js framework wiring (that is `nextjs`), NOT DNS records (that is `domains-dns`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| evals/README.md | markdown | 1020 B |
| evals/cases.yaml | config | 3.0 KB |
| references/storage-primitives.md | markdown | 4.4 KB |
| references/wrangler-config.md | markdown | 4.1 KB |
| scripts/verify.shexecutable | script | 5.2 KB |
evals/README.md
View on GitHub# Evals — cloudflare
These cases exercise the skill's routing and coverage. `should_trigger` lists prompts the
`cloudflare` skill must claim (config/bindings, storage choice, Static Assets deploy, Queues,
runtime-limit fixes), including a non-obvious symptom (stale KV reads) and a Catalan phrasing.
`should_not_trigger` lists adjacent prompts that must route elsewhere (deployment, nextjs,
domains-dns, postgresdb, redis) — each names the real sibling it belongs to. The `capability`
case checks the body actually produces a working wrangler.jsonc plus typed binding code for a
realistic multi-primitive Worker.
To run: feed `cases.yaml` to the repo's eval harness, which scores the skill description+body
against each prompt's expected routing and the capability rubric. To check manually, read
`cases.yaml` and confirm `SKILL.md` (and its references) answers each should_trigger prompt,
sends each should_not_trigger prompt to the named sibling, and covers every `must_include` item
in the capability scenario.
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 |