ericrisco/rsc-harness / skills/spreadsheet-ops
spreadsheet-ops
VerifiedUse when working a spreadsheet programmatically — writing or repairing a formula, generating an .xlsx with Python including charts and conditional formats, driving Google Sheets from a script, building a read-transform-write pipeline, or writing an in-sheet macro or trigger. Covers formula errors, Sheets API quota, service-account permissions, and formulas that read back blank. NOT pure dedupe or normalisation with no sheet output (that is `data-cleaning`), NOT scraping a web table into rows (that is `data-scraper`), NOT multi-app event wiring (that is `automation-flows`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| evals/README.md | markdown | 2.1 KB |
| evals/cases.yaml | config | 3.6 KB |
| references/formula-cookbook.md | markdown | 2.7 KB |
| references/python-excel.md | markdown | 3.8 KB |
| references/sheets-api-appsscript.md | markdown | 4.2 KB |
| scripts/verify.shexecutable | script | 5.0 KB |
evals/README.md
View on GitHub# Eval harness — `spreadsheet-ops`
Two things are graded: **triggering** (does the skill fire on real spreadsheet work and stay quiet on
near-misses that belong to a sibling?) and **capability** (does loading the skill make the produced
script measurably better?). Cases are in `cases.yaml`. They are graded by a human or a driver agent
feeding prompts to a fresh session — not an automated runner. The executable check is
`scripts/verify.sh`, which smoke-tests that generated artifacts actually compile/open and that formulas
use comma arguments; the eval cases here grade judgment, not code.
## Triggering
For each prompt, start a fresh agent with only `spreadsheet-ops` discoverable, paste the prompt
verbatim, and observe whether the agent reaches for this skill. Run 3–5 trials (the decision is
stochastic). `should_trigger` passes if the skill fires in the majority of trials. `should_not_trigger`
passes if it does **not** fire; each names a `route_to` sibling (`data-cleaning`, `data-scraper`,
`automation-flows`, `google-workspace`, `reporting`) — sanity-check the agent would plausibly route
there, though any not-this-skill route still passes the gate. Some routed siblings may not be built in
this collection yet; the routing intent is what's graded. Pass bar: ≥ 90% trigger accuracy across cases.
## Capability
Run the scenario twice — WITHOUT the skill (clean agent) and WITH it — and grade each transcript against
the `must_include` checklist, one point per bullet that is specifically and correctly covered (not just
name-dropped). WITH the skill should cover ≥ 80% of bullets and clearly beat WITHOUT (target ≥ +30
points or crossing fail→pass). If the script the WITH-skill agent emits is real, run it through
`scripts/verify.sh` to confirm the comma-args and compile bullets objectively.
## Notes
Prompts are deliberately varied: several never say "spreadsheet" (the #VALUE! SUMIFS repair, the blank
openpyxl cell, the service-account PermissionError), and one is in Spanish — these test intent over
keywords. Record trial counts and per-bullet verdicts so a reviewer can audit; don't report a bare
pass/fail.
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 |