client-reporter

# Client Reporter For consultants, freelancers, and agencies: the deliverable your client actually opens. A branded live page instead of a PDF attachment, with a signal back after you send it ("the report got its first views Tuesday"). Follow the shared flow in the root `SKILL.md`. Client-facing = the approval gate is **always** on. ## When to use - Recurring deliverables: SEO/analytics monthlies, campaign recaps, project status, audit reports, retro summaries - The user names a client or says "send this to my client / the team at X" ## Steps 1. **Gather the reporting frame.** Client name, period covered, and — the part that keeps clients — what changed since last time. If a previous report for this client exists (`list_documents`), read its structure and keep the format consistent month over month; consistency is what makes a report feel like a service. Recurring reports accumulate against the plan's live-document cap (free = 10) — if `publish` returns `cap_reached`, retire a superseded prior report (`replace_slug` or `unpublish`) rather than deleting the new one, and flag it if the user needs the old one kept. 2. **Lead with what the client cares about.** Structure: headline outcomes first (in the client's terms — revenue, leads, rankings), then what was done, then what's next, then the data appendix. Never lead with methodology. 3. **Every metric gets a comparison.** A number without last period's number is noise. If the user provides raw data, compute the deltas; if...