Analyze Performance
Weekly performance read across every channel we run: what worked, why, and what to make...
Install
npx skills add gooseworks-ai/goose-skills --skill analyze-performance -g -a claude-code -y- Repository
- gooseworks-ai/goose-skills1.3k
- Category
- Testing
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Weekly performance read across every channel we run: what worked, why, and what to make next, judged on the business's real number (store revenue, qualified pipeline, retained users), not platform claims. Use when: write my Monday report; how are my ads doing, which ad won?; are my ads actually making money (Meta says 4x ROAS but revenue is flat); why did sales drop this week; did the test win; is my tracking working; monthly numbers for the replan; anything on fire today. Not for acting on the recommendations (pausing, scaling, launching), use run-paid-campaigns; not for replanning the budget, use plan-campaign.
analyze-performance
What you get
- The Monday report, saved to
reports/performance/<YYYY-MM-DD>.mdand shown in chat, the same shape every week (references/monday-report.md); run-paid-campaigns decides and acts on its recommendations. - Learnings written to the brand brain after the marketer has seen and kept them; ended tests' measured results saved as readouts.
- A run record for next week (
references/run-memory.md): the per-channel and per-ad scorecards with the trend since last run, each call with its owner, review date and test, and what happened to last week's calls, saved to the brand, so "what worked" and "what to make next" rest on weeks of history, not one week. - Monthly unit-economics read for plan-campaign's replan; daily pulse on request, exception-only (
references/monthly-and-pulse.md).
