lemlist-campaign-from-icp

Convert a natural-language ICP into a paused lemlist campaign via the lemlist MCP.

277|88|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill lemlist-campaign-from-icp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lemlist-campaign-from-icp
Source: https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist-campaign-from-icp
Command: npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill lemlist-campaign-from-icp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nodejs>=20, LEMLIST_API_KEY, claude code, lemlist mcp (npx mcp-remote).

What problem does it solve?

It eliminates the time-consuming process of turning a natural-language ICP into a ready-to-review lemlist campaign by orchestrating strategy, lead sourcing, enrichment planning, copywriting, and QA into a single guided workflow.

Core Features & Use Cases

  • ICP to campaign orchestration: Chains 24 lemlist atomic skills (ICP, personas, pains, value props, offers, competitors, triggers, sourcing filters, and copywriting) into one end-to-end loop.
  • Leads sourced from the lemlist People Database: Uses the lemlist MCP to discover the live filter registry and run searches with production-ready constraints and deduplication.
  • Seniority-routed, quality-gated sequences: Builds separate sequences for VP+/Manager/IC, refines and scores the copy against a benchmark, and runs a final critique before any push.
  • Hard safety guardrails: Runs a dryrun to a local JSON file, requires the user to type exactly approve, and keeps the resulting campaign in DRAFT (never auto-starts).

Quick Start

In Claude Code, run the skill and tell it: create a lemlist campaign from this ICP, then type approve after the dryrun summarizes the exact lead count and campaign draft details.

Frequently Asked Questions about lemlist-campaign-from-icp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a natural-language ICP into a lemlist campaign?

To turn a natural-language ICP into a lemlist campaign, this skill orchestrates 24 atomic lemlist skills to source leads, route sequences by seniority, and generate benchmark-scored email copy. It outputs a paused, ready-to-review DRAFT campaign.

Do I need a lemlist API key to source leads through the MCP integration?

Yes, you need a lemlist API key to source leads through the MCP integration. The skill uses the lemlist MCP to discover the live filter registry, run production-ready People Database searches, and apply lead deduplication before generating your campaign.

Can I generate seniority-routed email sequences from an ICP in Claude Code?

You can generate seniority-routed email sequences from an ICP directly in Claude Code. The workflow builds separate 3-email sequences for VP+, Manager, and IC personas, refines the copy, and runs a final QA critique before creating the campaign.

What is the approval process before launching an automated lemlist campaign?

The approval process requires the skill to run a dryrun that saves a JSON artifact summarizing exact lead counts and campaign details. You must explicitly type "approve" to pass the approval gate, after which the campaign is created in DRAFT mode and never auto-starts.

Does the lemlist campaign orchestration skill automatically enrich sourced leads?

The lemlist campaign orchestration skill applies safety constraints on enrichment posture and does not automatically enrich sourced leads. It focuses on lead sourcing, deduplication, and sequence routing while keeping enrichment planning gated by your explicit approval.

What are the limitations of using dryrun-first JSON artifacts for campaign orchestration?

A limitation of using dryrun-first JSON artifacts is that campaign creation is strictly gated and cannot bypass the DRAFT-only state. The workflow halts if you do not type exactly "approve", preventing automated pushes and requiring manual review of the lead count and copy.