Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

B2b Demand Gen

ASecurity

Generate B2B pipeline — campaign strategy, multi-channel programs, SDR alignment, and pipeline measurement.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgosqlperformance

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill b2b-demand-gen --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of B2b Demand Gen?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for B2b Demand Gen
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-b2b-demand-gen/badge)](https://www.skillsdirectory.com/skills/aicodedecode-b2b-demand-gen)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: b2b-demand-gen
description: Generate B2B pipeline — campaign strategy, multi-channel programs, SDR alignment, and pipeline measurement.
category: business-marketing
---

## Overview

B2B demand generation creates qualified pipeline for sales: attracting the right accounts, engaging buying committees, and converting interest into sales-ready opportunities. This skill covers demand-gen strategy, program design across channels, SDR/marketing alignment, and the pipeline metrics that prove impact.

Demand gen is measured in pipeline and revenue, not leads. A thousand unqualified leads are worse than useless — they waste sales time.

## When to use

- Building a demand generation engine
- Fixing low-quality lead flow
- Aligning marketing with SDRs/sales
- Planning integrated campaigns
- Choosing demand-gen channels
- Reporting marketing-sourced pipeline

- Launching into a new vertical or segment
- Fixing a pipeline shortfall mid-quarter
- Aligning SDR and marketing on target accounts
- Supporting product-led growth motions
- Planning integrated campaigns with partners
## Core concepts

**The buying committee.** B2B purchases involve 6–10 stakeholders. Demand gen must engage multiple personas (champion, economic buyer, technical evaluator, end user) with role-relevant content — not just one "decision maker."

**Lead vs. demand.** Lead gen optimizes form fills; demand gen optimizes buying intent and pipeline. Ungated content, dark social, and brand building often outperform gated ebooks that generate contact info but no intent.

**The demand funnel.** Engaged account → marketing-qualified → sales-accepted → opportunity → closed-won. Define each stage with sales, agree on SLAs (follow-up speed, feedback loops), and measure conversion between stages.

**Program mix.** Content syndication, webinars, events, paid social/search, email nurture, direct mail/ABM ads, partner co-marketing, SDR outbound sequences. Orchestrate touches across channels to the same accounts — coordinated surround beats scattered tactics.

**Intent data.** Third-party intent (surging topics at target accounts) and first-party intent (site visits, content engagement) prioritize where to focus. Use intent to time outreach, not as a magic list.

**SDR alignment.** Marketing and SDRs are one team: shared targets, shared account lists, agreed qualification criteria, weekly standups, closed-loop feedback (SDRs report lead quality; marketing adjusts). Misalignment here wastes the entire engine.


**Offer ladder.** Match offers to funnel stages: top (educational content, tools, benchmarks) → middle (comparison guides, ROI calculators, webinars) → bottom (demos, trials, assessments).
Weak offers ("subscribe to our newsletter") convert nobody; strong offers solve a real problem even if the buyer never purchases.
Audit your offers annually — the same ebook for three years signals stagnation.
**SDR-marketing SLA.** Marketing commits to MQL volume and quality definitions; SDRs commit to follow-up speed (< 5 min for hot inbound) and attempt counts (8–12 touches across channels).
Review the SLA monthly with shared dashboards. When pipeline misses, the SLA review — not blame — finds the break.
## Practical workflow

1. **Define the ICP and targets.** Firmographics, technographics, trigger events. Build the target account list with sales — demand gen without sales agreement on targets fails.
2. **Map the buyer's journey.** Awareness → consideration → decision content per persona. Identify gaps — most teams lack mid-funnel content for technical evaluators.
3. **Design integrated campaigns.** Quarterly themes, each with: hero asset, channel plan (paid, email, social, SDR, events), account targeting, and sales plays. Coordinate timing so accounts see you everywhere at once.
4. **Launch with SDR integration.** SDRs get account lists, messaging, sequences, and intent signals before launch. Marketing runs air cover; SDRs run ground game. Same message, same week.
5. **Nurture systematically.** Multi-touch nurture streams by persona and stage: educational → proof (case studies) → commercial (demo, trial, pricing). Score engagement and alert SDRs on spikes.
6. **Measure pipeline.** Marketing-sourced pipeline, marketing-influenced pipeline, cost per opportunity, stage conversion rates, sales cycle length, win rate on marketing-sourced deals. Report monthly; optimize quarterly.

**SLA essentials:** SDR follows up on MQLs within X hours; SDR provides disposition feedback within Y days; marketing adjusts scoring/targeting based on feedback monthly; joint pipeline review weekly.


**Campaign planning template:** target account/persona list → offer (content, event, or tool matched to funnel stage) → channels (where this persona actually spends time) → nurture path (what happens after conversion) → sales handoff SLA (speed and quality criteria) → success metrics (MQLs, SQLs, pipeline, revenue — not clicks). Every campaign fills every field before launch.

**Pipeline math check:** quota ÷ win rate ÷ SQL-to-close rate = SQLs needed; SQLs ÷ MQL-to-SQL rate = MQLs needed; MQLs × CPL = budget required. If the budget does not support the math, fix the plan before spending — hope is not a strategy.

**Quarterly campaign planning:** review pipeline gap → allocate budget by funnel stage → select 3–5 big bets (not 20 small ones) → define offers and nurture paths → set sales handoff rules → launch in waves (not all at once) → weekly performance reviews with kill/scale decisions.
Big bets with kill criteria beat scattered activity every time.
## Common pitfalls

- **MQL vanity.** Celebrating lead volume while sales ignores them. Optimize for SALs and pipeline, not MQLs.
- **Gating everything.** Friction that kills reach. Gate late-stage assets; ungate thought leadership.
- **Marketing/SDR misalignment.** Different targets, different lists, no feedback loop. One team, shared goals.
- **Single-channel dependence.** One channel works until it doesn't. Diversify across 3–4 proven channels.
- **Ignoring the dark funnel.** Buyers research without filling forms. Invest in brand, community, and ungated content — measure via influenced pipeline and self-reported attribution.
- **Slow follow-up.** Leads contacted after 24+ hours convert far worse. Speed-to-lead is a top lever.
- **No closed-loop reporting.** Marketing never learns which leads became revenue. Connect CRM data back to campaigns.
- **MQL vanity.** Celebrating lead volume while sales rejects 80%. Align on the SQL definition first; optimize for accepted pipeline, not form fills.
- **No nurture for not-now buyers.** 70%+ of B2B buyers are not ready at first touch. Without nurture, you pay to acquire leads you then waste.
- **Last-touch attribution worship.** Crediting only the final touch starves top-of-funnel investment. Use multi-touch for planning, last-touch only for tactical tweaks.
- **Ignoring sales feedback.** Marketing celebrating MQLs sales rejects. Monthly closed-loop reviews keep definitions honest.
- **Ignoring customer marketing.** All budget on acquisition, none on expansion. Existing customers are the cheapest pipeline — invest proportionally.
- **Channel silos.** Paid, content, and events planned separately. Integrated campaigns outperform siloed tactics — plan jointly.
- **Short-termism.** Killing brand investment for quarterly pipeline. Brand compounds; performance extracts — balance both.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →