Lead Magnet Factory

Lead Magnet Factory

Use this skill to turn an offer or audience problem into a lead magnet people actually want. The lead magnet should solve a narrow, urgent problem and naturally lead to the paid offer.

Read references/templates.md when the user wants a full outline, DM copy, or landing page copy.

Core Principle

A strong lead magnet gives away a specific shortcut, not a vague education asset. It should create immediate progress and make the next step obvious.

Lead Magnet Types

Choose the format based on the audience and offer:

• Checklist - Best for operational tasks and repeatable QA.
• Prompt pack - Best for AI workflows and execution shortcuts.
• Template - Best when users need a reusable artifact.
• Scorecard - Best when users do not know where they stand.
• Swipe file - Best for marketers, sales teams, and creators.
• Teardown - Best when the audience wants expert judgment.
• Playbook - Best for multi-step business workflows.

Creation Workflow

1. Define the paid offer and desired next step.
2. Name the audience's urgent problem.
3. Choose a lead magnet format that creates a fast win.
4. Write 5 angles and select the one with the strongest pull.
5. Build the outline.
6. Add proof, examples, and copy-paste assets.
7. Write the CTA and follow-up sequence.

Scoring

Score each idea 1 to 10:

• Urgency: does the audience care now?
• Specificity: is the promise concrete?
• Speed: can they get value in minutes?
• Relevance: does it lead to the paid offer?
• Shareability: would someone tag a friend or comment?
• Production ease: can it be built quickly?

Pick the highest total unless it is hard to produce or disconnected from the offer.

Output Format

**Best Lead Magnet**
[name and promise]

**Why This One**
[reason]

**Angles Considered**
| Angle | Score | Notes |
|---|---:|---|

**Outline**
1. ...
2. ...
3. ...

**CTA**
[next step]

**Distribution Copy**
- LinkedIn post hook:
- Comment keyword:
- DM delivery message:
- Follow-up:

Rules

• Make the lead magnet useful even if the person never buys.
• Avoid giant generic guides.
• The title should promise a concrete result or reveal a painful mistake.
• The CTA should be direct and connected to the offer.
• Do not overcomplicate delivery. A simple doc or hosted page is often enough.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: jpeslar1
• Source: jpeslar1/john-peslar-ai-skills
• License: MIT

Install and usage instructions live in the source repository linked above.