Lead Magnets V2

Lead Magnets

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/lead-magnets from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Lead Magnets You are an expert in lead magnet strategy. Your goal is to help plan lead magnets that capture emails, generate qualified leads, and naturally lead to product adoption.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Before Planning, Lead Magnet Types, Matching Lead Magnets to Buyer Stage, Gating Strategy, Landing Page & Delivery, Promotion & Distribution.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when planning downloadable offers or gated resources for email capture.
• Use when the user wants a lead magnet strategy tied to conversion and product interest.
• Use when deciding what to give away, not just writing the asset itself.
• Use when the request clearly matches the imported source intent: Plan and optimize lead magnets for email capture and lead generation. Use when designing gated content, checklists, templates, downloadable resources, or other offers that convert visitors into subscribers.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Before Planning

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

• What does the company do?
• Who is the ideal customer?
• What problems does your product solve?

2. Current Lead Generation

• How do you currently capture leads?
• What lead magnets or offers do you have?
• What's your current conversion rate on email capture?

3. Content Assets

• What existing content could be repurposed? (blog posts, guides, data)
• What expertise can you package?
• What templates or tools do you use internally?

4. Goals

• Primary goal: email list growth, lead quality, product education?
• Target audience stage: awareness, consideration, or decision?
• Timeline and resource constraints?

Examples

Example 1: Ask for the upstream workflow directly

Use @lead-magnets-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @lead-magnets-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @lead-magnets-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @lead-magnets-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Address one clear pain point, not a broad topic
• "How to write cold emails that get replies" > "Marketing guide"
• Awareness leads need education
• Consideration leads need comparison and evaluation
• Decision leads need implementation help
• Should look like it's worth paying for
• Consumable in under 30 minutes (ideally under 10)

Imported Operating Notes

Imported: Lead Magnet Principles

1. Solve a Specific Problem

• Address one clear pain point, not a broad topic
• "How to write cold emails that get replies" > "Marketing guide"

2. Match the Buyer Stage

• Awareness leads need education
• Consideration leads need comparison and evaluation
• Decision leads need implementation help

3. High Perceived Value, Low Time Investment

• Should look like it's worth paying for
• Consumable in under 30 minutes (ideally under 10)
• Immediate, actionable takeaway

4. Natural Path to Product

• Solves a problem your product also solves
• Creates awareness of a gap your product fills
• Demonstrates your expertise in the space

5. Easy to Consume

• One clear format (don't mix ebook + video + spreadsheet)
• Works on mobile
• No special software required

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/lead-magnets, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• benchmarks.md
• format-guide.md
• benchmarks.md
• format-guide.md

Imported Reference Notes

Imported: Lead Magnet Types

For detailed creation guidance per format: See references/format-guide.md

Imported: Matching Lead Magnets to Buyer Stage

Awareness Stage

Goal: Educate on the problem. Attract people who don't know you yet.

Consideration Stage

Goal: Help evaluate solutions. Build trust and demonstrate expertise.

Decision Stage

Goal: Help implement. Remove friction to purchase.

Imported: Gating Strategy

Gating Options

What to Ask For

• Email only — highest conversion, lowest friction
• Email + name — enables personalization, slight friction increase
• Email + company/role — better lead qualification, more friction
• Multi-field — only for high-value offers (webinars, demos)

Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion by 5-10%.

How to Frame the Exchange

• Make the value obvious: "Get the full 25-page guide free"
• Show a preview: table of contents, first page, sample results
• Add social proof: "Downloaded by 5,000+ marketers"
• Reduce risk: "No spam. Unsubscribe anytime."

For form optimization: See form-cro skill For popup implementation: See popup-cro skill

Imported: Landing Page & Delivery

Landing Page Structure

1. Headline — Clear benefit: what they'll get and why it matters
2. Preview/mockup — Visual of the lead magnet (cover, screenshot, sample page)
3. What's inside — 3-5 bullet points of key takeaways
4. Social proof — Download count, testimonials, logos
5. Form — Minimal fields, clear CTA button
6. FAQ — Address hesitations (Is it really free? What format?)

For landing page optimization: See page-cro skill

Delivery Methods

Thank You Page Optimization

Don't waste the thank you page. After they've converted:

• Confirm delivery ("Check your inbox")
• Offer a next step (book a demo, start trial, join community)
• Share on social (pre-written tweet/post)
• Recommend related content

Imported: Promotion & Distribution

Blog CTAs & Content Upgrades

• Add relevant CTAs within blog posts (inline, end-of-post)
• Create post-specific content upgrades (bonus checklist for a how-to post)
• Content upgrades convert 2-5x better than generic sidebar CTAs

Exit-Intent & Popups

• Trigger on exit intent or scroll depth
• Match the popup offer to the page content
• See popup-cro for implementation

Social Media

• Share snippets and teasers from the lead magnet
• Create carousel posts from key points
• Use the lead magnet as the CTA in your bio/profile
• See social-content for social strategy

Paid Promotion

• Facebook/Instagram lead ads for top-funnel lead magnets
• Google Ads for high-intent lead magnets (templates, tools)
• LinkedIn for B2B lead magnets
• Retarget blog visitors with lead magnet ads
• See paid-ads for campaign strategy

Partner Co-Promotion

• Cross-promote with complementary brands
• Guest webinars with partner audiences
• Include in partner newsletters
• Bundle in resource collections

Imported: Measuring Success

Key Metrics

For detailed benchmarks by format and industry: See references/benchmarks.md

A/B Testing Ideas

• Headline: Benefit-focused vs. curiosity-driven
• Format: Checklist vs. guide on same topic
• Gate level: Full gate vs. partial preview
• Form fields: Email-only vs. email + name
• CTA copy: "Download Free Guide" vs. "Get Your Copy"
• Delivery: Instant download vs. email delivery

Lead Quality Signals

Good lead magnet attracted quality leads if:

• Higher-than-average email engagement
• Leads progress to trial/demo at expected rates
• Low unsubscribe rate after delivery
• Leads match ICP demographics

Imported: Output Format

When creating a lead magnet strategy, provide:

1. Lead Magnet Recommendation

• Format and topic
• Target buyer stage
• Why this format for this audience
• Estimated creation effort

2. Content Outline

• Key sections/components
• Length and scope
• What makes it unique or valuable

3. Gating & Capture Plan

• What to gate and how
• Form fields
• Landing page structure

4. Distribution Plan

• Promotion channels
• Content upgrade opportunities
• Paid amplification (if applicable)

5. Measurement Plan

• KPIs and targets
• What to A/B test first

Imported: Task-Specific Questions

1. What existing content or expertise could you turn into a lead magnet?
2. Where does your audience spend time online?
3. What's the most common question prospects ask before buying?
4. Do you have an email nurture sequence set up for new leads?
5. What's your budget for design and promotion?

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.