sales-lemlist
Lemlist platform help — multichannel sequences, lead database, enrichment, Lemwarm, unified inbox, AI personalization, LinkedIn automation, calls, WhatsApp, API, integrations. Use when Lemlist sequences not sending, emails landing in spam despite Lemwarm, leads not importing correctly, integrations not syncing, People Database search returning poor matches, or Lemlist API calls failing. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts outside Lemlist (use /sales-enrich).
What this skill does
# Lemlist Platform Help
Help the user with Lemlist platform questions — from multichannel sequence setup and Lemwarm through lead management, enrichment, AI personalization, LinkedIn automation, unified inbox, API, and integrations.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What area of Lemlist do you need help with?**
- A) Sequences — creating, managing, or optimizing multichannel sequences (for strategy, hand off: `/sales-cadence {your question}`)
- B) Lead database — finding prospects with People Database, filters, intent signals
- C) Enrichment — waterfall enrichment for emails and phone numbers
- D) Lemwarm — warmup, deliverability score, sender reputation
- E) Unified inbox — managing replies across channels
- F) LinkedIn — automated LinkedIn steps, connection requests, messages
- G) Calls — in-app dialer, call steps in sequences
- H) WhatsApp — WhatsApp messaging steps (add-on)
- I) AI personalization — dynamic variables, AI-generated content
- J) Integrations — HubSpot, Salesforce, Pipedrive, Zapier, Make
- K) API & Webhooks — automation, lead import, campaign management
- L) Admin — billing, plan features, team settings
- M) Something else — describe it
2. **What's your role?**
- A) Sales rep / AE / BDR
- B) Sales manager / team lead
- C) RevOps / Sales Ops
- D) Agency owner / account manager
- E) Admin / IT
- F) Founder / solo seller
- G) Other
3. **What are you trying to accomplish?** (describe your specific goal or question)
**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.
## Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
- List building / prospecting → `/sales-prospect-list`
- Contact enrichment outside Lemlist → `/sales-enrich`
- Cadence strategy / sequence design → `/sales-cadence`
- Cross-platform deliverability → `/sales-deliverability`
- Tool integration architecture → `/sales-integration`
Otherwise, answer directly from platform knowledge using the reference below.
## Step 3 — Lemlist platform reference
Provide module-by-module guidance based on the user's area:
### Sequences (Multichannel Campaigns)
- **What it is**: A sequence in Lemlist is a multichannel outreach campaign — email steps, LinkedIn actions, phone calls, and WhatsApp messages on an automated schedule
- **Key concepts**: Sequence = multichannel campaign, steps = touchpoints across channels, leads = enrolled contacts
- **Channels available**: Email, LinkedIn (connection requests, profile visits, messages), phone (in-app dialer), WhatsApp (paid add-on at $20/seat/month)
- **A/B testing**: Test subject lines, email body content, and entire step variants
- **Lead statuses**: interested, not interested, contacted, not contacted
- **Best practices**: Keep initial emails under 125 words, mix channels (don't do 3+ email steps in a row), use AI personalization for Level 3+ at scale
### Lead Database (People Database)
- **What it is**: Built-in B2B lead database with 600M+ contacts and smart filtering
- **Key features**: Search by title, seniority, industry, company size, location, tech stack
- **Intent signals**: Identifies prospects actively researching relevant topics (newer feature)
- **Credit model**: Pay per lead revealed — credits deducted on export/use
- **Pre-verification**: Leads from People Database are verified before delivery
- **Best practices**: Use filters to narrow before revealing — don't burn credits on broad searches
### Enrichment
- **What it is**: Built-in waterfall enrichment — find verified emails and phone numbers for your leads
- **How it works**: Lemlist tries multiple data providers in sequence (waterfall) to maximize match rates
- **Email finder**: Find professional email addresses from name + company
- **Phone finder**: Find direct/mobile phone numbers
- **Verification**: Emails are verified before delivery to reduce bounce rates
- **Best practices**: Enrich leads before adding to sequences — don't send to unverified addresses
### Lemwarm (Deliverability)
- **What it is**: Built-in email warmup tool included with every Lemlist seat at no extra cost
- **How it works**: Sends automated warmup emails to a premium network of 10,000+ real users, generating real opens and replies to build sender reputation
- **Deliverability score**: Score out of 100 showing inbox placement quality (target 90+)
- **Warmup settings**: Configure emails/day (recommended 30/day for accounts <6 months, 40/day for older) and ramp-up increment
- **Warmup timeline**: Minimum 3-5 weeks before adding cold outbound
- **Inbox rotation**: Distribute sends across multiple email accounts connected to a sequence
- **Best practices**: Enable Lemwarm on every connected email account immediately. Keep warmup running even during active campaigns — it maintains reputation.
### Unified Inbox
- **What it is**: Single view for all replies across email, LinkedIn, and other channels
- **Key features**: Reply tracking, conversation threads, label conversations, draft responses
- **Channel aggregation**: See email replies, LinkedIn messages, and WhatsApp responses in one place
- **Best practices**: Check unified inbox daily, respond within 1 hour for best conversion
### LinkedIn Automation
- **What it is**: Automated LinkedIn steps within sequences — profile visits, connection requests, and messages
- **Step types**: Visit profile, send connection request (with note, under 300 chars), send message (to existing connections)
- **Limits**: LinkedIn has daily action limits — Lemlist respects these but monitor your LinkedIn account for warnings
- **Plan requirement**: Multichannel Expert plan ($99/user/month) required for LinkedIn steps
- **Best practices**: Always visit profile before sending connection request. Keep connection request notes casual and non-salesy. Don't exceed 20-30 connection requests/day.
### Calls (In-App Dialer)
- **What it is**: Built-in calling within Lemlist sequences — add phone steps alongside email and LinkedIn
- **Key features**: Click-to-call from lead record, call logging within sequence activity
- **Plan requirement**: Multichannel Expert plan required
- **Best practices**: Place call steps within 24 hours of an email step — reference the email in your opener
### WhatsApp
- **What it is**: WhatsApp messaging steps within sequences (paid add-on at $20/seat/month)
- **How it works**: Add WhatsApp steps to multichannel sequences alongside email, LinkedIn, and calls
- **Requirement**: WhatsApp Business account + Lemlist WhatsApp add-on
- **Best practices**: Use WhatsApp for warm follow-ups after email/LinkedIn engagement, not cold first-touch
### AI Personalization
- **What it is**: AI-powered content generation that pulls data from LinkedIn profiles, company websites, and other sources to create personalized outreach at scale
- **How it works**: Configure AI variables that research each lead and generate custom snippets (icebreakers, pain points, company references)
- **Dynamic variables**: Standard merge fields ({{firstName}}, {{companyName}}) plus AI-generated custom variables
- **Best for**: Level 3-4 personalization at scale (100+ prospects) — finding specific talking points per lead
- **Not for**: Simple {{firstName}} personalization — just use standard variables for that
### Lemlist data model
Core entities — understand these to navigate the UI and work with the API:
| Entity | What it represents | Key relationships |
|---|---|---|
| **Campaign/Sequence** | A multichannel outreach sRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".