gooseworks-ai/goose-skills / skills/marketing/run-paid-campaigns
run-paid-campaigns
VerifiedRuns the paid leg of an approved plan: checks tracking, pages and stock before money moves, then stages one weekly proposal of kills, scales, pauses, swaps and launches, each with its reason and a check date. Nothing changes without your yes. Use when: launch these ads; it's Monday — kill, scale or pause?; swap this fatiguing ad; we sold out or the sale ended — pause the ads now; an ad got rejected or the account got restricted; we're in a brand crisis — hold the ads; give me the Google, TikTok or LinkedIn changes to make. Not for how the ads did or which ad won — use analyze-performance; not for rewriting a rejected image ad — use make-static-ads.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.9 KB |
| references/baseline-audit.md | markdown | 2.6 KB |
| references/launch-and-graduate.md | markdown | 7.7 KB |
| references/local-mode.md | markdown | 2.8 KB |
| references/meta-levers.md | markdown | 8.1 KB |
| references/moves.md | markdown | 8.1 KB |
| references/proposal-and-log.md | markdown | 19.6 KB |
| references/reading-results.md | markdown | 7.9 KB |
| references/run-memory.md | markdown | 18.7 KB |
| references/written-instructions.md | markdown | 4.5 KB |
| skill.meta.json | config | 6.8 KB |
| tests/test-by-hand.md | markdown | 10.5 KB |
references/meta-levers.md
View on GitHub# What GooseWorks can and cannot do on Meta today
Load before the first move of any run. Say the relevant limits to the marketer up front, in plain words — never let them believe a lever exists that doesn't. Tool descriptions are the live truth; re-read them if a call is refused.
## Can (product levers)
| Lever | Tool | What it really does | Approval |
|---|---|---|---|
| Read Goose ads' results | `gooseworks:meta_read` `view: "performance"` | Spend, clicks, landing-page views, leads, CTR, CPA, ROAS for **Goose-made creatives live in the account only**. Not attribution. `insight.available=false` → report numbers, name no winner. | — |
| Refresh the account copy | `gooseworks:refresh_meta_sync` | Re-syncs campaigns/ad sets/ads (normally daily). Use only when an object you know exists isn't visible (e.g. an ad set created today) — not as a routine freshness step. 1–3 min; poll the same tool. Reads only. | — |
| Publishable Pages | `gooseworks:meta_read` `view: "pages"` | The only valid `page_id`s. Empty → the marketer must grant Page access. | — |
| Launch | `gooseworks:prepare_meta_ad_push` | Saves a fully **paused** plan and checks destination + creatives. **NEW_CAMPAIGN**: Traffic objective only, landing-page views (if the destination has Meta tracking) or link clicks, lowest-cost bidding, lifetime budget, broad countries, a few ads, Facebook placements (no Instagram actor). **EXISTING_AD_SET**: adds Goose creatives to an ad set already in the account, inheriting its budget, schedule, audience, optimisation — the **only route to purchase/lead-optimised delivery**. | The marketer approves on the returned approval URL. You cannot approve. Read `push_status` until `AWAITING_APPROVAL`; never prepare a duplicate. |
| Change a budget | `gooseworks:propose_meta_budget_change` | Whole new budget, same kind as created (lifetime for Goose launches), **only on ad sets Goose created**. Refused if the budget moved in Ads Manager meanwhile — relay, re-read, never retry blind. | Approval URL; an increase makes the marketer type GO LIVE; a decrease is one click. |
| Swap a creative | `gooseworks:propose_meta_creative_replacement` | Adds a new finished Goose render to the same ad set (same Page, destination, CTA) and pauses the old **Goose** ad; if the old ad is live, the new one goes live first. Loses the old ad's likes/comments. | Approval URL; live swaps need GO LIVE. |
| Pause | `gooseworks:pause_meta_ad_push` | Pauses Goose-published ads — always pass the `push_id` from `state.md` (omitting it means the most recent push, and ids from another push pause nothing) plus the named `meta_ad_ids`. Reversible — but **there is no resume tool**; un-pausing is done by the marketer in Ads Manager. | Only with the marketer's own words **in the current turn** as `user_instruction`. Never on judgement or a schedule. |
| Undo a launch | `gooseworks:revert_meta_ad_push` | Deletes ads that never went live, pauses live ones, cancels the push. For mistakes only — **never use it for a kill**. Confirm intent first. | The marketer's words this turn. |
| Check a proposal | `gooseworks:meta_read` `view: "change_status"` / `"push_status"` | Approved or declined, and Meta's before/after values. Read on every resume instead of re-proposing. | — |
Every propose/pause call can carry `recommendation_ref` (`R<n>`); the server then removes that bullet from `## Open recommendations` in `ads/campaigns/<slug>/state.md` and appends a `### YYYY-MM-DD — …` block to `decisions.md` — but only if that `state.md` frontmatter lists the push in `meta_push_ids` or the campaign in `goose_campaign_id` (`proposal-and-log.md`).
## Cannot (→ written instructions the marketer applies, see `written-instructions.md`)
- Anything on campaigns, ad sets or ads **GooseWorks did not create** — usually most of the account. Budgets, pauses, duplications, audience edits there are written instructions, or connector changes when the marketer has an ads connector (below).
- Sales/lead/app-install objectives on a new campaign; cost caps, bid caps, ROAS goals; Advantage+ shopping campaign settings; placements; dayparting; radius/local targeting; audience exclusions; attribution-setting changes; end-date changes; account spending limit.
- Un-pausing an ad.
- Reading frequency, reach, CPM, learning status, delivery status, disapprovals, placement/age breakdowns, or non-Goose ads' results. Read them through the marketer's ads connector when they have one (below); else ask for an Ads Manager export (last 14 days, campaign/ad set/ad level, with frequency, CPM, results, cost per result) or take them from analyze-performance's read.
- Finding an existing ad set's id for EXISTING_AD_SET: the tool refers to an ad-context tool that is not on the server; ask the marketer to copy the ad set id from Ads Manager, `refresh_meta_sync`, then prepare.
## With an ads-platform connector (any platform)
**The one connector rule.** The marketing-guide §3, data-access, plan-campaign and `apply-and-log` point here; none restates it. It holds for any ads platform (Meta, Google, TikTok, LinkedIn…) whose connector the marketer has in this agent, with or without GooseWorks. Only this playbook makes changes through a connector; every other playbook keeps every connector read-only, and store, CRM and billing connectors stay read-only here too. The connector's tool descriptions are the truth for what it can do; never assume a write it doesn't list.
- **Reads:** account-wide results, frequency, CPM, reach, learning and delivery status, disapprovals, and ads GooseWorks didn't make (the "Cannot" reads above).
- **Before any change:** confirm the account is this brand's. Never through a connector: an object GooseWorks has a lever for (keep it on GooseWorks, so its outcomes are logged), deleting anything, uploading customer lists, changing the account spending limit.
- **One change per yes.** Each is a card: object, current → new value from a fresh read, reason, how we'll check. Apply only when the marketer's own message this turn names that change (object and new value), e.g. "yes, raise Founder story to $75/day". Two changes named exactly are two yeses; "yes", "go" or "do them all" is none: ask them to name each.
- **Apply:** re-read the object; if it changed since the card, show the new card and stop. Then one write call, plus the connector's own confirm step if it has one. A budget rises at most 30% per step. New campaigns, ad sets and ads are created paused; switching one on is its own named yes. A conversion campaign (sales, leads, sign-ups) needs the conversion event to reach the account: check it in the health gate first.
- **After:** read the value back, tell the marketer what it now shows, and log it (the `run-paid-campaigns-apply-and-log` skill (`../../run-paid-campaigns-apply-and-log/SKILL.md`) step 11). A failed call or a different read-back: say so plainly, log it, and never retry without a new yes.
- **Creative:** copy verbatim from the makers' hand-off files; images and videos are the marketer's own files or ads already in the account, claim-checked first (`launch-and-graduate.md` § Health gate, item 3).
- **What it lacks:** an approval page and an outcome log. Say once that this is weaker than GooseWorks' approval page; every `decisions.md` block for a connector change is yours (`proposal-and-log.md`).
## What "one-tap yes" really is today
The weekly proposal resolves into three bundles (four with a connector: its cards, each applied on its own named yes), and the playbook says so:
1. **Approval links** — created when the proposal is staged (the propose/prepare calls change nothing in Meta), one approval each; increases and live swaps need GO LIVE typed on the page.
2. **One sentence to say in chat** that fires the approved pauses — e.g. *"pause the UGC unboxing and 3-benefits ads"* — which becomes the `user_instruction`. A bare "yes" is not a pause instruction.
3. **Written-instruction cards** for everything outside GooseWorks' levers, each under a minute of work, with a "reply done" confirmation; ids never appear in what the marketer sees.
Never report anything as done until the approval page is approved and `change_status`/`push_status` (or the marketer's "done") confirms the after-state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |