Skip to content

gooseworks-ai/goose-skills / skills/marketing/analyze-performance

analyze-performance

Verified

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.

references/local-mode.md

View on GitHub
# Local mode for analyze-performance

Load at Before you start 2 when GooseWorks isn't connected (the `marketing-guide` skill (`../../marketing-guide/SKILL.md`) §5). It replaces step 2's reads and the GooseWorks reads line. Every `gooseworks:` call in this playbook is skipped; everything else runs as written.

## What to read instead (free, with the host's file tools)

In `gooseworks-local/<brand-slug>/`:
- `brand-notes.md` (facts and rules the marketer stated) and, through the claims gate, `claims.md`.
- The newest approved plan in `plans/<slug>/` (its Status line says Approved): Economics, targets, Test plan, Measurement plan, Replan triggers. No approved plan → the targets come from the contract or the one message.
- `reports/performance/definitions.md`, the latest dated report and its Decisions, and `reports/performance/inputs/`.
- The paid run's `ads/campaigns/<slug>/state.md`, the `### YYYY-MM-DD — <title>` blocks of its `decisions.md`, and its run records under `runs/run-paid-campaigns/`.
- This playbook's own run records under `runs/analyze-performance/` (run-memory's local branch).

Then the marketer's connectors (read-only: ads platforms, store, CRM, billing, product analytics) and exports, by `measurement-contract.md` §4.

## What changes

- **No GooseWorks reads:** no brain, campaign record, Meta read, social analytics, creative tags or video reads. Every ad is "unannotated" unless the marketer names its angle. Organic numbers come from the marketer's exports or a connector.
- **Saving:** the report, the contract, the inputs and the run records go to the same paths under `gooseworks-local/<brand-slug>/`, through the save-to-brain and run-memory local branches. The report is delivered by write-report's local branch ("saved in this folder"). Kept learnings go to `brand-notes.md` through save-learning. Readouts and worn-out angles are not saved as facts: they stay in the run record.
- **Schedules:** the guide's §3 Schedules, local branch. Never `gooseworks:automation_upsert`.
- **Say once** what local mode can't give (the guide's §5 list), in one line.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall