ericrisco/rsc-harness / skills/reporting
reporting
FlaggedUse when a recurring report must ship itself on a cadence — weekly digest, monthly exec pack, board pack — via a fetch→narrate→render→deliver pipeline with a schedule and a freshness gate. NOT a live view people slice (that is `dashboard`), NOT picking which KPIs to track (that is `kpi-framework`), NOT a one-off investigation (that is `analytics`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.6 KB |
| evals/README.md | markdown | 1008 B |
| evals/cases.yaml | config | 3.5 KB |
| references/pipeline.md | markdown | 8.2 KB |
| scripts/verify.shexecutable | script | 6.5 KB |
evals/README.md
View on GitHub# reporting — evals
These cases are run by the skill-eval harness, not by a bundled scorer here. `should_trigger` and
`should_not_trigger` check routing: each `should_trigger` prompt should select this skill (read the
`why` to see what makes it reporting, including the non-obvious "stale Monday email" case and the
Spanish/Catalan phrasings), and each `should_not_trigger` prompt should route to the named real
sibling (`route_to`) instead of being absorbed here — the boundaries against dashboard, kpi-framework,
analytics, forecasting, data-cleaning, and automation-flows are the whole point. The single
`capability` case is rubric-scored by a judge: a passing answer must hit every item in `must_include`
(report contract, template/params separation, pinned render stack, narrative layer, schedule,
freshness + failure gate, and correct routing of out-of-scope asks). There is no automated pass/fail
script — read each `why`/`route_to` and the rubric to grade by hand or feed them to the harness.
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 |