Built as a no-fluff execution skill for revenue-aligned demand generation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmarketing-leads-generationExecute the skills CLI command in your project's root directory to begin installation:
Fetches marketing-leads-generation from vasilyu1983/ai-agents-public and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate marketing-leads-generation. Access via /marketing-leads-generation in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
5
total installs
5
this week
53
GitHub stars
0
upvotes
Run in your terminal
5
installs
5
this week
53
stars
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.
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.
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 |
Set targets from your own baseline, then improve stage-by-stage:
| 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 |
For full funnel setup including MQL/SQL criteria and SLAs, use lead-funnel-definition.md.
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 |
| 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 |
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 |
ABS is often effective in B2B when targeting high-value accounts with complex buying committees.
| 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 |
| 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 |
Use related skills instead for:
| 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 |
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
Goal: Sustain deliverability and protect brand trust while running outbound and nurture.
Spam Rate Thresholds (Critical — 2025 Enforcement)
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
dengineproblem/agents-monorepo
claude-office-skills/skills
Keeps context tight: marketing-leads-generation is the kind of skill you can hand to a new teammate without a long onboarding doc.
marketing-leads-generation reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added marketing-leads-generation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for marketing-leads-generation matched our evaluation — installs cleanly and behaves as described in the markdown.
marketing-leads-generation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: marketing-leads-generation is focused, and the summary matches what you get after install.
marketing-leads-generation has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend marketing-leads-generation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in marketing-leads-generation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
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