agentleFS
kelpi-aikelpi-ai/meta-ads-skills/skills/pain-to-promise/SKILL.md

pain-to-promise

Skill3 starsChanged 5 months agoMITView on GitHub

Turn a mined buyer pain into a specific, algorithm-aimable promise, and stress-test it with the one-second recognition test. Use to sharpen an angle's promise line before it becomes copy or creative.

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:

    When an ad gets impressions but no clicks: usually a promise problem.

    line 13
  2. Distinctive:

    No superlatives without a mechanism ("the best" is noise.

    line 33

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

Pain to Promise

Doctrine

An angle lives or dies on its promise line, and promises fail in one predictable way: they generalize. "Essential nutrients in every bottle" is a promise to everyone, which the delivery algorithm reads as a promise to no one. "Lose weight without giving up the nutrients" names the person, the pain, and the outcome in nine words, so both the human and the algorithm know exactly who it is for. The narrower the promise, the harder it hits, and post-Andromeda, the better it delivers. New brands carry an extra burden: a stranger's promise needs specificity to be believed at all. Say how, say for whom, say what happens if it fails.

When to use

  • Between Buyer Language Miner (the pain) and Angle Writer / Creative Director (the copy and image).
  • When an ad gets impressions but no clicks: usually a promise problem.
  • Works with no MCP.

Run it

Turn these pains into promises for my offer: [ONE-LINE OFFER]

Pains (verbatim, from my buyer language mining): [PASTE 3-5 PAIN QUOTES with WHO said each]

For each pain:
1. Flip it into 3 candidate promise lines. Each must name or unmistakably imply: the WHO, the pain, and the specific outcome. Under 12 words each.
2. Run the one-second test on each: would the person who said this pain, scrolling at speed, recognize this line as "for me" in one second? Kill any line where the honest answer is no.
3. Run the anyone-test: could a competitor, or a company in a different category, run this exact line? If yes, it is generic. Sharpen or kill.
4. For the surviving lines: state the believability load. What would a stranger need to see next to believe this (mechanism, proof, guarantee)? One line each.
5. Rank the survivors and tell me which single promise you would put $20/day behind first, and why.

Guardrails

  • The promise must be one the offer actually keeps. A sharpened lie is still a lie; check every survivor against what the product really does.
  • No superlatives without a mechanism ("the best" is noise; "the only one that X" must be true).
  • Specific beats clever. If a line is witty but fails the one-second test, it is a caption, not a promise.

Good output looks like

For each pain: one surviving promise line, its believability requirement, and a ranked recommendation for the first test, all short enough to be on-image text.

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.