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/cases.yaml
View on GitHubskill: reporting
should_trigger:
- prompt: "Set up a weekly automated performance report emailed to our exec team."
why: "Core push report — recurring cadence, fixed audience, delivered without a human. The center of this skill."
- prompt: "Build a monthly PDF report for our biggest client, on a schedule."
why: "Recurring client-facing report + artifact format (PDF) + cadence — fetch→narrate→render→deliver pipeline."
- prompt: "Send the board a quarterly summary PDF every quarter, automatically."
why: "Cadence + formal artifact + push delivery; the quarterly board pack is a canonical reporting case."
- prompt: "Automatiza un informe mensual para dirección."
why: "Spanish for 'automate a monthly report for leadership' — recurring stakeholder report, must route here."
- prompt: "Munta un informe setmanal automàtic per al comitè."
why: "Catalan for 'build an automatic weekly report for the committee' — recurring push report."
- prompt: "Our Monday metrics email keeps going out with last week's numbers — make it reliable."
why: "Non-obvious: framed as a bug, but it is report-pipeline reliability (freshness gate, fail-loud) — squarely reporting, not a generic email fix."
should_not_trigger:
- prompt: "Build an interactive dashboard the team can open to slice sales by region."
route_to: dashboard
why: "Pull/live surface the user opens and filters — not a push artifact on a cadence."
- prompt: "Which KPIs should we even be tracking for the growth team?"
route_to: kpi-framework
why: "Deciding which metrics matter / defining the metric tree — reporting consumes an agreed set, it does not adjudicate it."
- prompt: "Dig into why signups dropped last Tuesday."
route_to: analytics
why: "One-off investigation to answer a question, not a recurring standing artifact."
- prompt: "Forecast next quarter's revenue from this history."
route_to: forecasting
why: "Predicting future values / projections — reporting reports what happened, it does not predict."
- prompt: "Our source CSV has duplicate and malformed rows — clean it."
route_to: data-cleaning
why: "Fixing dirty source data — reporting assumes a trustworthy source and only gates on freshness, it does not clean."
- prompt: "Just wire up a generic cron job that runs this script nightly."
route_to: automation-flows
why: "Generic scheduling/plumbing for any job with no report shape — reporting uses a scheduler but does not teach scheduling-in-general."
capability:
- scenario: "Set up a recurring weekly revenue report, delivered as a PDF emailed to the leadership team every Monday at 08:00, sourced from a metrics CSV."
must_include:
- "Defines a report contract: audience, cadence, sections, metric source (and who owns the numbers), channel, owner."
- "Separates the template from per-recipient params (one Jinja2 template scoped by params, not a forked template per recipient)."
- "Uses a pinned render stack (pandas → Jinja2 → WeasyPrint 68.1, Matplotlib for charts) and states the pin."
- "Writes a narrative/executive-summary layer (purpose + 3 takeaways + what changed vs last period), not just a raw metric table."
- "Schedules it via cron or GitHub Actions schedule:, and notes GH Actions cron is UTC."
- "Includes a freshness gate before send and a fail-loud failure alert to the named owner."
- "Routes KPI-definition to kpi-framework and any live-view/slice request to dashboard rather than absorbing them; defers transport to email-connector."
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 |