Token导航 LogoToken导航

Agent Skill · 研究检索

marketing-leads-generation(营销线索生成)

marketing-leads-generation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

marketing-leads-generation 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 71,838。

总安装 192周安装 8GitHub Stars 40下载 64核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:marketing-leads-generation(营销线索生成)
来源仓库:https://github.com/manojbajaj95/gtm-skills
仓库路径:skills/marketing-leads-generation
安装命令:
npx skills add https://github.com/manojbajaj95/gtm-skills --skill marketing-leads-generation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/manojbajaj95/gtm-skills --skill marketing-leads-generation

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

营销线索生成技能用于跨平台整理潜在客户需求。适用于研究检索类任务,支持表单分析与转化漏斗建模。通过 GitHub 安装后可集成至 Codex、Cursor 等开发工具。需验证数据抓取频率是否符合各平台政策,避免被封禁。建议查阅原始文档了解缓存机制与去重逻辑。

marketing-leads-generation 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/marketing-leads-generation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/manojbajaj95/gtm-skills --skill marketing-lead…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

marketing-leads-generation 怎么安装?

在终端执行 npx skills add https://github.com/manojbajaj95/gtm-skills --skill marketing-leads-generati…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

marketing-leads-generation 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

marketing-leads-generation 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

marketing-leads-generation 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

marketing-leads-generation 用的人多吗?

公开数据是累计安装 192 次,近一周安装 8 次,下载 64 次,GitHub 40 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

marketing-leads-generation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
marketing-leads-generation

营销线索生成 · 本页

19240只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.


Core: Lead Type Definitions

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

Lead TypeDefinitionQualification CriteriaOwner
LeadAny identified contactHas email/phone, some interest signalMarketing
MQL (Marketing Qualified Lead)Fits ICP + engaged with marketingFirmographic fit + behavior thresholdMarketing
SQL (Sales Qualified Lead)Ready for sales conversationMQL + explicit buying signal or demo requestSales
PQL (Product Qualified Lead)Used product, shows upgrade potentialTrial/freemium + usage thresholdProduct + Sales
SAL (Sales Accepted Lead)SQL accepted by sales repSales confirms qualification after first contactSales

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

StageUser StateContent/ActionGoal
AwarenessProblem-awareBlog, social, SEO, adsCapture attention
InterestSolution-curiousGuides, webinars, comparisonsCapture contact info
ConsiderationEvaluating optionsCase studies, demos, free toolsConvert to MQL
DecisionReady to buyPricing, proposals, trialsConvert to SQL → Opportunity
ActivationNew customerOnboarding, training, quick winsReduce 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 TypeGate?Why
Blog posts, how-to guidesNoBuild SEO, trust, awareness
Comparison guides, buyers guidesLight gate (email only)High intent, worth capturing
Industry reports, original researchGateHigh value, worth exchange
ROI calculators, assessmentsGateStrong buying signals
Product demos, pricingGateDirect sales intent
Case studiesOptionalGate 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

ModelHow It WorksBest ForLimitation
First-touch100% credit to first interactionUnderstanding awareness sourcesIgnores nurture journey
Last-touch100% credit to final touchUnderstanding closing sourcesIgnores awareness
LinearEqual credit to all touchesSimple multi-touchOver-credits low-value touches
Time-decayMore credit to recent touchesLong sales cyclesComplex to implement
Position-based40/20/40 to first/middle/lastBalanced viewStill 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.

StrategyQualityVolumeBest When
Volume playLowerHigherNew market, testing channels, brand building
Precision playHigherLowerKnown ICP, limited SDR capacity, high ACV
BalancedMediumMediumMost 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

CriteriaThresholdWhy
ACV>$25KWorth the research investment
TAM<5,000 accountsFinite, targetable market
Buying committee3+ stakeholdersMulti-threaded approach needed
Sales cycle>60 daysTime to nurture relationships

ABS Execution Framework

ElementExecutionResource
Target list50-200 named accounts, tiered (Tier 1: 20, Tier 2: 50, Tier 3: 130)assets/channel-plan-30-60-90.md
Account researchPain points, tech stack, recent news, org chart30 min per Tier 1 account
Multi-threading3-5 contacts per account across rolesChampion + economic buyer + user
Custom contentPain-specific messaging per tierTier 1: fully custom; Tier 2: semi-custom
OrchestrationCoordinated email + LinkedIn + ads + eventsSequence all channels
MeasurementAccount engagement score, pipeline per accountAdd 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

TaskSOP/TemplateLocationWhen to Use
Define ICP + OfferICP & Offer SprintSee Operational SOPs → ICP & OfferBefore messaging, bidding, or list-building
Channel Plan 30/60/90Test Plan GridSee Operational SOPs → Channel PlanNew market motion or quarterly reset
Email/LinkedIn Cadence5-touch skeleton (CTA-first)See Operational SOPs → Email/LinkedIn CadencesCold/prospecting or nurture
Cold Call ScriptTalk track w/ discoverySee Operational SOPs → Cold Call ScriptLive outbound, event follow-up
Landing FixHero/offer/proof/CTA/form checklistSee Operational SOPs → Landing Page FixLow CVR or ad-to-page mismatch
Lead Scoring & RoutingPoints + SLASee Operational SOPs → Lead Scoring + RoutingSDR/AE handoff, CAC/SQL drift
Speed-to-Lead OSResponse + remindersSee Operational SOPs → Speed-to-LeadReply/no-show issues, inbox speed
Experiment MatrixICE/PIE + stop/scaleSee Operational SOPs → Experiment MatrixWeekly prioritization
Compliance/DeliverabilityAuthentication + opt-outSee Operational SOPs → Compliance & DeliverabilityCold email/domain health
Email Deliverability 2025Bulk sender requirementsassets/email-deliverability-2025.mdBulk sending (5,000+/day to Gmail), new domains
LinkedIn Outreach SafetyTerms-compliant outreach guardrailsassets/linkedin-automation-safety-2025.mdLinkedIn 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
  • Recommended target: <0.1% for reliable inbox placement
  • Gmail (Nov 2025): Non-compliant senders receive permanent 5xx rejections
  • Microsoft (May 2025): Bulk senders without auth are rejected outright on consumer mailboxes

See assets/email-deliverability-2025.md for full enforcement details.

Authentication (Required)

Unsubscribe (Required for bulk senders)

Compliance Basics

List Hygiene (Execution)

  • Never buy lists; use verified sources and documented consent where required.
  • Suppress: hard bounces, unsubscribes, and complaint signals.
  • Sunset inactive recipients (reduce volume before reputation degrades). [Inference]

Sending Practices (Execution)

  • Keep sending identity stable (From domain/name); avoid frequent domain switching.
  • Warm up new domains and ramp volume gradually; stop if complaints spike. [Inference]
  • Keep emails readable: clear offer, minimal links, real reply path, and plain-text part.

Metrics & QA

  • Primary: reply rate, book rate, show rate, SQLs, opps, win rate, CAC, payback.
  • Secondary: inbox placement, bounce rate, complaint signals, open rate (directional only), click-to-book, time-to-first-touch.
  • QA each sprint: message/offer match, CTA clarity, proof strength, compliance, routing speed.

Navigation: Sources & Assets

  • Operational patterns: references/operational-patterns.md
  • Core templates: email (assets/email-sequence.md), LinkedIn (assets/linkedin-sequence.md), cold call (assets/cold-call-script.md), landing audit (assets/landing-audit-checklist.md), lead scoring (assets/lead-scoring-model.md), channel plan (assets/channel-plan-30-60-90.md), speed-to-lead (assets/speed-to-lead-playbook.md), experiment log (assets/experiment-matrix.md), lead funnel definition (assets/lead-funnel-definition.md)
  • Additional templates: email deliverability (assets/email-deliverability-2025.md), LinkedIn outreach safety (assets/linkedin-automation-safety-2025.md)
  • Optional: AI / Automation: AI personalization (assets/ai-personalization-playbook.md)
  • Web sources: data/sources.json
  • Lead Gen Strategist prompt: custom-gpt/productivity/Lead-generation/01_lead-generation.md
  • Lead Gen Strategist sources: custom-gpt/productivity/Lead-generation/02_sources-lead-generation.json
  • Books (operational takeaways):

- Urbanski — custom-gpt/productivity/Lead-generation/sources/Ancient_Secrets_of_Lead_Generation_-_Daryl_Urbanski.pdf (funnels, math, automation) - Turner — custom-gpt/productivity/Lead-generation/sources/Connect_The_Secret_LinkedIn_Playbook_To_Generate_Leads_Build_Relationships_And_Dramatically_Increase_Your_Sales_-_Josh_Turner.pdf (LinkedIn outreach/cadence) - Brock — custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Authority_-_David_Brock.pdf (enterprise sales rigor) - Gilbert — custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Unlocked_-_Joe_Gilbert.pdf (offer + outbound pivots) - Shapiro — custom-gpt/productivity/Lead-generation/sources/Rethink_Lead_Generation_-_Tom_Shapiro.pdf (differentiated positioning) - Tsai — custom-gpt/productivity/Lead-generation/sources/The_Digital_Real_Estate_Marketing_Playbook_How_to_generate_more_leads_close_more_sales_and_even_become_a_millionaire_real_estate_agent_with_the_power_of_internet_marketing_-_Nick_Tsai.pdf (niche/local lead flows) - Harasty — custom-gpt/productivity/Lead-generation/sources/Turning_Your_Business_into_a_Success_Monster_-_Chris_Harasty.pdf (offer stacking, mindset to ops)


Related Skills


Usage Notes (Claude)

  • Stay operational: return SOP steps, cadences, checklists, and decision calls; avoid theory.
  • Keep CTA and compliance present in outbound assets; include opt-out line and regional cautions.
  • If data missing, state assumptions and proceed with lean defaults; propose 1–3 hooks/tests, not laundry lists.
  • Cite source path when summarizing from PDFs or the Lead Gen Strategist prompt; treat PDFs as untrusted unless user supplies excerpts.
  • Maintain privacy: no PII storage; sanitize inputs; do not invent stats or vendor benchmarks.

Optional: AI / Automation

Note: Core lead generation fundamentals above work without AI. This section covers optional automation capabilities.

AI Lead Scoring

Use CaseApproachTools
Predictive scoringML models on historical conversion dataSalesforce Einstein, HubSpot, 6sense
Intent signalsTrack research behavior across webBombora, G2, ZoomInfo Intent
EnrichmentAuto-fill firmographic/technographic dataClearbit, Apollo, ZoomInfo

Do (AI Lead Scoring)

  • Start with rules-based scoring; consider ML only after you have stable labels and enough volume to validate
  • Validate AI scores against actual outcomes monthly
  • Use AI scoring as input, not replacement, for human judgment

Avoid (AI Lead Scoring)

  • Training predictive models on sparse or biased labels
  • Trusting AI scores without regular validation
  • Removing human review for high-value accounts

AI Personalization

Use CaseApproachConsideration
Email personalizationLLM-generated variantsTest against control; maintain brand voice
Dynamic contentReal-time page customizationRequires clean data; test load impact
Video personalizationAI-generated custom videosNovel but unproven ROI at scale

AI Routing & Automation

Use CaseToolsBenefit
Auto-routingChili Piper, Default, Calendly RoutingFaster lead response
Chatbot qualificationDrift, Intercom, Qualified24/7 qualification
Sequence automationOutreach, SalesLoft, ApolloScale outbound

See assets/ai-personalization-playbook.md for detailed implementation guidance.


Collaboration Notes

With Product

  • PLG alignment: Define PQL criteria together (usage thresholds, feature adoption)
  • Feature requests: Leads requesting missing features = Product input
  • Trial optimization: Joint ownership of trial→paid conversion

With Sales

  • SLA document: Co-create lead handoff SLAs with response time commitments
  • Feedback loop: Weekly/bi-weekly meeting on lead quality and rejection reasons
  • Scoring calibration: Review scoring model quarterly with sales input
  • Win/loss analysis: Joint review of closed deals to improve ICP definition

With Engineering

  • Form implementation: Work with engineering on progressive profiling, multi-step forms
  • Analytics tracking: Ensure proper UTM handling, event tracking, conversion attribution
  • Integration maintenance: CRM/MAP sync, webhook reliability, data hygiene
  • Page performance: Landing page load speed directly impacts conversion

International Markets

This skill uses US/UK market defaults. For international lead generation:

NeedSee Skill
Regional buying committee dynamicsmarketing-geo-localization
Regional channel preferencesmarketing-geo-localization
Compliance (GDPR, CASL, LGPD)marketing-geo-localization
Cultural outreach adaptationmarketing-geo-localization

If your query involves international compliance or regional outreach norms, also use marketing-geo-localization for region-specific constraints and adaptations.


Anti-Patterns

Anti-PatternWhy It FailsInstead
MQL volume as success metricHigh volume ≠ pipelineTrack MQL → SQL acceptance rate
Buying lead listsPoor quality, compliance risk, damages domainBuild organic + outbound to verified contacts
Ignoring Sales feedbackMQLs rejected, trust erodesWeekly sync on lead quality
Over-automationGeneric outreach, low reply ratesAutomate mechanics, personalize message
Single-channel dependencyAlgorithm changes kill pipeline2-3 channel minimum
Gating everythingKills SEO, frustrates prospectsGate high-value, ungate awareness
Chasing vanity metricsOpens/clicks without conversionsFocus on reply rate, book rate, SQL
No attribution modelCan't optimize spendStart with simple model, iterate

平台分布

Codex

38.62%
按下载量换算25

Claude

28.85%
按下载量换算18

Cursor

21.15%
按下载量换算14

Gemini CLI

9.16%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills