Reports from tables

pacpio-team/reports-from-tables
Copy project link
Public
Anyone can see and download this project, even without signing in.
Owner: Pacpio Team Made by the Pacpio team
Made by the Pacpio team
Report

Use it with your AI

Works in Claude, ChatGPT or any other AI

  1. Step 1: Connect your AI

    Do it once. It takes a minute.

    Connect your AI
  2. Step 2: Ask your AI

    Paste this into your chat:

    What does the Pacpio project pacpio-team/reports-from-tables do?

SKILL.md

1.9 KB · 29 lines
Copy the text
Download this file
name description
report Builds a report from a table, headline numbers, breakdowns, top and bottom, anomalies and how it was counted; use for "monthly report".

Report

Use when: the user wants a report, a summary of a period, "what happened in September".

Input

The table (a file in data/ or the clean copy), the period, and from my/report-settings.md the metrics, breakdowns and the reader. If the table has not been described or checked, do that first or say in "Data notes" that it was skipped.

Steps

  1. Read my/report-settings.md, knowledge/counting-rules.md, knowledge/report-rules.md, templates/report.md.
  2. Headline numbers: the total of the key metric, the number of rows, the average per row and the median; say which one to trust and why.
  3. Breakdown by the first dimension from the settings: sum, share of the total, count per group; the Total line must equal the headline total. A second breakdown only if the settings ask for it.
  4. Top five and bottom five items by the metric.
  5. Changes against the previous period, if a previous table or report exists; otherwise say "no previous period".
  6. Anomalies in numbers; data notes (missing, excluded, assumptions); "How this was counted": the column for each number, filters, the subtotals written out, the rounding, the cross-check.
  7. Save reports/YYYY-MM-<topic>.md (note "Report: ").
  8. Answer with the three headline numbers and the file name.

Output

The report by the template, up to two pages. Numbers with units; percentages with "of what".

Edge cases

  • More than about 300 rows: count in parts of up to 100 rows, write the partial sums in "How this was counted", or use the user's spreadsheet totals as a check.
  • The user asks why a number fell: report where it fell (which group, which week) and what to ask the data owner; no causes.
  • Several tables in one request: one report per table, then a short comparison if asked.
---name: reportdescription: Builds a report from a table, headline numbers, breakdowns, top and bottom, anomalies and how it was counted; use for "monthly report".---# ReportUse when: the user wants a report, a summary of a period, "what happened in September".## InputThe table (a file in `data/` or the clean copy), the period, and from `my/report-settings.md` the metrics, breakdowns and the reader. If the table has not been described or checked, do that first or say in "Data notes" that it was skipped.## Steps1. Read `my/report-settings.md`, `knowledge/counting-rules.md`, `knowledge/report-rules.md`, `templates/report.md`.2. Headline numbers: the total of the key metric, the number of rows, the average per row and the median; say which one to trust and why.3. Breakdown by the first dimension from the settings: sum, share of the total, count per group; the Total line must equal the headline total. A second breakdown only if the settings ask for it.4. Top five and bottom five items by the metric.5. Changes against the previous period, if a previous table or report exists; otherwise say "no previous period".6. Anomalies in numbers; data notes (missing, excluded, assumptions); "How this was counted": the column for each number, filters, the subtotals written out, the rounding, the cross-check.7. Save `reports/YYYY-MM-<topic>.md` (note "Report: <topic> <period>").8. Answer with the three headline numbers and the file name.## OutputThe report by the template, up to two pages. Numbers with units; percentages with "of what".## Edge cases- More than about 300 rows: count in parts of up to 100 rows, write the partial sums in "How this was counted", or use the user's spreadsheet totals as a check.- The user asks why a number fell: report where it fell (which group, which week) and what to ask the data owner; no causes.- Several tables in one request: one report per table, then a short comparison if asked.