Lemlist setup skill
Sets up and optimizes Lemlist: personalized images and videos, multi-channel sequences, warmup, and deliverability settings.
by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗
npx degit LeadMagic/gtm-skills/skills/tools/lemlist-setup#main ~/.claude/skills/lemlist-setupChecked ·commit main
Inside this skill
SKILL.md · the author's own words# Lemlist Setup ## Overview Lemlist differentiates on personalization — custom images, videos, and landing page personalization that other platforms don't offer natively. Combined with lemwarm (automated warmup) and multi-channel capabilities, it's ideal for teams that want higher per-email engagement at lower volume. ## Authoritative Foundations - **lemlist Help Center** — Build multichannel sequences (email, LinkedIn, calls) with conditions, and use lemwarm and custom tracking doma… - **Guillaume Moubeche — lemlist outbound** — Multichannel sequences — email, LinkedIn, calls in one enrollment; personalization should ear… - **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and hon… ## When to Use - "Set up Lemlist" - "Lemlist campaign setup"
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Lemlist setup
Show the full text150 lines
Lemlist Setup
Overview
Lemlist differentiates on personalization — custom images, videos, and landing page personalization that other platforms don't offer natively. Combined with lemwarm (automated warmup) and multi-channel capabilities, it's ideal for teams that want higher per-email engagement at lower volume.
Authoritative Foundations
- lemlist Help Center — Build multichannel sequences (email, LinkedIn, calls) with conditions, and use lemwarm and custom tracking domains before sending.
- Guillaume Moubeche — lemlist outbound — Multichannel sequences — email, LinkedIn, calls in one enrollment; personalization should earn the reply, not decorate the email.
- Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and honor unsubscribes quickly.
When to Use
- "Set up Lemlist"
- "Lemlist campaign setup"
- "Personalized cold email at scale"
- "Lemlist warmup strategy"
Step-by-Step Process
Phase 1: Lemwarm Setup
Before sending any campaign:
- Add all sending mailboxes to lemwarm
- Start with 2-5 warmup emails/day, auto-escalate over 3-4 weeks
- Monitor reputation score: target >95 before launching real campaigns
- Lemwarm sends auto-replies from warmup pool to build positive reputation
Phase 2: Campaign Architecture
- Sequence: 3-7 steps, email + LinkedIn + custom tasks
- Personalization: Custom images (prospect name/logo on image), custom videos (screencast with prospect website), custom landing pages (dynamic text/image)
- Conditions: If opened → different next step. If clicked → different follow-up. If no engagement → different angle.
- Sending: Max 100 emails/day/domain across all campaigns
Phase 3: Creative Personalization
- Custom images: Prospect name on a whiteboard, their logo in your UI, "Hi {first_name}" graphic
- Custom videos: Loom-style screencast showing their website + your product integration
- Custom landing pages: Dynamic hero image with their company logo, dynamic headline with their name, dynamic case study from their industry
Phase 4: Multi-Channel
Layer LinkedIn into sequences:
- Email Touch 1 → LinkedIn profile view 2 days later
- Email Touch 2 → LinkedIn connection request 2 days later
- Email Touch 3 → LinkedIn DM 2 days later
- All tracked in Lemlist timeline
Phase 5: Analytics
- Campaign health: reply rate, interest rate, meeting rate
- Creative performance: which images/videos drive highest engagement
- A/B test: personalization vs plain text, creative vs standard
- Warmup health: per-mailbox reputation score, spam placement rate
Output Format
Lemlist playbook with: warmup schedule, campaign configuration, creative personalization templates, multi-channel integration plan, and optimization framework.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Execution Artifacts
references/framework-notes.md— Guillaume multichannel, Pat Full-Circle, lemwarm gatestemplates/output-template.md— lemwarm + multichannel + Clay gate deliverablescripts/check-output.py— local checklist validator This skill includes lightweight artifacts the agent can load on demand:references/clay-enrollment-handoff.md— Clay → Lemlist variables + problem_hook mappingreferences/lemlist-guillaume-outbound.md— Guillaume Moubeche canonical playbookreferences/pat-spielmann-outbound-copy.md— verify + multichannel (Pat Spielmann)- the
clay-loops-toolkitskill (routing-matrix.md) — signal → campaign map references/gtm-experts-outbound-index.md— expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- Lemlist Personalization Framework: apply only the part that directly improves the requested deliverable.
- ColdIQ Multi-Channel: apply only the part that directly improves the requested deliverable.
- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Related Skills
- cold-email-strategy, cold-email-copywriting, email-deliverability, inbox-setup, social-selling
| 1 | |
| 2 | name lemlist-setup |
| 3 | description >- |
| 4 | Sets up and optimizes Lemlist: personalized images and videos, multi-channel |
| 5 | sequences, warmup, and deliverability settings. Use when the user is building |
| 6 | Lemlist campaigns or running personalized cold email at scale in Lemlist. |
| 7 | Triggers on: "Lemlist", "Lemlist setup", "Lemlist campaigns", "personalized |
| 8 | cold email". |
| 9 | license MIT |
| 10 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 11 | metadata |
| 12 | version "1.0.0" |
| 13 | author LeadMagic |
| 14 | category tools |
| 15 | tags [lemlist, cold-email, personalization, lemwarm, multi-channel] |
| 16 | frameworks |
| 17 | - "lemlist Help Center" |
| 18 | - "Guillaume Moubeche — lemlist outbound" |
| 19 | - "Google and Yahoo — Bulk sender requirements (2024)" |
| 20 | |
| 21 | |
| 22 | # Lemlist Setup |
| 23 | |
| 24 | ## Overview |
| 25 | Lemlist differentiates on personalization — custom images, videos, and landing |
| 26 | page personalization that other platforms don't offer natively. Combined with |
| 27 | lemwarm (automated warmup) and multi-channel capabilities, it's ideal for teams |
| 28 | that want higher per-email engagement at lower volume. |
| 29 | |
| 30 | ## Authoritative Foundations |
| 31 | **lemlist Help Center** — Build multichannel sequences (email, LinkedIn, calls) with conditions, and use lemwarm and custom tracking domains before sending. |
| 32 | **Guillaume Moubeche — lemlist outbound** — Multichannel sequences — email, LinkedIn, calls in one enrollment; personalization should earn the reply, not decorate the email. |
| 33 | **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and honor unsubscribes quickly. |
| 34 | |
| 35 | ## When to Use |
| 36 | "Set up Lemlist" |
| 37 | "Lemlist campaign setup" |
| 38 | "Personalized cold email at scale" |
| 39 | "Lemlist warmup strategy" |
| 40 | |
| 41 | ## Step-by-Step Process |
| 42 | |
| 43 | ### Phase 1: Lemwarm Setup |
| 44 | Before sending any campaign: |
| 45 | Add all sending mailboxes to lemwarm |
| 46 | Start with 2-5 warmup emails/day, auto-escalate over 3-4 weeks |
| 47 | Monitor reputation score: target >95 before launching real campaigns |
| 48 | Lemwarm sends auto-replies from warmup pool to build positive reputation |
| 49 | |
| 50 | ### Phase 2: Campaign Architecture |
| 51 | **Sequence:** 3-7 steps, email + LinkedIn + custom tasks |
| 52 | **Personalization:** Custom images (prospect name/logo on image), custom videos |
| 53 | (screencast with prospect website), custom landing pages (dynamic text/image) |
| 54 | **Conditions:** If opened → different next step. If clicked → different follow-up. |
| 55 | If no engagement → different angle. |
| 56 | **Sending:** Max 100 emails/day/domain across all campaigns |
| 57 | |
| 58 | ### Phase 3: Creative Personalization |
| 59 | **Custom images:** Prospect name on a whiteboard, their logo in your UI, "Hi {first_name}" graphic |
| 60 | **Custom videos:** Loom-style screencast showing their website + your product integration |
| 61 | **Custom landing pages:** Dynamic hero image with their company logo, dynamic headline |
| 62 | with their name, dynamic case study from their industry |
| 63 | |
| 64 | ### Phase 4: Multi-Channel |
| 65 | Layer LinkedIn into sequences: |
| 66 | Email Touch 1 → LinkedIn profile view 2 days later |
| 67 | Email Touch 2 → LinkedIn connection request 2 days later |
| 68 | Email Touch 3 → LinkedIn DM 2 days later |
| 69 | All tracked in Lemlist timeline |
| 70 | |
| 71 | ### Phase 5: Analytics |
| 72 | Campaign health: reply rate, interest rate, meeting rate |
| 73 | Creative performance: which images/videos drive highest engagement |
| 74 | A/B test: personalization vs plain text, creative vs standard |
| 75 | Warmup health: per-mailbox reputation score, spam placement rate |
| 76 | |
| 77 | ## Output Format |
| 78 | Lemlist playbook with: warmup schedule, campaign configuration, creative personalization |
| 79 | templates, multi-channel integration plan, and optimization framework. |
| 80 | |
| 81 | |
| 82 | |
| 83 | ## Quality Check |
| 84 | |
| 85 | Before delivering, verify: |
| 86 | [ ] All required sections are complete |
| 87 | [ ] Output matches the user's stated need |
| 88 | [ ] Named frameworks are cited for key recommendations |
| 89 | [ ] No vague claims — every recommendation has a specific action |
| 90 | [ ] Deliverable is ready for operational use, not just conceptual |
| 91 | |
| 92 | ## Common Pitfalls |
| 93 | |
| 94 | **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables. |
| 95 | **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner. |
| 96 | **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority. |
| 97 | |
| 98 | ## Execution Artifacts |
| 99 | |
| 100 | `references/framework-notes.md` — Guillaume multichannel, Pat Full-Circle, lemwarm gates |
| 101 | `templates/output-template.md` — lemwarm + multichannel + Clay gate deliverable |
| 102 | `scripts/check-output.py` — local checklist validator |
| 103 | This skill includes lightweight artifacts the agent can load on demand: |
| 104 | `references/clay-enrollment-handoff.md` — Clay → Lemlist variables + problem_hook mapping |
| 105 | `references/lemlist-guillaume-outbound.md` — Guillaume Moubeche canonical playbook |
| 106 | `references/pat-spielmann-outbound-copy.md` — verify + multichannel (Pat Spielmann) |
| 107 | the `clay-loops-toolkit` skill (routing-matrix.md) — signal → campaign map |
| 108 | `references/gtm-experts-outbound-index.md` — expert router |
| 109 | Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice. |
| 110 | |
| 111 | ## Implementation Depth |
| 112 | |
| 113 | Use this section when the user asks for a finished asset, not a high-level explanation. |
| 114 | |
| 115 | ### Diagnostic Questions |
| 116 | |
| 117 | What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led? |
| 118 | Which ICP tier is the output for: small business, mid-market, enterprise, or mixed? |
| 119 | What proof is available today: customer stories, usage data, third-party validation, screenshots, or none? |
| 120 | What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow? |
| 121 | What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure? |
| 122 | |
| 123 | ### Framework Application |
| 124 | |
| 125 | Map the recommendation explicitly to the named frameworks in this skill: |
| 126 | |
| 127 | Lemlist Personalization Framework: apply only the part that directly improves the requested deliverable. |
| 128 | ColdIQ Multi-Channel: apply only the part that directly improves the requested deliverable. |
| 129 | Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable. |
| 130 | |
| 131 | ### Deliverable Standard |
| 132 | |
| 133 | A strong output from this skill includes: |
| 134 | |
| 135 | A crisp diagnosis of the current situation |
| 136 | A recommended path with tradeoffs, not a generic list |
| 137 | A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan |
| 138 | A measurement plan with leading and lagging indicators |
| 139 | Risks and edge cases called out before execution |
| 140 | |
| 141 | ### Adaptation Rules |
| 142 | |
| 143 | For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity. |
| 144 | For mid-market: include workflow ownership, handoffs, integrations, and enablement assets. |
| 145 | For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements. |
| 146 | |
| 147 | |
| 148 | ## Related Skills |
| 149 | cold-email-strategy, cold-email-copywriting, email-deliverability, inbox-setup, social-selling |
| 150 |
Discussion
Alternatives
Browse more free Claude skills or everything in Marketing.