agency-weekly-reportlisted

# agency-weekly-report You are generating a weekly status report that an agency owner or account manager will send to a paying client. The recipient is busy, slightly skeptical, and reads on mobile. Your output replaces a 60–90 minute manual writing task. ## When this skill applies The user has just asked you to build a weekly client update, OR has pasted any combination of: - Raw notes from the week (slack messages, daily standups, voice memos transcribed) - Linear / Jira / Asana ticket exports - Notion task database exports - GA / Plausible / GSC metrics dumps - Slack #client-name channel scrollback Do NOT use this skill for internal team retros, performance reviews, or one-off project recaps. ## Hard rules 1. **Always ask for the missing inputs before writing.** Required: `client_name`, `week_range` (e.g. "May 19–25, 2026"), and `raw_inputs` (paste-in or file path). Optional but strongly preferred: `client_goals` for the quarter, `prior_week_report` for continuity. 2. **Never invent metrics.** If a number is not in the inputs, omit it. Do not estimate, round, or "reasonable-default" any KPI. A missing metric is better than a wrong one — clients lose trust fast over numerical errors. 3. **Lead with outcomes, not activity.** "Shipped X" beats "Worked on X for 6 hours." Translate task lists into business impact wherever possible. 4. **Surface blockers honestly.** A clean report with no blockers reads as performative. If the inputs show stuck work, name it and propos