agentleFS
kelpi-aikelpi-ai/meta-ads-skills/skills/fatigue-detector/SKILL.md

fatigue-detector

Skill3 starsChanged 5 months agoMITView on GitHub

Diagnose whether an ad is actually fatigued (two-condition rule) or you are just impatient, and decide refresh vs leave alone. Use when performance dips or a lead cost suddenly multiplies.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Before killing anything: impatience kills more winners than fatigue does.

    line 13
  2. Distinctive:

    Read-only. Refresh and retire are human decisions.

    line 29
  3. Distinctive:

    Never judge an ad against another ad's baseline.

    line 30

≈ “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

Fatigue Detector

Doctrine

"CTR down, CPM up, must be fatigue" is the most common misdiagnosis in ads. Sometimes it is the auction, the season, or a broken pixel. The two-condition rule cuts false alarms: an ad is fatigued only when frequency > 4.0 AND CTR is down 30%+ from its own baseline. Post-Andromeda, ad lifespans compressed and fatigue scales with spend more than with days, so small budgets fatigue slower than the "20 new ads a month" crowd claims. The owner's version of this pain: "the exact same ads that cost $6.85 a lead now cost $30.90."

When to use

  • A previously-working ad got expensive.
  • Before killing anything: impatience kills more winners than fatigue does.
  • Needs a Meta Ads MCP, read access.

Run it

Fatigue check, READ-ONLY, change nothing:

1. Pull frequency and CTR by ad for the last 14 days, plus each ad's CTR baseline from its best prior 14-day window.
2. Apply the two-condition rule: flag ONLY ads with frequency > 4.0 AND CTR down 30%+ from their own baseline.
3. For each flagged ad: which angle is it, how much has it spent since the decline started, and is a sibling angle still healthy?
4. For ads that LOOK tired but fail the rule: tell me the likelier cause (auction/CPM shift, seasonality, tracking change, or not enough recent spend to judge).
5. Recommend per flagged ad: refresh the creative (same angle, new execution) or retire the angle (the message is exhausted, not the image). Do not touch anything.

Guardrails

  • Read-only. Refresh and retire are human decisions.
  • Never judge an ad against another ad's baseline; fatigue is measured against the ad's own history.
  • A new execution of a dead angle is still dead. If three executions of one angle all decayed fast, the angle is done: back to Angle Writer.

Good output looks like

A short list split into "actually fatigued (here is the evidence)" and "leave it alone (here is what is really happening)".

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.