agentleFS
kelpi-aikelpi-ai/meta-ads-skills/skills/media-buyer/SKILL.md

media-buyer

Skill3 starsChanged 5 months agoMITView on GitHub

Build the whole campaign (objective, one broad ad set, a $20/day test, one ad per angle) as a PAUSED draft for review. Use when angles and creatives are approved and it is time to go live.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After Creative Director; you have approved ads and image hashes.

    line 12
  2. Distinctive:

    After publishing: hands off for a week.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Media Buyer

Doctrine

Simple structure wins at small budgets: one campaign, one broad ad set, 3-5 genuinely different angles as separate ads. Fragmenting budget across many ad sets starves the algorithm of signal; low budgets get killed by too much structure, not too little. Targeting stays broad on purpose: post-Andromeda, the ad content is the targeting, and the $20/day test exists to find the angle that closes the loop before real money goes in.

When to use

  • After Creative Director; you have approved ads and image hashes.
  • Needs a Meta Ads MCP with write access. Everything is built paused; nothing spends until you publish.

Run it

Build me a test campaign, everything PAUSED until I review it:

1. Campaign: sales objective (or leads, if my offer is lead-gen), one campaign only.
2. Ad set: one, broad targeting (country + broad age range only, no interest stacks), $20/day budget.
3. Ads: one ad per approved angle, using these creatives: [IMAGE HASHES + COPY]. Do not blend angles.
4. Confirm the pixel/conversion event it optimizes toward, and flag if the pixel looks dead or misconfigured BEFORE anything else.
5. Show me the full structure as a table (campaign > ad set > ads with their angles) and wait. I will say "publish" when I have reviewed it.

Do not enable any Advantage+ creative enhancements. I want the creatives to run exactly as approved.

Guardrails

  • Paused draft first, always. The human says "publish", the skill never assumes it.
  • $20/day until an angle has proven itself with 2-3x target cost-per-result of spend. Scaling before signal is donating to Meta.
  • One campaign. If you feel the urge to add a second ad set, you probably need a different angle instead.
  • After publishing: hands off for a week. Daily edits reset learning. Reading daily is what the Daily Auditor is for.

Good output looks like

A paused campaign whose structure you can read in ten seconds, optimizing toward a verified conversion event, with each ad mapped to a named angle.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.