marketing-leads-generation

vasilyu1983/ai-agents-public · updated May 30, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/vasilyu1983/ai-agents-public --skill marketing-leads-generation
0 commentsdiscussion
summary

Built as a no-fluff execution skill for revenue-aligned demand generation.

skill.md

LEAD GENERATION — PIPELINE OS (OPERATIONAL)

Built as a no-fluff execution skill for revenue-aligned demand generation.

Structure: Core lead generation fundamentals first. AI-specific automation in clearly labeled "Optional: AI / Automation" sections.

Scope Boundary (Important)

This skill covers pipeline creation up to qualification and meeting booking (Lead/MQL/SQL/PQL definitions, routing, SLAs, and conversion). It does not cover late-stage closing work such as proposals, negotiation, procurement, contract redlines, or expansion.

If the user is asking for end-to-end sales execution (discovery-to-close), route to startup-sales-execution.


Core: Lead Type Definitions

Clear definitions prevent Sales/Marketing friction. Align on these before building pipeline.

Lead Type Definition Qualification Criteria Owner
Lead Any identified contact Has email/phone, some interest signal Marketing
MQL (Marketing Qualified Lead) Fits ICP + engaged with marketing Firmographic fit + behavior threshold Marketing
SQL (Sales Qualified Lead) Ready for sales conversation MQL + explicit buying signal or demo request Sales
PQL (Product Qualified Lead) Used product, shows upgrade potential Trial/freemium + usage threshold Product + Sales
SAL (Sales Accepted Lead) SQL accepted by sales rep Sales confirms qualification after first contact Sales

What “Good” Looks Like (Operational)

Set targets from your own baseline, then improve stage-by-stage:

  • Sales acceptance rate (SQL → SAL)
  • Speed-to-lead (time to first touch)
  • Stage conversion rates and time-in-stage
  • Pipeline created per channel (not leads)

Core: Funnel Design Framework

Stage User State Content/Action Goal
Awareness Problem-aware Blog, social, SEO, ads Capture attention
Interest Solution-curious Guides, webinars, comparisons Capture contact info
Consideration Evaluating options Case studies, demos, free tools Convert to MQL
Decision Ready to buy Pricing, proposals, trials Convert to SQL → Opportunity
Activation New customer Onboarding, training, quick wins Reduce churn, increase expansion

Funnel Diagnostic Questions

  1. Where is the biggest drop-off? (Measure stage-to-stage conversion)
  2. What's your time-in-stage for each? (Long times = friction)
  3. Are leads skipping stages? (May indicate misalignment)
  4. What percentage of MQLs get accepted by Sales? (Low = quality issue)

For full funnel setup including MQL/SQL criteria and SLAs, use lead-funnel-definition.md.


Core: Gating Strategy

Not all content should be gated. Use this decision framework:

Content Type Gate? Why
Blog posts, how-to guides No Build SEO, trust, awareness
Comparison guides, buyers guides Light gate (email only) High intent, worth capturing
Industry reports, original research Gate High value, worth exchange
ROI calculators, assessments Gate Strong buying signals
Product demos, pricing Gate Direct sales intent
Case studies Optional Gate if detailed; ungate if brief

Do (Gating)

  • Ask only for fields you'll use (email + company is often enough)
  • Progressive profiling: collect more data over multiple interactions
  • A/B test gated vs ungated for the same content
  • Honor the value exchange: gated content must deliver real value

Avoid (Gating)

  • Gating everything (kills organic discovery)
  • Long forms for top-of-funnel content (start with the minimum fields you will use)
  • Requiring phone number for early-stage content
  • Gating content that's freely available elsewhere

Core: Attribution Fundamentals + Limitations

Attribution Models

Model How It Works Best For Limitation
First-touch 100% credit to first interaction Understanding awareness sources Ignores nurture journey
Last-touch 100% credit to final touch Understanding closing sources Ignores awareness
Linear Equal credit to all touches Simple multi-touch Over-credits low-value touches
Time-decay More credit to recent touches Long sales cycles Complex to implement
Position-based 40/20/40 to first/middle/last Balanced view Still somewhat arbitrary

What Attribution Cannot Tell You

  • Offline influence: Trade shows, word-of-mouth, podcast listens
  • Dark social: Slack shares, private LinkedIn DMs, email forwards
  • Buying committee dynamics: Multiple stakeholders, different journeys
  • True incrementality: Would they have converted anyway?

Do (Attribution)

  • Use attribution as directional signal, not absolute truth
  • Combine with qualitative data (ask "how did you hear about us?")
  • Focus on trends over time, not single-touchpoint credit
  • Match attribution model to your sales cycle length

Avoid (Attribution)

  • Treating attribution as ground truth
  • Cutting channels based solely on last-touch data
  • Over-investing in attribution tooling before conversion tracking and decision-making are solid
  • Ignoring brand/awareness because it's hard to attribute

Core: Lead Quality vs Volume Tradeoffs

The 2025 reality: precision > volume. Longer sales cycles and larger buying committees mean quality matters more than ever.

Strategy Quality Volume Best When
Volume play Lower Higher New market, testing channels, brand building
Precision play Higher Lower Known ICP, limited SDR capacity, high ACV
Balanced Medium Medium Most B2B companies

Quality Signals (Prioritize These)

  • ICP firmographic match (industry, size, geo)
  • Explicit intent signals (demo request, pricing page, competitor comparison)
  • Engagement depth (multiple pages, return visits, long time on site)
  • Decision-maker title

Warning Signs (Low Quality)

  • High MQL volume but low Sales acceptance rate (materially below baseline)
  • Lead-to-opportunity time increasing (pipeline drag)
  • High early-stage drop-off in demos/calls
  • Leads requesting irrelevant features

Core: Account-Based Sales (ABS)

ABS is often effective in B2B when targeting high-value accounts with complex buying committees.

When to Use ABS

Criteria Threshold Why
ACV >$25K Worth the research investment
TAM <5,000 accounts Finite, targetable market
Buying committee 3+ stakeholders Multi-threaded approach needed
Sales cycle >60 days Time to nurture relationships

ABS Execution Framework

Element Execution Resource
Target list 50-200 named accounts, tiered (Tier 1: 20, Tier 2: 50, Tier 3: 130) assets/channel-plan-30-60-90.md
Account research Pain points, tech stack, recent news, org chart 30 min per Tier 1 account
Multi-threading 3-5 contacts per account across roles Champion + economic buyer + user
Custom content Pain-specific messaging per tier Tier 1: fully custom; Tier 2: semi-custom
Orchestration Coordinated email + LinkedIn + ads + events Sequence all channels
Measurement Account engagement score, pipeline per account Add to assets/lead-scoring-model.md

Do (ABS)

  • Start with Tier 1 (highest value) to prove the motion
  • Coordinate Sales + Marketing on account selection and messaging
  • Use intent data to prioritize accounts showing buying signals
  • Track account-level metrics, not just lead-level

Avoid (ABS)

  • Running ABS on >200 accounts (becomes spray-and-pray)
  • Treating ABS as "just personalized email" (it's full orchestration)
  • Skipping account research (generic outreach defeats the purpose)
  • Single-threading accounts (champion leaves = deal dies)

When to Use This Skill

  • Pipeline build/rehab: net-new SQL targets, revive stalled funnels, rebalance channel mix
  • Outbound motions: cold email/LinkedIn, call scripts, reply handling, objection rebuttals
  • Landing/CRO: fix hero/offer/CTA, forms, proof, trust, and post-click routing
  • Lead scoring/routing: MQL/SQL thresholds, SDR/AE handoff, SLA design
  • Experiment cadence: 30/60/90 test plans, ICE/PIE scoring, stop/scale rules
  • Compliance/deliverability: CAN-SPAM/GDPR hygiene, domain warmup, opt-out, DKIM/SPF/DMARC
  • Account-based sales (ABS): named account targeting, multi-threaded outreach, account scoring

When NOT to Use This Skill

Use related skills instead for:


Quick Reference

Task SOP/Template Location When to Use
Define ICP + Offer ICP & Offer Sprint See Operational SOPs → ICP & Offer Before messaging, bidding, or list-building
Channel Plan 30/60/90 Test Plan Grid See Operational SOPs → Channel Plan New market motion or quarterly reset
Email/LinkedIn Cadence 5-touch skeleton (CTA-first) See Operational SOPs → Email/LinkedIn Cadences Cold/prospecting or nurture
Cold Call Script Talk track w/ discovery See Operational SOPs → Cold Call Script Live outbound, event follow-up
Landing Fix Hero/offer/proof/CTA/form checklist See Operational SOPs → Landing Page Fix Low CVR or ad-to-page mismatch
Lead Scoring & Routing Points + SLA See Operational SOPs → Lead Scoring + Routing SDR/AE handoff, CAC/SQL drift
Speed-to-Lead OS Response + reminders See Operational SOPs → Speed-to-Lead Reply/no-show issues, inbox speed
Experiment Matrix ICE/PIE + stop/scale See Operational SOPs → Experiment Matrix Weekly prioritization
Compliance/Deliverability Authentication + opt-out See Operational SOPs → Compliance & Deliverability Cold email/domain health
Email Deliverability 2025 Bulk sender requirements assets/email-deliverability-2025.md Bulk sending (5,000+/day to Gmail), new domains
LinkedIn Outreach Safety Terms-compliant outreach guardrails assets/linkedin-automation-safety-2025.md LinkedIn outreach risk reduction

Decision Tree (Pipeline Triage)

Leads low?
├─ ICP/offer unclear → Run ICP & Offer Sprint → ship 3 hooks (pain/risk/value) → retest
├─ Channel skewed → Add 2nd channel (LI + email OR retargeting) → small-budget test
└─ Volume ok, quality low → Tighten filters + Lead Scoring → reroute + new CTA

Replies low?
├─ Open rate materially below baseline (or bounces/complaints rising) → Fix list quality + auth + subject/hook
└─ Opens ok, replies low → Rewrite CTA (one action), add proof/trigger, shorten to ≤120 words

Bookings low but replies? → Add Speed-to-Lead + 2 follow-ups + calendar drop + friction audit

Traffic ok, CVR low?
├─ Message mismatch → Rewrite hero/CTA to match ad/pain
├─ Proof light → Add 3 proof types (metric case, logo, testimonial)
└─ Form friction → Reduce fields, add multi-step or chat, highlight privacy/trust

Operational SOPs (Fast Execution)

ICP & Offer Sprint (90 minutes)

  • Pull top 10 wins/losses; extract firmographic + trigger + objection patterns.
  • Draft 3 offers: pain-killer, speed/automation, risk reversal. Each with 1 quantified proof + 1 urgency lever.
  • Ship 3 hooks for LI/email: pain, risk/cost of inaction, better future. Keep CTA singular (fit check/demo/audit).

Pipeline Health Checklist (Weekly)

  • Confirm stage definitions (MQL/SQL/SAL) are unchanged (no silent drift).
  • Check SQL → SAL acceptance rate vs baseline; investigate top rejection reasons if down.
  • Check speed-to-lead median and p90 vs SLA; fix routing/alerts if breached.
  • Review bounce/complaint/unsubscribe trends; pause sends if complaints spike.
  • Verify list hygiene: suppress bounces/unsubs/complaints; remove role accounts where required.
  • Validate 2 outbound sequences against a control (reply rate and meeting rate), not opens/clicks.
  • Review landing page CVR vs baseline by top traffic sources; flag message mismatch.
  • Confirm forms capture only fields in use; remove any unused “nice-to-have” fields.
  • Audit routing: highest-intent leads go to humans first; bots/automation only assist.
  • Confirm attribution model is consistent this week (no reporting changes mid-period).
  • Inspect pipeline created per channel (not leads) and reallocate effort to top 2 plays.
  • Review show rate and no-show reasons; add reminders or friction fixes if slipping.
  • Pull 5 recent wins and 5 losses; update ICP triggers/objections accordingly.
  • Align with Sales on next-week target accounts (ABS) and the primary CTA per segment.
  • Document one change per channel (email/LI/landing) with a hypothesis and stop/scale rule.

Channel Plan (30/60/90)

  • 30d: Validate 2 hooks across email + LinkedIn (connection + DM) + 1 retargeting format. Targets: reply rate + CPL guardrails set from your baseline; protect lead quality (Sales acceptance, SQL rate).
  • 60d: Keep winners; add webinar/workshop or partner/referral. Layer nurture (value drops) + remarketing.
  • 90d: Scale top 2 plays; add lead scoring + SDR SLAs; kill underperformers that stay below an agreed guardrail after a fair sample. Review CAC, SQL→opp→win.

Email/LinkedIn Cadences (3–6 touches)

  • Touch 1: Pain hook + proof + single CTA + opt-out. 70–120 words.
  • Touch 2: Mini-case (before/after metric) + CTA to booking link.
  • Touch 3: Objection handling (security/integration/budget) + CTA to quick fit check.
  • Touch 4–6: Cost-of-inaction math, social proof, light bump. Always include opt-out and compliance footer.
  • LinkedIn: Connect (no pitch) → Value drop (post/DM) → Soft CTA (benchmark/mini-audit) → Nudge. Add voice note if high-intent.

Cold Call Script (Talk Track)

  • Opener: Permission + value in one line; avoid “Did I catch you…”.
  • Discovery: 3 questions (current tool/flow, pain metric, trigger/priority).
  • Value hits: Match top pain; cite one proof; propose next step.
  • Objections: Acknowledge → brief proof → micro-commit (share stack/book 15m).
  • Close: Time-bound CTA (this week) + send calendar while on call.

Landing Page Fix (Offer-First)

  • Hero: Problem + outcome + proof; CTA above fold. Mirror ad/sequence language.
  • Offer: 3 bullets (value, speed, risk reversal). Add pricing cue if helpful.
  • Proof: Logo strip + 1 metric case + 1 testimonial; add compliance/trust (security, certifications).
  • Form: Reduce fields; add multi-step or chat; auto-email/SMS confirmation; show privacy/opt-out.
  • Tests: Hero variant (pain vs outcome), CTA text, social proof block, form length, risk reversal.

Lead Scoring + Routing

  • Score dimensions: Fit (industry/size/role), Intent (page depth, replies), Behavior (demo request, resource download).
  • [Inference] Example points: Fit (0–40), Intent (0–40), Behavior (0–20). MQL ≥60; SQL ≥75 with decision role or demo intent.
  • Routing: MQL → SDR within 15 minutes; SQL → AE calendar hold. SLA: first touch <15m, 2nd touch <2h, 3rd touch same day.

Speed-to-Lead OS

  • Inbox+CRM alerts (email, Slack, mobile). Auto-response with calendar link.
  • Sequence: T0 min: reply/confirm; T+15m: value drop + booking; T+4h: nudge + social proof; T+24h: call + SMS (if consent).
  • Track: response time, booking rate, no-show rate; add reminders + backup rep if no response.

Experiment Matrix

  • Score ideas weekly (ICE/PIE). Run 3–5 tests max; cap blast radius (budget/volume).
  • Stop if below an agreed guardrail after minimum sample; scale only after repeatable lift across consecutive checks.
  • Log: hypothesis, owner, start/end, sample size, metric, decision (stop/scale/iterate).

Compliance & Deliverability (Operational Checklist)

Goal: Sustain deliverability and protect brand trust while running outbound and nurture.

Spam Rate Thresholds (Critical — 2025 Enforcement)

  • Gmail/Yahoo/Microsoft hard ceiling: 0.3% complaint rate
how to use marketing-leads-generation

How to use marketing-leads-generation on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add marketing-leads-generation
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/vasilyu1983/ai-agents-public --skill marketing-leads-generation

The skills CLI fetches marketing-leads-generation from GitHub repository vasilyu1983/ai-agents-public and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/marketing-leads-generation

Reload or restart Cursor to activate marketing-leads-generation. Access the skill through slash commands (e.g., /marketing-leads-generation) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.657 reviews
  • Ganesh Mohane· Dec 28, 2024

    Keeps context tight: marketing-leads-generation is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kaira Ramirez· Dec 24, 2024

    marketing-leads-generation reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Zaid Verma· Dec 16, 2024

    We added marketing-leads-generation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Alexander Choi· Dec 12, 2024

    Registry listing for marketing-leads-generation matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Daniel Chawla· Dec 8, 2024

    marketing-leads-generation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Amelia Ramirez· Nov 27, 2024

    Solid pick for teams standardizing on skills: marketing-leads-generation is focused, and the summary matches what you get after install.

  • Sakshi Patil· Nov 19, 2024

    marketing-leads-generation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Diego Gonzalez· Nov 15, 2024

    I recommend marketing-leads-generation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Anika Bansal· Nov 3, 2024

    Useful defaults in marketing-leads-generation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Camila Haddad· Oct 22, 2024

    I recommend marketing-leads-generation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 57

1 / 6