ericrisco/rsc-harness / skills/vercel
vercel
VerifiedUse when operating an already-chosen Vercel project from the CLI or its config file — preview versus production deploys, debugging builds, pushing and pulling env vars across environments, custom domains, function runtime, duration and regions, crons, rewrites and headers, and deployment protection. NOT host choice, Docker or CI (that is `deployment`), NOT Next.js app code or next.config (that is `nextjs`), NOT DNS records or registrar transfers (that is `domains-dns`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.7 KB |
| evals/README.md | markdown | 1.6 KB |
| evals/cases.yaml | config | 3.5 KB |
| references/cli-cookbook.md | markdown | 4.0 KB |
| references/vercel-json.md | markdown | 4.5 KB |
| scripts/verify.shexecutable | script | 6.2 KB |
evals/README.md
View on GitHub# Eval harness — `vercel`
These cases are graded by an agent/human judge, not a shell script. No live Vercel account, login,
or network is needed: triggering checks routing, and the capability check grades a generated
`vercel.json` against a `must_include` rubric (you can additionally pipe that file through
`scripts/verify.sh` for a mechanical sanity pass).
## How to run
- **Triggering.** Load the full skill catalog so routing is realistic (vercel alongside deployment,
nextjs, domains-dns, cloudflare, …). For each `should_trigger` prompt, run 3-5 fresh sessions and
confirm the `vercel` skill fires. For each `should_not_trigger`, confirm `vercel` stays silent and
the agent routes toward the named `route_to` sibling. A near-miss leaking into `vercel` is a worse
failure than a missed trigger — investigate any leak. Pass bar: ~90% trigger accuracy.
- **Capability.** Run the scenario twice — once with `skills/vercel/SKILL.md` (and its `references/`)
loaded, once without — and score each output against the `must_include` list (one point per item).
Pass when the with-skill run covers >=80% AND clearly beats the without-skill run; if both score
the same, the skill is adding no value on that scenario. Optionally run the produced `vercel.json`
through `bash scripts/verify.sh <file>` to confirm it mechanically passes (no `builds`+`functions`,
no in-file `memory`, well-formed crons).
Record per-prompt fire rates, routing targets on near-misses, and with/without capability scores.
Note borderline cases honestly rather than rounding up to a green check.
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 |