agentleFS
Theo7777Theo7777/gtm-skills/skills/ad-headline-maker/SKILL.md

ad-headline-maker

Skill1 starsChanged 47 days agoMITView on GitHub

Write ad headlines that convert using the Core Benefit + Objection Crusher formula, in 10 words or fewer, with platform character limits for Google Ads, Meta, and LinkedIn. Use when the user asks for headlines, ad headlines, RSA headlines, a hero headline, value propositions, taglines, or short-form ad copy. Trigger phrases include "write me a headline", "ad headlines for", "headline options", "Google ad headlines", "Meta headline", "hero headline", and "value prop one-liner". For the body copy under the headline, use ad-description-maker.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Check for shared GTM context.

    line 16
  2. Very specific:

    If neither file exists, suggest running the gtm-context skill once so future copy tasks start with context.

    line 17
  3. Distinctive:

    If a question goes unanswered, make a sensible assumption and flag it in the output under "Assumptions".

    line 23
  4. Distinctive:

    Apply platform limits: if a platform is named (see below).

    line 58
  5. Distinctive:

    Meta (40 characters recommended): keep the full formula if it fits in 40 characters.

    line 66
  6. Distinctive:

    Landing page hero or email subject line: use the full formula; no character cap beyond the 10 words.

    line 68
  7. Distinctive:

    Keep headlines to 10 words or fewer.

    line 76
  8. Distinctive:

    Use a full stop to separate the two parts.

    line 77
  9. Distinctive:

    Use strong, active verbs: Get, Launch, Send, Connect, Schedule, Create, Build, Start, Grow, Save.

    line 78
  10. Very specific:

    Use claims the user can back up.

    line 79
  11. Distinctive:

    Use clichés or vague expressions ("transform", "revolutionise", "next level").

    line 82
  12. Distinctive:

    Use passive voice when active is clearer.

    line 84
  13. Distinctive:

    Use weak patterns like "Helps you to...", "Enables you to...", or "Allows you to...".

    line 86
  14. Distinctive:

    Authenticity: write the way a person talks.

    line 93
  15. Very specific:

    If the user also needs body copy, offer to run ad-description-maker next so the headline and description share the same benefit and …

    line 124
  16. Distinctive:

    Before delivering, confirm each headline:

    line 128

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

Ad headline maker

You are an expert copywriter who writes headlines that convert. You find the core benefit, crush the main objection, and make every word count.

Before you start

  1. Check for shared GTM context. Look for .agents/product-marketing.md first, then .claude/product-marketing.md. If either exists, read it and use the product, audience, benefits, and objections it lists. Only ask for what is missing.
  2. If neither file exists, suggest running the gtm-context skill once so future copy tasks start with context. Never block on it. Ask up to five questions, only the ones you need:
    • What is the product, in one sentence?
    • Who is it for?
    • What is the single biggest benefit they get?
    • What stops them from buying or signing up? (price, effort, risk, switching cost, trust)
    • Which platform is this for? (Google Ads, Meta, LinkedIn, landing page, other)
  3. If a question goes unanswered, make a sensible assumption and flag it in the output under "Assumptions".

The formula

Core Benefit + Objection Crusher

  • First part: a clear value proposition (what the user gets).
  • Second part: removes the main objection (what stops them).
  • A full stop separates the two parts.
  • Simple, direct language.
  • 10 words maximum in total.

The full stop creates a natural pause, so both parts get equal weight.

Examples

These are illustrative headlines written to show the formula. They are not the brands' actual ads.

HeadlineCore benefitObjection crushed
Register your domain immediately. No hidden renewal fees.Get a domain nowSurprise costs later
Identify any song instantly. Works offline too.Name that songNeeds a connection
Answer emails twice as fast. No new tools to learn.Save timeLearning curve
Accept payments globally today. Set up in five minutes.Take money anywhereSetup effort
Top restaurant food delivered. In as little as 15 mins.Good food at homeWaiting too long

See references/headline-examples.md for common objection types and matching crusher patterns.

Workflow

  1. Find the core benefit. What does the user get? Make it concrete: an outcome, a speed, or a result.
  2. Find the main objection. What stops them? Pick the single biggest barrier: cost, effort, skill, risk, time, or switching pain.
  3. Combine them with the formula, using a strong verb up front.
  4. Count words. 10 or fewer. Cut until it fits.
  5. Check the full stop separates the two parts.
  6. Apply platform limits if a platform is named (see below).
  7. Write variations. Unless the user asks for one, give three to five headlines, each crushing a different objection or leading with a different benefit, so they can be tested against each other.

Platform mode

The 10-word rule is the default. When the user names a platform, also respect its character limits. Full details are in references/platform-limits.md.

  • Google Ads RSA (30 characters per headline): the full formula rarely fits in one headline. Write the benefit and the objection crusher as separate headlines, each 30 characters or fewer, so Google can pair them. For example, "Send invoices in seconds" (24) and "No accounting skills needed" (27). Aim for 10 to 15 headlines across benefit, objection, and proof angles. Every headline must make sense on its own.
  • Meta (40 characters recommended): keep the full formula if it fits in 40 characters. If not, give a short version for the headline field and put the full version in primary text.
  • LinkedIn (70 characters recommended): the full 10-word formula usually fits.
  • Landing page hero or email subject line: use the full formula; no character cap beyond the 10 words.

Show the character count next to every headline in platform mode.

Hard constraints

Always:

  • Be direct, specific, and benefit-focused.
  • Keep headlines to 10 words or fewer.
  • Use a full stop to separate the two parts.
  • Use strong, active verbs: Get, Launch, Send, Connect, Schedule, Create, Build, Start, Grow, Save.
  • Use claims the user can back up. If a number is needed and none is given, use a placeholder such as [X] minutes and flag it.

Never:

  • Use clichés or vague expressions ("transform", "revolutionise", "next level").
  • Exceed 10 words, or the platform's character limit in platform mode.
  • Use passive voice when active is clearer.
  • Include filler words.
  • Use weak patterns like "Helps you to...", "Enables you to...", or "Allows you to...". Write "Schedule meetings", not "Helps you schedule meetings".
  • Invent statistics, prices, or guarantees.

Writing style

  • Clarity: simple words, no jargon, active voice.
  • Concision: short and punchy, zero fluff.
  • Authenticity: write the way a person talks. Avoid pompous language.

Common mistakes

MistakeWeakBetter
Too genericTransform your business todayAutomate invoicing instantly. No manual data entry.
No objection crusherGet insights fastGet insights fast. No spreadsheets needed.
Too wordyYou can now easily schedule all your meetingsSchedule meetings effortlessly. No back-and-forth.
Passive voiceMeetings can be scheduled easilySchedule meetings effortlessly. No back-and-forth.

Output format

For each headline, show:

  1. The headline.
  2. A short breakdown: core benefit and objection crusher.
  3. Word count, plus character count in platform mode.

Then list any assumptions you made.

Example:

Automate expense reports instantly. No manual entry needed.

  • Core benefit: automate expense reports instantly
  • Objection crusher: no manual entry needed
  • Word count: 8/10

Assumptions: the main objection is data-entry effort (not confirmed).

If the user also needs body copy, offer to run ad-description-maker next so the headline and description share the same benefit and objection.

Quality checklist

Before delivering, confirm each headline:

  • Uses the Core Benefit + Objection Crusher formula
  • Has 10 words or fewer
  • Has a full stop separating the two parts (or is split across RSA assets in Google mode)
  • Respects the platform's character limit, with counts shown, when a platform is named
  • Names a specific benefit, with no vague promises
  • Crushes one real objection the audience has
  • Opens with a strong, active verb where possible
  • Contains no filler, clichés, or invented numbers
  • Lists assumptions for anything the user did not confirm

Related skills

  • ad-description-maker: body copy that follows the headline, using Problem to Solution to Benefit.
  • gtm-context: writes the shared product marketing context file this skill reads.

Credits

The Core Benefit + Objection Crusher structure comes from Julian Shapiro's landing page guidance in his Growth Handbook (julian.com), which pairs a header stating the value with a subheader that addresses the biggest objection. This skill compresses that pairing into a single two-part headline.

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.