Client Reporting Kit
Every report ends in a decision, not a shrug.
Turns your AI into a client-report kit builder — scopes a reporting kit around metrics your client actually agreed to, assembles the skills it needs (metrics snapshot, narrative, deck, next steps, delivery), and sets the bar each must clear so every report ends in a decision, not a shrug.

Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Client Reporting Kit
When to use
- Your client reports take a day to build and get a "thanks!" — no decision, no reply, no action
- Every report is rebuilt from scratch because there is no template, no agreed metrics, no standard
- You dread reporting week because it means re-deciding what to show, how to show it, and what it means
- Your reports are full of charts the client never asked for and short on the one number they care about
- You want a kit that turns reporting from a monthly scramble into a repeatable, decision-producing routine
Workflow
- Scope the kit (input: client, contract, goals → output: kit scope sheet)
Agree the metrics before the first report is ever built: three to five numbers, each tied to a goal the client named, each with an owner and a definition nobody can argue about ("qualified leads = form submissions from the contact page, excluding internal test entries"). The scope sheet also names the report's cadence (weekly, monthly), its reader (the one person whose decision it must inform), and its job in one sentence: "this report tells the client what happened, what it means, and what we do next." A report whose metrics were never agreed is a report that gets argued about instead of acted on. - Inventory the reporting skills (input: scope sheet → output: skill inventory)
List the skills the kit needs, one per reporting job: Metrics snapshot (turns raw data into the agreed numbers, each with its definition, its period, and its comparison — last period and same period last year where it means something), Narrative (turns the numbers into plain-language story: what moved, why it moved, what did not move and why that is fine), Deck (turns narrative + numbers into a readable report: one idea per page, every chart labeled with its takeaway), Next steps (turns the narrative into two to four proposed actions, each with an owner, a cost, and an expected effect), Appendix (turns everything else into an appendix — raw tables, method notes, definitions — so the main report stays short without hiding anything), Delivery (turns the finished report into the send: a short email with the headline, the decision needed, and the deadline for it). If the kit has no next-steps skill, the report is a history lesson: interesting, then filed.
Template preview
Client Reporting Kit — Report Pack
One report, one decision. Metrics agreed before the first number is ever pulled.
1. Kit scope sheet
Client: {name} | Reader (one person whose decision this informs): {name, role} Cadence: {weekly / monthly} | Length ceiling: {e.g. 6 pages + appendix} The report's job (one sentence): This report tells the client what happened, what it means, and what we do next.
Agreed metrics (3–5, each with definition + owner):
2. Metrics snapshot
Rule: no number appears without its definition, its period, and its comparison.
3. Narrative
What moved: {what changed + why} Why it moved: {cause, stated plainly}


