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.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/lead-magnet-design/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms covering natural user language, explicit 'when to use' guidance including situational triggers, and a clear niche that minimizes conflict with adjacent skills. The only minor note is that it's somewhat verbose, but the verbosity serves a purpose by covering edge-case trigger scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and deliverables: 'building gated content (ebooks, templates, checklists, swipe files, mini-courses, free tools)' and names specific anti-patterns (thin-bait, kitchen-sink-resource, earned-value-magnet). Clearly describes the discipline of designing lead magnets with standalone value while qualifying leads. | 3 / 3 |
Completeness | Clearly answers both 'what' (designing lead magnets that deliver standalone value while qualifying leads) and 'when' with explicit trigger terms and situational 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', 'when a lead magnet is being scoped for the first time'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'lead magnet, gated content, opt-in offer, ebook, checklist, template, swipe file, mini-course, free tool, content upgrade, freebie, opt-in, list-building offer.' These are all terms a marketer would naturally use when seeking help with this task. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche — lead magnet design specifically — with distinct triggers that are unlikely to conflict with general content marketing, email marketing, or copywriting skills. The specificity of the anti-pattern framework (thin-bait, kitchen-sink-resource, earned-value-magnet) further distinguishes it. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a well-structured essay on lead magnet philosophy rather than an actionable playbook. Its greatest weakness is verbosity: the thin-bait vs earned-value framing is repeated multiple times, format descriptions explain things Claude already knows, and the closing restates the entire thesis. The 12-consideration framework and quality gates provide useful structure, but the lack of concrete examples (sample titles with analysis, sample follow-up sequence outlines, before/after comparisons) keeps the skill at a strategic rather than executable level.
Suggestions
Cut content by 50%+ by removing repeated explanations of the thin-bait/kitchen-sink/earned-value framing (state it once, reference it thereafter) and eliminating explanations of what common formats are (Claude knows what a checklist is).
Add concrete, worked examples: a sample lead magnet title with analysis, a sample 7-day follow-up sequence outline, a before/after of a thin-bait magnet redesigned as an earned-value magnet.
Move detailed format descriptions and failure mode catalogs entirely into the referenced files rather than duplicating them inline, keeping only a summary table or brief list in the main SKILL.md.
Add explicit validation checkpoints to the 12-consideration framework (e.g., 'Run the would-they-pay test with 3 people in the target audience before proceeding to step 5').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~2800+ words. Extensively explains concepts Claude already understands (what thin-bait is, what templates are, what checklists are, what ebooks are). Multiple sections repeat the same ideas (the thin-bait vs earned-value framing appears at least 4 times). The closing section restates the entire skill's thesis. Significant padding with rhetorical flourishes that add no instructional value. | 1 / 3 |
Actionability | Provides conceptual frameworks and diagnostic questions (the 12 considerations, the 'would they pay' test, format-specific quality gates) that give some concrete guidance. However, there are no executable examples, no sample outputs, no templates to fill in, no concrete before/after examples of magnet titles or sequences. The guidance remains at the strategic/philosophical level rather than providing copy-paste-ready artifacts. | 2 / 3 |
Workflow Clarity | The 12-consideration framework provides a clear sequence for designing or auditing a lead magnet, and the delivery/follow-up section outlines a timeline (delivery moment, first 7 days, days 8-30). However, there are no explicit validation checkpoints or feedback loops—no 'if this fails, do X' branching, no concrete verification steps to confirm the magnet passes quality gates before launch. | 2 / 3 |
Progressive Disclosure | References to 9 separate reference files are well-organized and clearly signaled at the end, with inline references throughout. However, no bundle files were provided, so the references are unverifiable. More importantly, the SKILL.md itself is monolithic—much of the inline content (format descriptions, failure modes, quality gates) should have been pushed into the reference files rather than duplicated in the main body, undermining the progressive disclosure pattern. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
8e70d03
Table of Contents
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.