Weekly report agents
Friday reporting went from 2-3 hours to 45 minutes, per client.
One reporting skill per client, same pipeline underneath: pull the live numbers, score them against the client's targets, write the report in my voice, and post the draft to my review channel. Nothing reaches a client until I've read every number.
How a run actually goes
Claude reads the newsletter dashboard in Chrome
For How to AI it opens the Substack dashboard, pulls total subscribers and total opens, then does the math itself: open rate and email CTR, with week-over-week comparison.
Pipeboard pulls the Meta side
Spend, CPL, leads, CPM and ad CTR per creative, plus the fb.me links so the client can click straight into each ad.
Writes the report in my voice
Account overview, top 3 creatives, insights, winning angle, next steps, TL;DR. First person, no AI tells.
Posts the draft to my Slack first
The Slack connector posts to my private review channel. I review the draft there; the client channel only gets it after I approve. The gate is part of the skill.
Same pipeline, 6 clients: only the sources swap
Beehiiv for A Media Operator and ByteByteGo, the TFM dashboard for Insight Links, Hex for Workweek's 6 newsletters at once. Write the brief once per client; Friday runs itself.
Anyone on the team can build their own: 4 ingredients
1 · Your data sources
Meta metrics come from Pipeboard (your ad account ID). Newsletter metrics from wherever your client lives: Beehiiv, Substack, or a dashboard Claude reads in Chrome.
2 · Your client's definition of good
The KPI and its target (CPL under $2.50, CPQL under $20...). This is what turns numbers into "on track" or "needs action".
3 · One great past report
Paste your best one as the GOOD example, and optionally a bad one to avoid. This does more than any list of rules.
4 · Where it goes
Your review channel first, client channel only after you approve. The gate is part of the skill.
Say this to Claude, word for wordRead the howtoai-weekly-report skill from the tfm-skills
plugin. That's the simple one. (ww-friday-report is the
multi-account complex one.)
Build my-[client]-weekly-report based on it, with my specifics:
- Meta via Pipeboard, account [ID]
- Newsletter metrics via [Beehiiv / Substack / dashboard URL]
- KPI: [CPL], target [$X]
- Here's a great past report as the example: [paste]
- Draft to my review channel, I review first. Then iterate, weekly: every time you correct a draft ("don't lead with CPM", "the client hates the word fatigue"), tell Claude to bake that correction into the skill. Three Fridays in, it writes the report the way you would.
Rules & guardrails straight from the skill instructions
- Primary metric is Subscriber CAC + volume; Verified CAC is secondary.
- Always first person, straight to the client: technical, optimistic, never sycophantic or verbose.
- Never present today's data in a weekly window (7 days ending yesterday).
- Always show the draft for approval before anything is sent.