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/brand.md
View on GitHub---
brand_id: <id>
business_type: <enum: software|ecommerce|app|services|other>
familiarity: <enum: novice|intermediate|expert>
updated_at: <date>
---
<!--
ads/brand.md — facts about the business that every campaign shares. Written by intake and
strategy, changes rarely. Product facts are NOT copied here: they live in the catalog and a
campaign's strategy.md references them by product id.
brand_id The GooseWorks brand id. Outside GooseWorks: `local`.
business_type Picks which intake questions apply (software: sales cycle, PLG/SLG, ACV;
ecommerce: AOV, repeat rate, site conversion; app: install→paid, ARPU).
familiarity The user's own answer about Meta Ads experience. The orchestrator uses it to
explain terms for novices and drop explanations for experts.
updated_at Date of the last write (YYYY-MM-DD).
Numbers the USER stated (ACV, margin, CAC target) are Goose's inputs, written plainly with who
said it ("per Dana"). A number read from a tool (Stripe, Shopify, Meta) is an observation and
goes on an `- Observed:` line with its tag — see RULES.md.
-->
# Brand — <brand name>
## Business model
<!-- What they sell, to whom, how they make money. Two to four sentences. -->
## Unit economics
<!-- ACV or AOV, gross margin, LTV, CAC target. Say who stated each and whether it is an
estimate. Unknowns are written "unknown — ask at strategy", never guessed. -->
## Sales cycle
<!-- Time from first touch to purchase, and the path (self-serve trial, demo call, checkout). -->
## Other channels
<!-- Where else they sell or acquire customers; what is already working. -->
## Connected accounts
<!-- Which Meta ad account, Page and pixel Goose uses, by id, and the date connected.
Connection STATUS is not stored: it is read from the readiness tools each time. -->
## Claims rules
<!-- What ads may and may not claim: approved proof, banned phrases, regulated words.
Default: no named customers and no results claims unless the user approved one here. -->
## Safety rules
<!-- Hard limits the harness must respect: max daily budget, audiences to exclude, pause
thresholds the user pre-approved. -->
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 |