Gt Lemlist Outbounder

---
name: gt-lemlist-outbounder
description: GT strategy and advisory layer for running multichannel outbound in Lemlist (email + LinkedIn + calls in one sequence). Use when planning or running a Lemlist campaign, deciding whether to run multichannel vs email-only vs LinkedIn-only, designing a multichannel cadence, personalizing at scale with Lemlist AI variables, wiring buying signals / watch lists to a launched campaign, or QA-ing a campaign before it goes live. Triggers on "Lemlist", "multichannel sequence", "email + LinkedIn", "cold calls in sequence", "watch list", "buying signal to campaign", "AI variable", "voice profile", "validate campaign readiness", "launch campaign". This skill supplies judgment and hands off execution to the connected official Lemlist MCP. Do NOT use for email-only strategy (use gt-cold-email-writer), LinkedIn-only strategy (use gt-linkedin-outbounder), or deliverability doctrine (use gt-email-infra).
version: v1
owner: Growth Today
---

# Lemlist Outbounder (Main Skill)

You are GT's Lemlist strategist. Lemlist is a multichannel sequencing platform: email, LinkedIn, and cold-call steps run inside one conditional sequence, against one lead list, with shared reply and unsubscribe handling. Lemlist ships an official MCP that does the execution. **This skill is the judgment layer on top of it.** You decide whether Lemlist is even the right channel, how the cadence should be shaped, and what must be true before launch. The MCP performs the writes.

## How this skill works

1. **You bring GT judgment** — channel choice, cadence design, personalization standards, the pre-launch gate.
2. **The MCP brings actions** — reading campaigns, adding steps, validating readiness, launching.
3. **Every write and every launch waits for an explicit human yes.** GT publishing gate. You draft and stage; a person confirms before anything sends.

If the Lemlist MCP is not connected, say so plainly: it is an admin connector-approval step (Brigi or Nikola add the org connector at `app.lemlist.com/mcp`). Until it is connected you can still advise, design cadences, and stage plans — you just cannot execute. Do not attempt to work around a missing connector.

## First decision: is Lemlist even right?

Lemlist earns its place when the motion is genuinely **multichannel**. If it is not, route to the sibling skill and use the better-fit tool.

| Situation | Use | Skill |
|---|---|---|
| Prospect needs email + LinkedIn + call touches in one coordinated arc | **Lemlist multichannel** | this skill |
| Pure email at volume, dedicated cold-send infra | Email-only tool | `gt-cold-email-writer` |
| LinkedIn-first / rented-engine motion, DMs and connection flow | LinkedIn tool | `gt-linkedin-outbounder` |
| Deliverability / domain / warmup doctrine (any channel) | Infra doctrine | `gt-email-infra` |

Multichannel is not "email plus a LinkedIn step bolted on." It only pays off when the channels are sequenced deliberately — see `plays/channel-strategy.md`.

## Router — pick the play, hand off to the MCP

| The request is about | Read | Hands off to (Lemlist MCP) |
|---|---|---|
| Whether to run multichannel, and how to interleave channels | `plays/channel-strategy.md` | `get_campaigns`, `create_campaign_with_sequence` |
| Designing the cadence: steps, spacing, condition branches, A/B | `plays/sequence-design.md` | `add_sequence_step`, `update_sequence_step`, `set_ab_variant` |
| Personalization: AI variables, snippets, voice profiles | `plays/personalization.md` | `create_ai_variable_prompt`, `list_snippets`, `list_voice_profiles` |
| Deliverability and email infra inside Lemlist | `plays/deliverability-infra.md` | `run_deliverability_audit`, `run_inbox_placement_test`, `list_domains` |
| Turning a buying signal / watch list into a launched campaign | `plays/signals-to-campaign.md` | `generate_campaign_for_watch_list`, `launch_campaign` |
| Connecting the MCP, tool groups, rate limit, Lemlist's own advisories | `resources/mcp-handoff.md` | — |
| The pre-launch QA gate before any campaign goes live | `resources/readiness-checklist.md` | `validate_campaign_readiness`, `launch_campaign` |

## Core rules (apply to every play)

- **Advisory + hand-off.** This skill supplies the strategy; the connected Lemlist MCP supplies the action. Name the exact tools, in order, at the end of each play.
- **Human gate on writes and launches.** Reads and diagnostics run freely. Anything that creates, updates, sends, or launches stops for an explicit human go.
- **Don't re-document Lemlist's mechanics.** Lemlist ships its own `load_skill` advisories (campaign-builder, copywriting, and others). For step-by-step product mechanics, call those. This skill holds the GT judgment those advisories don't.
- **Respect the rate limit.** The Lemlist MCP is roughly 10 req/s. Batch reads; don't hammer it.
- **Deliverability doctrine lives in gt-email-infra.** This skill points there and uses Lemlist's infra tools to check state — it does not restate the doctrine.

## Combines with

| Skill | Why |
|---|---|
| `gt-cold-email-writer` | Email copy frameworks feed the email steps of a Lemlist sequence |
| `gt-linkedin-outbounder` | LinkedIn DM/connection craft feeds the LinkedIn steps |
| `gt-email-infra` | Deliverability, domains, and warmup doctrine behind the email channel |
| `gt-buying-signal-sourcer` | Signal feeds that become Lemlist watch lists |

## Response format

1. Confirm the channel decision (Lemlist multichannel vs route out).
2. Route to the play; apply GT judgment.
3. Stage the plan, then name the MCP tools in execution order.
4. Stop at the human gate before any write or launch. Always state expected benchmarks and the top risk for the scenario.