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?

Make a copy Sign in to get your own project to change. Download a copy All files in one ZIP. The copy doesn’t update by itself.

SKILL.md

1.6 KB · 26 lines
Copy the text
Download this file
name description
data-check Finds problems to fix before counting, empty cells, mixed formats, duplicates, outliers, spelling variants, totals rows; use for "check this data".

Data check

Use when: before a report on a new table, or when the user says the numbers look wrong.

Input

A file in data/, or the profile from describe-table.

Steps

  1. Look for: empty cells in number or date columns; dates or numbers in more than one format; exact duplicate rows and duplicate ids; values far outside the usual range (ten times the typical value, negative where it cannot be); spelling variants of the same category ("Delivery", "delivery ", "Deliv."); a totals or subtotals row inside the data; rows that belong to another period.
  2. List each problem with the row numbers and a suggested fix. Say how each would change the totals.
  3. Do not change data/<name>.csv. If the user agrees to the fixes, save data/<name>-clean.csv with exactly the agreed changes and list them in the file's first line as a comment-free note in data/README.md.
  4. Save reports/<table>-check.md (note "Data check: , problems").
  5. Answer with the count of problems by kind and the one that changes the totals most.

    6. Output

    A table: Problem | Rows | Suggested fix | Effect on totals. Then the list of applied fixes, if any.

    Edge cases

    • No problems found: say so in one line and move to the report.
    • A value that could be a typo (240 instead of 24): flag it and ask; never correct a value by guessing.
    • Categories in two languages or cases: propose a mapping table and apply it only in the clean copy.
---name: data-checkdescription: Finds problems to fix before counting, empty cells, mixed formats, duplicates, outliers, spelling variants, totals rows; use for "check this data".---# Data checkUse when: before a report on a new table, or when the user says the numbers look wrong.## InputA file in `data/`, or the profile from `describe-table`.## Steps1. Look for: empty cells in number or date columns; dates or numbers in more than one format; exact duplicate rows and duplicate ids; values far outside the usual range (ten times the typical value, negative where it cannot be); spelling variants of the same category ("Delivery", "delivery ", "Deliv."); a totals or subtotals row inside the data; rows that belong to another period.2. List each problem with the row numbers and a suggested fix. Say how each would change the totals.3. Do not change `data/<name>.csv`. If the user agrees to the fixes, save `data/<name>-clean.csv` with exactly the agreed changes and list them in the file's first line as a comment-free note in `data/README.md`.4. Save `reports/<table>-check.md` (note "Data check: <table>, <n> problems").5. Answer with the count of problems by kind and the one that changes the totals most.## OutputA table: Problem | Rows | Suggested fix | Effect on totals. Then the list of applied fixes, if any.## Edge cases- No problems found: say so in one line and move to the report.- A value that could be a typo (240 instead of 24): flag it and ask; never correct a value by guessing.- Categories in two languages or cases: propose a mapping table and apply it only in the clean copy.