CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lead-magnet-design

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured methodology skill body with excellent progressive disclosure (all references real, one level deep, clearly signaled) and mostly actionable, opinionated guidance including worked title examples, a litmus test, per-format gates, and a 12-consideration framework. The main weakness is conciseness: the intro and closing recap earlier material, and the keystone framing is repeated three times across the body.

Suggestions

Trim the opening section and the closing section ("Closing: magnets earn the email when they earn the reader's afternoon"): both recap the frontmatter description and restate the thin-bait/kitchen-sink/earned-value distinction already covered in its own keystone section, cutting roughly 30-40 lines without losing guidance.

Move the full per-format breakdowns ("Templates... Checklists... Swipe files... Ebooks...") into references/format-selection-patterns.md, keeping only a one-line strength/weakness summary per format in the body, since the detail file already exists for exactly this content.

Add explicit validation criteria to the 12-consideration framework steps (e.g., what evidence confirms 'format matched to audience and topic'), and state the fix-and-retry loop for failed considerations as concretely as the existing 'If it fails, redesign before launching' rule.

DimensionReasoningScore

Conciseness

The 288-line body is mostly efficient and opinionated, but contains real repetition: the thin-bait/kitchen-sink-resource/earned-value-magnet framing appears in the intro, its own keystone section, and again in the closing; the closing section ("The discipline is in the design choices upstream of the form... The format matched... The title that filters...") restates nearly every earlier section; and the opening paragraphs largely duplicate the frontmatter description. It is not 2 because each section still carries distinctive decision guidance Claude would not generate identically; not 4 because the intro and closing recap are unnecessary explanation that could be trimmed.

3 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: literal title patterns with worked examples ("The B2B onboarding email sequence that 3x'd our 14-day activation rate (for SaaS founders)"), a hands-on litmus test ("Hand the magnet to a non-subscriber in the target audience. Watch them use it."), per-format quality gates phrased as checkable questions, and a 12-item design/audit framework. It is not 5 because some passages remain conceptual prose ("The honest answer matters", "The test is not perfect") and there are no copy-paste-ready output templates; not 3 because concrete examples and decision rules cover the common cases well.

4 / 5

Workflow Clarity

"When designing or auditing a lead magnet, walk these 12 considerations" gives a clear ordered sequence, and there are explicit pass/fail checkpoints ("If the magnet passes the test, it earns the email. If it fails, redesign before launching"). It is not 5 because the feedback-loop discipline (validate -> fix -> retry) is applied to only a couple of steps rather than woven through the framework, and the 12 considerations are stated without per-step validation criteria; not 3 because the sequence is coherent and key checkpoints are explicit.

4 / 5

Progressive Disclosure

Structure is exemplary: every section ends with a clearly signaled one-level-deep pointer ("Detail in [`references/format-selection-patterns.md`](references/format-selection-patterns.md)"), all 9 referenced files exist in the bundle, none reference further files, and a consolidated "Reference files" index lists each with a one-line description. It is not 4 because navigation, signaling, and the split between inline overview and reference detail leave no organizational gaps.

5 / 5

Total

16

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states the what and the when explicitly with an unusually thorough set of natural trigger terms, in third person, without fluff or over-claims. The only weaknesses are minor — action verbs stay at the design-methodology altitude, and a few generic trigger terms (checklist, template) create small overlap risk with adjacent skills.

DimensionReasoningScore

Specificity

The description lists several concrete artifact types ("ebooks, templates, checklists, swipe files, mini-courses, free tools") and concrete design actions ("delivers genuine standalone value while qualifying the lead and warming them for what comes next"), but the action coverage stays at the design-methodology level with minor gaps. It is not 5 because it does not comprehensively enumerate the actions (designing, auditing, format selection, follow-up sequence design) the way a 5-anchor description would; not 3 because it goes well beyond naming the domain with 1-2 actions.

4 / 5

Completeness

It explicitly answers both what ("Designing lead magnets that earn the email. The discipline of building gated content... that delivers genuine standalone value while qualifying the lead") and when ("Triggers on lead magnet, gated content, opt-in offer, ebook..." and "Also triggers when an audience is being asked for an email... when previous lead magnets converted but did not produce qualified leads, or when a lead magnet is being scoped for the first time") with concrete trigger phrases. This matches the 5 anchor exactly; not 4 because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

"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" is a comprehensive list of natural terms a user would actually say, including synonyms and common variations. It is not 4 because essentially no natural phrasing for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

The description carves a clear niche with distinct triggers ("lead magnet, gated content, opt-in offer, swipe file" are unlikely to fire the wrong skill), but broadly applicable terms like "checklist", "template", and "free tool" carry minor overlap risk with document- or tool-creation skills. It is not 5 because of that residual generic-term overlap; not 3 because the dominant framing is unmistakably specific to lead magnet design.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/lead-magnet-design/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.