agentleFS
F0rger123F0rger123/claude-meta-ads-god-mode/skills/ads-optimization/SKILL.md

ads-optimization

Skill1 starsChanged 22 days agoMITView on GitHub

Structured optimization engine for Meta and Google Ads - multi-window analysis (today, 3, 7, 14, 30 days), conversion lag, learning status, wasted spend, search terms, creative fatigue, budget constraints, attribution quality, and confidence-graded recommendations (HIGH / MODERATE / EXPERIMENT). Use for "optimize", "what wasted the most spend", "what should we change", "weekly optimization".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use adsgm quality to grade evidence when in doubt.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Ads optimization

Workflow: workflows/optimization-cycle.md.

Windows and what each is for

WindowUseNever use for
Todayanomalies, delivery breaks, runaway spendperformance verdicts
Last 3 daysearly warning (tracking drop, disapprovals, CPM spike)pausing or scaling
Last 7 daysprimary read for active entities (full week cycle)low-volume accounts' CPA
Last 14 daysfatigue trends, small accounts-
Last 30 dayssearch terms, structure, small-volume verdictsdetecting recent change

Exclude the last N days from CPA verdicts where N ≈ conversion lag (Google lag buckets; CRM lead-to-qualified time).

Wasted spend ("Show me what wasted the most spend this month")

Rank entities by spend with no or poor results, but only call it waste when:

  • Certain waste: irrelevant search terms, spend outside service area, broken URLs/disapproved-then-reapproved ads, duplicate campaigns bidding on the same queries, spend on a tracking-broken period with no leads in CRM either.
  • Probable waste: ads/ad sets/keywords with spend ≥ 2-3x target CPA and zero conversions, out of learning, tracking verified (HEURISTIC).
  • Not waste: learning ad sets, breakdown segments with higher averages (Meta breakdown effect), upper-funnel campaigns judged on last-click.

Report: top 5-10 by $ with class (certain/probable), evidence, fix, confidence, approval needed.

Recommendation format

[HIGH CONFIDENCE] Add 7 phrase negatives (DIY/jobs) to Kitchen Search
  Data: 30d, $166 on 23 terms, 0 conv; no converter blocked
  Expected: -$40/week waste
  Action: adsgm google plan (add_negative_keywords) -> approval: yes (client in approval mode)

Confidence:

  • HIGH - large sample, clean tracking, mechanism clear (e.g., irrelevant queries, out-of-area spend).
  • MODERATE - directional data; act in small reversible steps, set a read date.
  • EXPERIMENT - hypothesis; design a test with one variable (workflows/creative-testing.md).

Use adsgm quality to grade evidence when in doubt. Do not overreact to tiny samples; "no action - insufficient data until <date>" is a valid recommendation.

Order of operations per cycle

  1. Tracking health and anomalies. 2. Certain waste. 3. Budget constraints on winners. 4. Fatigue/creative. 5. Structure. 6. Tests. Max 3-5 changes per cycle per platform; log each with adsgm plan so cooldowns apply.

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.