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/cases.yaml
View on GitHubskill: spreadsheet-ops
should_trigger:
- prompt: "Write a Python script that exports this DataFrame to an .xlsx with a column chart and conditional formatting on overdue rows."
why: "Core Python→Excel artifact generation with charts + conditional formats — the xlsxwriter/pandas path."
- prompt: "My SUMIFS keeps returning #VALUE! and I can't see why. Here's the formula."
why: "Symptom-led formula repair; the user names the error, not the skill. Mismatched range shapes is the classic cause."
- prompt: "Every night my job needs to append a few rows to a Google Sheet. What's the right way to do it from Python?"
why: "Cloud read→write pipeline via gspread/Sheets API, including append + quota awareness."
- prompt: "I set a formula with openpyxl and saved, but when I read the cell back it's blank. What's wrong?"
why: "Non-obvious no-compute trap: openpyxl stores the formula; data_only returns None until Excel opens the file."
- prompt: "Haz una macro de Google Sheets que coloree las filas según el estado de cada pedido."
why: "Spanish + in-sheet automation → Apps Script V8, batched setBackgrounds. Tests language + intent."
- prompt: "My service account gets PermissionError / SpreadsheetNotFound when it tries to open the sheet, but the key is valid."
why: "Non-obvious share trap — a service account has no access until the sheet is shared with its client_email."
should_not_trigger:
- prompt: "These columns have mixed date formats and duplicate rows — clean and normalize them, no spreadsheet output needed."
route_to: data-cleaning
why: "Pure data hygiene with no spreadsheet artifact is data-cleaning's job."
- prompt: "Scrape this HTML pricing table from a webpage into structured rows."
route_to: data-scraper
why: "Extracting structured data from a web table is data-scraper, not spreadsheet authoring."
- prompt: "When a Typeform is submitted, post to Slack and add a row to a Sheet — wire the whole flow."
route_to: automation-flows
why: "Multi-app event chaining (Zapier/Make/n8n style) is automation-flows; spreadsheet-ops only owns the sheet step."
- prompt: "Set up OAuth and Drive access for my Google account so my app can authenticate."
route_to: google-workspace
why: "Credential/OAuth/Drive setup is google-workspace; this skill consumes the credential, it doesn't create it."
- prompt: "Build the recurring weekly stakeholder report deliverable for the leadership team."
route_to: reporting
why: "A finished recurring report deliverable is reporting; spreadsheet-ops stops at the programmable sheet."
capability:
- scenario: "Given a CSV of orders (order_id, customer, amount, status, due_date), produce a runnable Python script that writes an orders.xlsx with a header row, a SUMIFS total of amounts where status is OPEN, conditional formatting highlighting OVERDUE rows, and an idempotent keyed upsert by order_id so rerunning does not duplicate rows."
must_include:
- "Formula arguments are comma-separated, never semicolons (=SUMIFS(...,...,...) with commas)"
- "Any formula string written into a cell starts with a leading '=' "
- "States/handles that openpyxl stores the formula and does NOT compute it (value None / data_only caveat), or writes computed values"
- "Chart and/or conditional formatting via the correct engine (xlsxwriter for a new rich file, or openpyxl rules), not hand-waved"
- "Idempotent upsert keyed by order_id — reads existing keys, updates matches, appends the rest; no duplicate rows on rerun"
- "Script is runnable: passes python -m py_compile (valid syntax, real imports)"
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 |