agentleFS
styfinitystyfinity/claude-marketing-department/skills/lead-magnet-builder/SKILL.md

lead-magnet-builder

Skill6 starsChanged 4 months agoMITView on GitHub

Scores lead magnet ideas against the paid offer, picks the winner, outlines it, writes the core content in full, and drafts the opt-in and promo copy that give it away. Use when the list needs to grow with buyers rather than freebie collectors.

3 other projects use 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. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Ask for the minimum at opt-in — usually just the email address.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Lead Magnet Builder — bait that matches the buyer

A lead magnet is not a gift, it is a filter. The right magnet solves one narrow, urgent slice of the exact problem the paid offer solves fully — so the people who grab it are the people who buy. A magnet that appeals to everyone grows the list and starves the pipeline.

Inputs

  • The paid offer the magnet feeds, the audience, and any candidate ideas: $ARGUMENTS
  • From marketing-brief.md if present: the offer, top pains and desired outcomes, the ICP, the language bank, and the banned-phrases list.

Do this

  1. Generate 6–10 candidates (fold in any supplied). Each must sit on one of the brief's top pains and be a genuine first step of the paid journey — a checklist, template, teardown, calculator, swipe file, or short guide.
  2. Score each 1–5 on four axes and show the table:
    • Pulls the ICP specifically — would someone who will never buy still want it? Then it scores low.
    • Consumable in under 15 minutes — magnets that ask for an evening never get opened.
    • Delivers a real win — something is genuinely solved by the last line, not teased.
    • Sets up the offer — finishing it makes the paid next step feel obvious.
  3. Pick the winner and outline it: three title options (specific, outcome-named), the promise, the sections, and the built-in bridge — the magnet solves step one and makes step two visible.
  4. Write the core content in full. The actual checklist, template, or guide — complete and usable, not a summary of what it would contain. Where the content needs data the brief lacks, flag the gap instead of inventing.
  5. Write the giveaway copy: the opt-in page (headline, three bullets, CTA) and two social posts announcing it, phrased from the language bank.
  6. Name delivery and follow-up: what the delivery email says (the magnet plus one consumption tip) and when the paid offer first appears — usually after the win lands, not before.

Output

The scoring table, the finished magnet ready to format, opt-in page copy, two promo posts, and the delivery note. Flag every place where thin data forced a placeholder.

Rules

  • The magnet must be genuinely useful on its own. If it only works as an advert for the offer, it is a brochure wearing a bow.
  • The title may lean on curiosity; the contents deliver exactly what the title promised.
  • Specific beats broad. A 12-point pre-launch checklist beats an ultimate guide to marketing.
  • Evidence over invention: no fabricated statistics or examples inside the magnet. Its credibility is the whole point.
  • Ask for the minimum at opt-in — usually just the email address. Every extra form field costs more subscribers than it is worth.

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.