Updated September 28, 2026 | 11 min read

I Tested the Copywriting Manager Sequence Skill: 3 Emails That Get Sales Managers to Reply (Free Claude Code Skill)

Most cold emails to managers read like they were written for a VP. Big revenue claims. Strategic vision. Board-level language. And managers ignore every word, because that’s not their world. Their world is broken processes, underperforming reps, and tools that don’t talk to each other.
I kept seeing this pattern across campaigns we analyzed internally at lemlist. So when we built the copywriting manager sequence skill for Claude Code, the goal was specific: generate a 3-email arc that speaks to manager-level friction, with copy rules strict enough to prevent the usual AI slop.
In this post, I’ll walk you through exactly what this skill does, how to install it, how to customize it per role, and how to launch the output inside a real multichannel campaign. I’ll also cover where it fits compared to writing these sequences by hand or prompting ChatGPT.

What the copywriting manager sequence skill does

The copywriting manager sequence is a Claude Code skill built to write three cold emails aimed at manager-level buyers: Sales Managers, RevOps Managers, Marketing Managers, and Team Leads. At its simplest, a skill is a directory that contains a SKILL.md file. (Equipping agents for the real world with Agent Skills \ Anthropic) Once it’s in your local skills directory, Claude applies it automatically whenever you ask for manager-focused email copy.
The output includes a two-word lowercase subject line for each email, a body between 50 and 100 words, personalization placeholders, and sequence notes explaining the reasoning behind each message. You get a finished, ready-to-send sequence.
The skill writes specifically for manager-level roles rather than adapting generic outbound copy. It produces a 3-email arc where each email has a distinct job (friction, root cause, consequence), with subject lines, body copy, and placeholders ready to fill in. Length limits, tone constraints, and formatting rules keep the output from reading like filler. And variable fields for prospect name, company, role, and pain point let you personalize with real data.
This skill requires no API keys and makes no external network calls. It’s instructions-only, meaning it lives as a plain-text markdown file in your local skills directory with no shell access or third-party connections. We built it at lempire and open-sourced it in the l3mpire/claude-skills repo, so you can inspect every line before installing.

Why manager-level buyers need a different email sequence

Managers sit in an odd spot in the org chart. They translate VP strategy into daily execution for reps and ICs. They feel every broken process firsthand, which means the copy that lands with a VP usually falls flat with them.
Here’s how the angle shifts by seniority:
VP / Director
Manager / Team Lead
Individual Contributor
Primary concern
Revenue targets, board-level metrics
Team output, process gaps, tool adoption
Personal quota, daily workflow
Buying trigger
Strategic initiative or budget cycle
Operational bottleneck or team complaint
Personal pain with current tool
Email angle that works
ROI and competitive positioning
Workflow friction and team efficiency
Feature-specific and fast
You might read this and think the differences sound minor. They’re not. A sales manager who gets an email about “driving 30% revenue growth” will file it under “that’s my VP’s problem.” An email that names the exact friction their reps hit during pipeline review, though? That gets read.
The skill targets pain points that show up at the team level, week after week:
  • Reps losing hours to manual tasks instead of selling
  • Inconsistent outreach quality across the team, with no shared playbook
  • Too many disconnected tools, each creating its own data silo
  • Reporting gaps that make it hard to show results upward

The 3-email sequence structure for manager personas

Before you run the skill, gather four inputs: the persona’s exact title, company size or stage, a known pain point (even a hypothesis works), and a reference company in the same vertical. Having these ready means Claude can produce a personalized sequence on the first pass, no back-and-forth needed.
The skill follows a fixed arc. Email 1 names the friction. Email 2 explains what’s causing it. Email 3 shifts to consequence and closes the loop. Each one gets shorter as the sequence moves forward.
Email 1 does one job: recognition. It names something specific that happens in the manager’s world every week, with no product mention and no pitch. The goal is a reaction closer to “how do they know that” than “here’s another vendor.”
Email 2 goes one layer deeper and explains why the problem keeps happening, usually by pointing at a process issue rather than a people issue. This email also carries a P.S. with a behavioral reference (“Teams like those at [Company] often find…”) instead of a fabricated stat or case study.
Email 3 reframes the friction around what it means for the manager’s credibility with their own VP, then closes with a clear yes-or-no question. The skill always ends this one with a specific line: “won’t message again, hope I didn’t do something wrong!” In my experience, breakup emails like this get read because they signal respect for the person’s time.

Copywriting rules the skill follows

The skill functions less like a prompt and more like a style guide with teeth. It enforces constraints that catch the most common problems in AI-written outbound copy, whether or not you’re the one running the skill.
Subject lines are exactly two words, lowercase, no clickbait. Body copy runs 50 to 100 words, not counting variables or the P.S. Everything is plain text only, no HTML, no bullet lists inside the email itself. The tone is peer-to-peer with no exclamation marks, no “I,” and no superlatives like “best” or “leading.”
Personalization fields cover company name, prospect name, title, pain point, and a reference company where relevant. Without personalization data on hand, the skill adapts and writes without it rather than dropping in a placeholder that reads as hollow.
The skill also blocks a specific list of habits: fabricated metrics, generic value props, feature lists disconnected from a real pain point, links or attachments in early emails, and filler phrases like “just following up.”
Quote Icon
Tip: Borrow the accuracy rule even if you’re writing by hand. A line like “Teams like those at [Company] often find…” reads as credible without committing you to proof you can’t produce on demand.

Other ways to write manager sequences (and where this skill fits)

Fair to ask: do you need a Claude Code skill for this? You have options.
Writing by hand. If you’ve written hundreds of cold emails and already have a working framework for manager messaging, you can absolutely do this manually. The tradeoff is time. Building a 3-email sequence with proper constraints takes 30–60 minutes per persona, longer if you’re iterating across four or five titles.
Generic ChatGPT or Claude prompt. You can paste a detailed prompt into any LLM and get decent output. The problem is consistency. Without a saved skill file, you’re re-prompting the constraints every time, and the model drifts. Copy gets longer, tone shifts, rules get dropped.
Other skill marketplaces. Repositories like anthropics/skills host skills for document and enterprise workflows. Community repos on GitHub (like awesome-claude-skills collections) aggregate hundreds of skills across categories. If you’re already using a different AI coding tool (Cursor, Codex, Gemini CLI), some skills are portable across agents since they follow the open Agent Skills standard.
The copywriting manager sequence skill sits between “fully manual” and “fully generic AI.” It locks in the rules once, produces consistent output for every persona you feed it, and the file is editable when you need to change the framework. That’s the gap it fills.

How to install and use the skill in Claude Code

Setup takes a couple of minutes. Follow these steps:
  1. Open your terminal and run the install command:
    npx skills add l3mpire/claude-skills/copywriting-manager-sequence
    The .md file lands in your local skills directory (the folder Claude Code checks for reusable prompts).
  2. Restart Claude Code (or start a new session). Claude will discover the skill automatically based on its description field. (GitHub - l3mpire/claude-skills · GitHub)
  3. Ask Claude for a sequence directly. For example: “Write a 3-email sequence for a RevOps Manager at a 200-person SaaS company.” You pass in the persona details and the skill handles the rest.
  4. Or let Claude invoke it on its own when it recognizes a matching request. Either way works.
Is this safe to run? Yes. The skill is instructions-only. It requires no API keys, makes no shell calls, and connects to no third-party hosts. It’s a plain-text markdown file that lives locally on your machine. You can read the full source in the l3mpire/claude-skills repo on GitHub before installing.

Customizing sequences for sales managers, RevOps managers, and team leads

The skill writes manager-level copy by default, but the output improves once you point it at a specific title. It accepts role-specific inputs and shifts the angle accordingly.
For sales managers, the pain points center on pipeline velocity, rep coaching, forecast accuracy, and quota attainment with existing headcount. RevOps and operations managers deal with tool sprawl and process consistency across the GTM stack. Marketing managers care about campaign execution and MQL-to-SQL conversion rates. Customer success managers focus on renewals, escalations, churn detection, and expansion revenue.
The vocabulary changes with the role. RevOps copy leans on infrastructure language; sales manager copy leans on team performance. Specifying the title upfront saves a round of edits later.

Launching your manager sequence in a multichannel campaign

Copy on its own doesn’t book meetings. It has to reach the right inbox, alongside the right channels, at the right pace.
  1. Import your manager-level lead list. Pull from your CRM, upload a CSV, or build a list with role and seniority filters (lemlist’s database covers 600M+ contacts across 65M+ companies for this).
  2. Enrich contacts with verified data. Confirmed emails and phone numbers protect your sender reputation from bouncing off dead addresses.
  3. Load the sequence and add LinkedIn or call steps. Paste in the skill’s output, then layer in connection requests or call tasks between emails to keep timing tight.
  4. Activate and monitor replies. Track opens, replies, and bounces from one inbox, especially useful when multiple reps run the same sequence across different territories.
Start a 14-day free trial to load your manager sequences into multichannel campaigns with built-in deliverability tools and lead enrichment.

Common mistakes when writing outbound sequences for managers

A few habits tend to flatten reply rates, even when the copy itself is solid.
Writing to the VP instead of the manager is the most common one. Strategic language about revenue lands better with a VP than with someone focused on team execution. The skill catches this, but if you’re editing the output, watch for scope creep.
Pitching in the first email kills the arc. Leading with features before showing you understand the problem turns recognition into a sales pitch.
Making every email the same length defeats the structure. Each one in the sequence carries a different job and should get shorter as it goes.
Skipping personalization fields, sending raw skill output without filling in prospect details, reads as generic to anyone who receives it.
Relying on email alone is a missed opportunity. Managers, especially in tech, often respond faster on LinkedIn. Layer in other channels.

FAQs about the copywriting manager sequence skill

How many emails does the copywriting manager sequence skill generate?
Three. Email 1 names the friction, Email 2 diagnoses the cause, and Email 3 shifts to consequence and closes the loop, with sequence notes explaining the logic behind each message.
Can the skill output be used outside of Claude Code?
Yes. The output is plain text with standard formatting, so it drops into any outbound platform, CRM, or email tool without modification.
What’s the difference between the manager sequence skill and a VP sequence skill?
The manager skill focuses on operational pain and team-level friction, while a VP skill leans on strategic outcomes and business metrics. Tone and CTA style shift to match how each persona evaluates a new tool. The l3mpire/claude-skills repo includes other persona-specific skills worth exploring if you’re running sequences at multiple seniority levels.
Can the skill be edited to match a specific brand voice?
Yes. The skill file is a plain-text markdown document, so tone, length, pain-point language, and CTA framing can all be edited directly in the file, and changes stay in your local skills directory.
Is the copywriting manager sequence skill safe to install?
Yes. The skill requires no API keys, no shell access, and makes no network calls. It’s a local, instructions-only markdown file. You can audit the source in the l3mpire/claude-skills GitHub repo before running the install command.

Final thoughts

The gap between “good copy” and “booked meetings” is usually infrastructure, not writing quality. The copywriting manager sequence skill handles the writing layer: consistent structure, tight rules, persona-aware messaging. What it doesn’t do is send, track, or enrich.
That’s where lemlist picks up. Load the sequences, enrich your leads with verified contact data, add LinkedIn and call steps alongside your emails, and monitor everything from a single dashboard. Rated 4.6/5 on G2 with over 1,500 reviews (Lemlist Review 2026: Features, Pros & Cons, Alternatives) (Lemlist Review 2026: Features, Pros & Cons, Alternatives), lemlist is trusted by thousands of sales teams running exactly this kind of workflow.
Start a 14-day free trial to see how it works. No credit card required.
Share this post