Skip to content

gooseworks-ai/goose-skills / skills/shared/meta-ad-manager

meta-ad-manager

Unverified

Front 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.

references/planning-only.md

View on GitHub
# Planning-only mode

## Summary

Use this mode when neither GooseWorks nor a Meta token is available. The harness still does its
most valuable work: intake, strategy, and a creative brief the user can take to Ads Manager.
Nothing is read from or written to Meta, and the skill says so plainly rather than treating it as
a failure.

## The `ads/` docs

- A local `ads/` folder in the working directory, exactly as in the direct Meta adapter: `local`
  for both ids, whole-file writes, and `python3 <this skill's folder>/contract/validate.py ads`
  (run from the directory that holds `ads/`) to check it.
- The campaign brief is kept in `strategy.md` (see `ad-management-intake`'s adapter).

## Whose ads are Goose's

Nothing is launched in this mode, so there is no launch record.

## Stages available

| Stage | In this mode |
|---|---|
| intake | yes |
| strategy | yes. Account facts are unknown: assume a cold account with no tracking, and say so |
| create, review | a written creative brief per angle; no generation |
| launch | no. Hand over the strategy and the brief, and name the access a launch needs: GooseWorks, or a Meta token with `ads_management`, the ad account id and Page access. `launch-meta-ad-campaign`'s planning-only reference produces the Ads Manager checklist |
| checks, fixes, answers from Meta | no. "Why" questions are still answered from `decisions.md` |

The furthest stage a campaign can reach here is `review` (the user has approved the creative brief). Do not move it to `launch` or `live`.

## Final line

End each session with: what was written to `ads/`, that nothing was created in Meta, and the one
access step that would unlock the next stage.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall