gooseworks-ai/goose-skills / skills/shared/meta-ad-manager
meta-ad-manager
UnverifiedFront door and loop owner of a Meta (Facebook/Instagram) ad harness. Reads the brand's ads/ docs, works out which campaign the user means and which stage it is at, hands off to the stage skill that runs it (intake, strategy, creative, launch, checks, fixes, answers), and writes every stage change back to the docs. Use it when someone wants to run ads on Meta, comes back to ads they started earlier, a stage skill hands back, or a scheduled check fires.
contract/templates/campaign/strategy.md
View on GitHub---
campaign: <slug>
product_ids: <list>
version: <int>
updated_at: <date>
based_on: <string>
---
<!--
ads/campaigns/<slug>/strategy.md — what this campaign is trying to do and why. Written by the
strategy skill at launch and revised at each deep check. Reasoning is part of the file: a
decision without its "because" is not finished.
campaign The folder slug.
product_ids Catalog product ids this campaign advertises, e.g. [prod_123]. Reference, never
copy, the product description.
version Starts at 1; +1 each time the strategy changes. The change is also a
decisions.md entry.
updated_at Date of the last write (YYYY-MM-DD).
based_on What this version rests on: "intake 2026-09-24", "deep check 2026-10-01".
Plan numbers here (budget, ad count, test length) are Goose's decisions and are written plainly.
Anything measured goes on an `- Observed:` line with its window and sync time.
-->
# Strategy — <campaign name>
## Goal
<!-- The business outcome in the user's words (trials, purchases, demo calls). -->
## Audience
<!-- Who the ads are for and how Goose will reach them (broad, interests, lookalike). -->
## Objective and placements
<!-- Meta objective and placement mix, each with the reason. -->
## Budget
<!-- Daily or lifetime amount, split across ad sets, and the approved ceiling. -->
## Creative plan
<!-- Ads needed, the angles and formats for diversity, and the 3x rule: generate three times
the count so the judge loop and the user can choose. -->
## Test frame
<!-- What is being compared, for how long, and the minimum evidence before judging. -->
## Success metric
<!-- The one number that says it worked, and the threshold. -->
## Reasoning
<!-- Why this plan over the obvious alternatives, and what would change it. -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |