Skip to content

rampstackco/claude-skills / skills/lead-magnet-design

lead-magnet-design

Verified

Designing lead magnets that earn the email. The discipline of building gated content (ebooks, templates, checklists, swipe files, mini-courses, free tools) that delivers genuine standalone value while qualifying the lead and warming them for what comes next. Honest about thin-bait (overpromises, underdelivers), kitchen-sink-resource (everything, helps with nothing), and earned-value-magnet (delivers standalone value while qualifying the lead). Triggers on lead magnet, gated content, opt-in offer, ebook, checklist, template, swipe file, mini-course, free tool, content upgrade, freebie, opt-in, list-building offer. Also triggers when an audience is being asked for an email and the offer attached to that ask needs design discipline, when previous lead magnets converted but did not produce qualified leads, or when a lead magnet is being scoped for the first time.

references/format-specific-quality-gates.md

View on GitHub
# Format-specific quality gates

Per-format quality tests. Templates, checklists, swipes, mini-courses, ebooks, videos. Each format has gates specific to that format. A great template fails different tests than a great mini-course.

The quality gates exist because thin-bait can hide in any format. The gates make hiding harder. Apply them before launch; if the magnet fails a gate, redesign before shipping.

---

## Template gates

A template earns the email when the reader produces a usable artifact in minimal time.

**Gate 1: Time-to-usable-artifact.** Can the reader produce a usable artifact in under 30 minutes? If the template requires hours of customization to be useful, the format is failing.

**Gate 2: Specificity of prompts.** Are the prompts specific enough to feel custom? "Insert your unique value proposition here" is too generic. "What is the specific outcome your customer needs in the first week" is specific enough to guide the reader.

**Gate 3: Adaptability across the segment.** Is the template adaptable across the segment of the audience, or rigidly bound to one situation? A template for "B2B SaaS pricing one-pager" should work across multiple B2B SaaS situations; a template that only fits one company's exact circumstances is too rigid.

**Gate 4: Worked example included.** Does the template include a worked example showing what a completed version looks like? Worked examples reduce the time-to-usable-artifact and signal that the template was real-tested.

**Gate 5: Tooling honesty.** If the template requires specific tools (a Notion template, a Figma file, an Airtable base), is the tool dependency honestly disclosed in the title? Surprise dependencies frustrate readers who do not have the tool.

---

## Checklist gates

A checklist earns the email when each item is actionable today.

**Gate 1: Each item actionable today.** No "consult your team about X" or "decide on the strategy for Y." Each item should be something the reader can verify or complete.

**Gate 2: Workflow order.** Does the checklist sequence reflect actual workflow order? An out-of-order checklist forces the reader to mentally re-sort, which costs the speed advantage the format promised.

**Gate 3: Scope discipline.** Is the checklist scoped narrowly enough to feel comprehensive within scope? "Pre-launch checklist for B2B SaaS" is narrower than "Pre-launch checklist for any product" and produces a tighter, more useful resource.

**Gate 4: Item count sanity.** Strong checklists are usually 12-30 items. Fewer than 8 items often signals thin-bait; more than 50 often signals that the format should have been an ebook or playbook instead.

**Gate 5: Verification cues.** Does each item include enough cue for the reader to know they actually verified it? "Email sequence tested in production" is verifiable; "Email sequence reviewed" is not.

---

## Swipe file gates

A swipe file earns the email when the swipes are real, attributed, and curated.

**Gate 1: Real swipes.** The swipes should be examples actually used in the wild, not invented for the magnet. Real swipes have specificity that invented ones lack.

**Gate 2: Attribution where possible.** Each swipe attributed to source where the source is public. Unattributed swipes can read as theft.

**Gate 3: Currency.** Are the swipes current? Swipes from 5 years ago may have specific dating cues that signal staleness. Periodic refresh is part of the swipe-file discipline.

**Gate 4: Curation visible.** Is the curation visible? The reader can see why each swipe is included? A 200-swipe dump with no commentary is less useful than 30 curated swipes with notes on why each was included.

**Gate 5: Categorization.** Are the swipes categorized by use case (subject lines, headlines, ad copy, design references)? A flat list of unsorted swipes is harder to extract value from than a categorized collection.

---

## Mini-course gates

A mini-course earns the email when each lesson stands on its own and the cumulative arc adds up.

**Gate 1: Each lesson standalone.** A reader who only completes lesson 1 should still extract value. "You will learn the answer in lesson 4" loses readers who do not make it to lesson 4.

**Gate 2: Cumulative time honesty.** Is the total time commitment honestly disclosed in the title or landing page? "5-day course" should mean 5 days of meaningful engagement, not 5 days of one paragraph emails.

**Gate 3: Production consistency.** Are all lessons at consistent production quality? Courses that decay in production quality across lessons signal that the team ran out of capacity.

**Gate 4: Clear next step at end.** Does the course end with a clear next step (related product, related resource, ongoing community)? "Thanks for taking the course" without a next step is a missed opportunity.

**Gate 5: Completion tracking.** Does the course include progress markers ("Lesson 3 of 5") so the reader knows where they are? Lack of progress markers correlates with low completion.

**Gate 6: Each lesson's central insight.** Can the team articulate the central insight of each lesson in one sentence? Lessons without a central insight are filler.

---

## Free tool gates

Free tools (calculators, quizzes, generators) earn the email when the result is meaningful.

**Gate 1: Meaningful result.** The output should help the reader make a decision or understand a situation. "Your score is 73" without interpretation is meaningless. Detail in `calculator-design` and `quiz-and-assessment-design`.

**Gate 2: Calculation transparency or methodology disclosure.** Detail in `calculator-design`.

**Gate 3: Email-capture honesty.** Detail in `calculator-design`.

---

## Ebook gates

An ebook earns the email when the resource produces value for readers who do not finish.

**Gate 1: Navigability.** Table of contents, page numbers, summary boxes. A reader who jumps to chapter 3 should be able to extract value without reading 1 and 2.

**Gate 2: Production quality consistent with the brand.** A poorly-produced ebook (typos, inconsistent formatting, low-resolution images) signals that the brand did not invest. The reader's expectation of the brand drops.

**Gate 3: Length honesty.** Is the page count honestly disclosed? "30-page guide" should mean 30 pages of substance, not 30 pages including 12 of brand-positioning.

**Gate 4: Chapter summaries.** Each chapter ends with a summary that lets a reader who skimmed extract the key insight. Summaries reduce the cost of skimming, which raises the value the reader gets even if they do not finish.

**Gate 5: First-chapter discipline.** The first chapter should deliver value, not warm up. Author bio and brand-positioning belong in the appendix or the about-the-author note, not chapter 1.

---

## Video series gates

A video series earns the email when production quality and consumption shape match the audience.

**Gate 1: Production quality consistent.** Audio clear, video stable, lighting reasonable. Production quality the brand can sustain across all videos.

**Gate 2: Runtime honesty.** Total runtime disclosed honestly. "5-video series" with one video 30 seconds and another 45 minutes is dishonest.

**Gate 3: Audio-first viability.** Many video viewers consume in audio-only contexts (commutes, exercise). Does the video work as audio? If the video has heavy on-screen reading required, the audio-only viewer loses the value.

**Gate 4: Transcripts available.** A transcript reaches the audience that prefers reading and improves accessibility.

**Gate 5: Each video standalone.** Same as the mini-course gate. A viewer who only watches video 1 should extract value.

---

## Cross-format gates

Some gates apply regardless of format.

**Gate A: The "would they pay for this" test.** Detail in `references/would-they-pay-for-this-test.md`.

**Gate B: Audience-fit signal.** Does the magnet attract the audience the brand serves? Detail in `references/audience-fit-qualification.md`.

**Gate C: Title-content alignment.** Does the magnet deliver on the title's specific promise? Detail in `references/title-and-presentation-discipline.md`.

**Gate D: First-impression quality.** Whatever the format, does the first impression (first page, first lesson, first calculator output) deliver something useful immediately?

**Gate E: Update cadence.** Is the magnet updated when references go stale, screenshots change, or methodology evolves? Stale magnets degrade the brand.

---

## When a magnet fails a gate

The magnet fails a gate. Now what.

**Option 1: Fix the magnet.** Add the worked example, narrow the scope, improve the production quality. Often the right answer.

**Option 2: Change the format.** Sometimes the topic is wrong for the chosen format. A topic that fails ebook gates might pass checklist gates.

**Option 3: Do not ship.** Some magnets should not exist. Killing the magnet at the gate stage is honest; shipping a failing magnet costs more than killing it.

The team's response to gate failures is the discipline marker. Strong programs fix or kill at the gate; weak programs ship despite failed gates and accept the downstream cost.

---

## The gate review process

Gates are most useful when applied as a structured pre-launch review.

**The review.**

- Identify the format.
- List the gates for that format (plus the cross-format gates).
- For each gate, score pass / fail / marginal.
- Marginal gates warrant strengthening before launch.
- Failed gates require redesign before launch.

**Who reviews.**

- The magnet's author should self-review.
- A second person (outside the magnet's authoring team) should also review. Outside-in honesty catches what the authoring team rationalizes.

**Document the review.** A short note on which gates passed and which were strengthened. Useful for future magnet design and team learning.

---

## Common gate failures

**Templates.** Generic prompts; no worked example; tool dependency hidden.

**Checklists.** Items that are not actionable; out-of-workflow order; thin item count.

**Swipe files.** Invented swipes; no attribution; uncategorized dump.

**Mini-courses.** Lessons that depend on each other; production quality decays; no clear next step.

**Free tools.** Vanity outputs without interpretation; misleading methodology; manipulative gates.

**Ebooks.** Poor navigability; production quality below brand standard; length padded with brand-positioning.

**Video series.** Inconsistent production; no transcripts; long runtime hidden.

The pattern across formats: the gates surface the failures that conversion-rate metrics hide. A magnet can convert at high rates while failing the gates; the gate failures show up downstream as poor lead quality and poor sequence engagement.

---

## Methodology-level choices that stay in the public skill

Per-format quality gates with specific tests. Cross-format gates. The gate review process. The decision tree when a magnet fails a gate. Common gate failures.

## Implementation choices that stay internal

Specific gate-scoring conventions for the team. Specific review processes and reviewers. Specific worked-example libraries. Specific production-quality benchmarks. Specific update-cadence calendars. These vary by team.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall