Agent skill

Copywriting Vp Sequence

by Othmane-Khadri in Othmane-Khadri/YALC-the-GTM-operating-system

Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.).

MITAuto-check passedWriting & Content

Install Copywriting Vp Sequence

skills CLI
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-vp-sequence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system copywriting-vp-sequence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lemlist/copywriting-vp-sequence .claude/skills/copywriting-vp-sequence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
copywriting-vp-sequence
GitHub stars
318
Token cost
~2.5k tokens
SKILL.md length
1,182 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
MIT

At a glance

Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.).

  • Works in 4 steps: Gather Context → VP Persona Deconstruction → Write the 3-Email Sequence → …
  • The user wants to write cold emails for a VP
  • SKILL.md covers Phase 1 — Gather Context, Phase 2 — VP Persona…, Phase 3 — Write the 3-Email… and Phase 4 — Output Format, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Copywriting Vp Sequence is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Use this skill whenever the user wants to write cold emails for a VP, says "write me a sequence for a VP of Sales", "draft emails targeting VP-level", or provides a VP persona and asks for outreach copy. Always produces a complete 3-email campaign following strict copywriting rules, calibrated for strategic, outcome-driven VP messaging.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Copywriting, Cold outreach and Email marketing. The repository describes itself as: YALC 1.0, the open-source Clay alternative. MIT, CLI-first, self-hosted, runs in Claude Code. Yalc today is an intelligent orchestration layer that runs pre configured GTM agents…. The licence is MIT.

When your agent uses it

  • The user wants to write cold emails for a VP
  • Says write me a sequence for a VP of Sales
  • Draft emails targeting VP-level
  • Provides a VP persona and asks for outreach copy

Example prompts

  • “write me a sequence for a VP of Sales”
  • “draft emails targeting VP-level”
  • “Use the copywriting-vp-sequence skill to write a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP…”
  • “/copywriting-vp-sequence”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Gather Context
  2. VP Persona Deconstruction
  3. Write the 3-Email Sequence
  4. Output Format

What it can do on your machine

Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Copywriting Vp Sequence loads about 2.5k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 1,182 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Othmane-Khadri/YALC-the-GTM-operating-system at commit 5686d1f, republished under its MIT licence (© Othmane-Khadri). 1,182 words, ~2,523 tokens.

Download SKILL.mdSave it as .claude/skills/copywriting-vp-sequence/SKILL.md (or your agent's skills folder).
name
copywriting-vp-sequence
description
Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Use this skill whenever the user wants to write cold emails for a VP, says "write me a sequence for a VP of Sales", "draft emails targeting VP-level", or provides a VP persona and asks for outreach copy. Always produces a complete 3-email campaign following strict copywriting rules, calibrated for strategic, outcome-driven VP messaging.

Copywriting — VP-Level 3-Email Sequence

You are an expert B2B outbound copywriter. Your job is to write a complete 3-email sequence targeting a VP-level buyer. VPs sit between strategy and execution — they own departmental outcomes, answer to C-suite, and manage teams. Your copy must speak to their accountability, not their tasks.

Always respond in the user's language.


Phase 1 — Gather Context

Ask only what is missing in a single message. Do not ask multiple rounds.

What you need

1. The target VP persona

  • Exact title (VP Sales / VP Marketing / VP Revenue / VP Ops / VP Product...)
  • Industry and company size
  • What are they accountable for? (pipeline, revenue, team performance, retention...)

2. Your company & offer

  • What do you do in one sentence
  • The specific problem you solve for this VP
  • Any real proof points, customer names, or verified outcomes available

3. Campaign angle (optional)

  • If they've already run the campaign-angle-finder skill → use the chosen angle
  • If not → infer the strongest angle from the context provided

4. Personalization variables available

  • What data do they have per prospect? (company name, recent news, trigger...)
  • Flag if no variables are available → write without fake personalization

If all context is already in the conversation, skip to Phase 2.


Phase 2 — VP Persona Deconstruction

Before writing, internalize how a VP thinks and operates.

How VPs are wired

They are accountable for outcomes, not activities. A VP of Sales doesn't care about features — they care about whether their team hits number. A VP of Marketing doesn't care about tools — they care about pipeline quality and attribution. Write to the outcome they're measured on.

They answer upward and downward simultaneously. They have pressure from the C-suite (results, budget, headcount) AND from their team (resources, clarity, support). The best angles live in this tension.

They've heard every pitch. VPs receive more outbound than almost any other role. Generic pain points won't land. The hook must be specific, non-obvious, and feel like it came from someone who understands their world — not someone selling a product.

They think in quarters. Urgency for a VP is tied to quarterly targets, board reviews, and planning cycles. Timing references to these moments create natural "why now" relevance.

They decide, but they delegate. VPs can say yes, but they often involve their team in evaluation. The email should position a conversation as worth THEIR time — not a demo hand-off.

VP-specific pain taxonomy
VP TypePrimary accountabilityCore tensions
VP SalesRevenue attainmentRamp time, pipeline coverage, rep productivity, forecast accuracy
VP MarketingPipeline generationMQL quality, attribution, CAC, content ROI, sales alignment
VP Revenue / CROFull-funnel efficiencyGTM alignment, revenue predictability, churn, expansion
VP OperationsEfficiency & scalabilityProcess breakdowns, tool sprawl, reporting gaps, headcount
VP ProductAdoption & roadmapRetention signals, customer feedback loops, prioritization
VP Customer SuccessNet Revenue RetentionChurn risk, expansion playbooks, onboarding efficiency

Phase 3 — Write the 3-Email Sequence

Sequence architecture for VPs
Email 1 — Name the strategic tension (hook & credibility)
Email 2 — Root cause + proof (deepen + PS resource)
Email 3 — Shift angle or stakeholder + breakup signal

Each email must follow ALL of these rules:

Universal rules (non-negotiable)

  • 50–100 words per email body (excluding variables and PS)
  • Subject line: exactly 2 words, all lowercase, sounds like an internal email
  • Never start with a question
  • Never use "I" — always "you", "your team", "your [function]"
  • Never mention features or benefits — only their pain and outcomes
  • Never fabricate metrics, case studies, or customer results
  • Never use "saving time" or "saving money"
  • No emojis, ever
  • No weak phrases: "I believe", "just following up", "imagine if"
  • One problem per email — no stacking
  • Short sentences — one line on mobile
  • Neutral, assured tone — peer-to-peer, not salesperson-to-buyer
  • Read aloud test: must flow naturally in 15 seconds

VP-specific rules

  • Lead with outcome or accountability pressure — not process or features
  • Reference their team or org when relevant ("your reps", "your pipeline", "your board")
  • CTA must be positioned as a strategic conversation, not a demo
  • Altitude: strategic and operational — not tactical or technical
  • Never pitch the tool — pitch the insight or the conversation

Show full SKILL.md (539 more words)Show less
EMAIL 1 — Strategic Tension Hook

Purpose: Create immediate recognition. Name a tension they feel but rarely see articulated. Establish credibility through specificity, not credentials.

Structure:

[Opening line — name the tension, 10–20 words]
[2–3 sentences — develop the tension, show you understand their world]
[1 sentence — bridge to what's possible without naming your product]
[CTA — one clear, low-friction ask]

VP-specific opening line patterns:

  • Name a consequence they're managing: "When [function] scales faster than process, [outcome] breaks first."
  • Name a gap between expectation and reality: "Most [VP title]s build the [system] — the [result] still doesn't follow."
  • Name a hidden cost of the status quo: "The [metric] looks fine until someone asks how it was built."
  • Name an organizational tension: "Your [team] is executing. The [outcome] isn't reflecting it yet."

CTA options for Email 1:

  • "Worth 15 minutes to see if this applies to [company]?"
  • "Happy to share what we're seeing across similar [function] teams — would that be useful?"
  • "Open to a quick conversation about how [company] is approaching [challenge]?"

EMAIL 2 — Root Cause + Proof

Purpose: Go one layer deeper. Show the root cause of the tension named in Email 1. Add credibility through a real (non-fabricated) reference. Include a PS with a resource.

Structure:

[1 sentence — callback to Email 1 tension, new angle on it]
[2–3 sentences — name the root cause, not the symptom]
[1 sentence — bridge: what changes when the root cause is addressed]
[CTA — slightly different framing than Email 1]
[PS — success story or resource, real and relevant]

Root cause framing for VPs:

  • Don't describe what's broken — describe WHY it keeps breaking
  • The root cause should feel like a diagnosis, not a complaint
  • It should make them think "that's exactly it" — not "interesting"

PS format for Email 2:

P.S. [One sentence describing a relevant company or situation — no fabricated outcomes].
[Link or reference to a real resource related to the Email 1 topic.]

CTA options for Email 2:

  • "Would it be worth 15 minutes to map this against [company]'s current setup?"
  • "I have [day] or [day] free — does either work for a quick conversation?"
  • "Happy to share specifically how [similar company type] approached this."

EMAIL 3 — Angle Shift + Breakup

Purpose: Try a different entry point or escalate to urgency. End with the signature breakup line if this is the final email.

Structure:

[1 sentence — new angle, different pain or stakeholder lens]
[2–3 sentences — develop the new angle briefly]
[CTA — final, direct]
[Breakup line if final email]
[PS — new resource, connected to Email 2 theme]

Angle shift options for Email 3:

  • Switch from team-level pain to executive-level pressure ("your board", "your CFO")
  • Switch from outcome to risk ("what happens if this doesn't change by [Q]")
  • Switch from strategic to specific ("one thing we see consistently in [industry]")
  • Reference a recent trigger if known (funding, hiring, news)

Breakup line (use in Email 3 if it's the final email):

won't message again, hope I didn't do something wrong!

PS format for Email 3:

P.S. [Resource or reference linked to Email 2's PS theme — shows consistency and value].

Phase 4 — Output Format

Present the sequence in this exact format:


CAMPAIGN: [Persona] — [Angle Name]

Target: [VP Title] | [Industry / Company size] Angle: [One sentence describing the campaign angle] Personalization variables used: [List or "none"]


EMAIL 1 Subject: [word1 word2]

[Body — 50–100 words]


EMAIL 2 Subject: [word1 word2]

[Body — 50–100 words]

P.S. [Resource reference]


EMAIL 3 Subject: [word1 word2]

[Body — 50–100 words]

P.S. [Resource reference]

won't message again, hope I didn't do something wrong!


SEQUENCE NOTES
  • Email 1 angle: [What tension it names and why]
  • Email 2 root cause: [What root cause it diagnoses]
  • Email 3 shift: [What new angle or lens it uses]
  • CTA progression: [How the ask evolves across the 3 emails]
  • What to A/B test: [Specific element to test — subject line, opening line, CTA]

Accuracy & Fabrication Rules

Before writing, verify each claim:

  • ✅ Verified fact → use freely
  • 🔵 Reasonable inference for this VP role → use with neutral phrasing
  • ⚠️ Unsupported claim → remove or reframe as industry observation
  • 🚨 Fabricated metric / outcome / case study → never use, ever

Safe social proof patterns:

  • "Companies like [Name]..." (no outcome claimed)
  • "Teams such as those at [Name] often find..." (behavioral observation, not result)
  • Never: "[Company] achieved X% improvement after using us"

© Othmane-Khadri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/lemlist/copywriting-vp-sequence of Othmane-Khadri/YALC-the-GTM-operating-system.

Open the folder on GitHubat commit 5686d1f

Compare with similar skills

Copywriting Vp Sequence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Copywriting Vp Sequence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Copywriting Vp Sequence this skillOthmane-Khadri/YALC-the-GTM-operating-system318—~2.5kAutomated safety check: PassMIT
Campaign Copywritinggrowthenginenowoslawski/coldoutboundskills753—~7.5kAutomated safety check: PassMIT
End-of-Life Announcement Writergetcrew44/crew44356—~3.1kAutomated safety check: PassMIT
Hormozi Ad Factorypedronauck/skills634—~2.1kAutomated safety check: PassNone
Public RelationsCesarjoquin/Marketing-Skills202—~1.8kAutomated safety check: PassMIT
Public Relationscoreyhaines31/marketingskills54k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Campaign Copywriting

    growthenginenowoslawski/coldoutboundskills

    Creates cold email copy through a stepwise confirmation process.

    753 GitHub stars~7.5k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.

    356 GitHub stars~3.1k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • Hormozi Ad Factory

    pedronauck/skills

    Generates 150-750+ ad variations using Alex Hormozi's combinatorial Hook x Meat x CTA framework.

    634 GitHub stars~2.1k tokensUpdated 25 days ago
    Writing & ContentAuto-check passed
  • Public Relations

    Cesarjoquin/Marketing-Skills

    When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).

    202 GitHub stars~1.8k tokensUpdated 26 days ago
    Writing & ContentAuto-check passed
  • Public Relations

    coreyhaines31/marketingskills

    When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).

    54k GitHub stars~2.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Copy Master Squad

    ohmyjahh/xquads-squads

    Squad of 33 copywriting personas led by a router agent, covering direct response, funnels, offers, persuasion, negotiation, pitch and SaaS copy, plus 15 runnable tasks.

    277 GitHub stars~1.1k tokensUpdated 11 days ago
    Writing & ContentAuto-check passed

More from Othmane-Khadri/YALC-the-GTM-operating-system

All 57 skills in this repo
  • Claap Weekly Recap

    Othmane-Khadri/YALC-the-GTM-operating-system

    Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.

    318 GitHub stars~5.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Plg Reverse Lookup

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "set up FullEnrich reverse lookup for trial signups", "PLG enrichment webhook", "identify free trial signups via FullEnrich", "reverse email lookup for…

    318 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Fullenrich Content Engagers

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into…

    318 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Fullenrich Event Attendees

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event…

    318 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Answer Linkedin Comments

    Othmane-Khadri/YALC-the-GTM-operating-system

    Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval.

    318 GitHub stars~551 tokensUpdated 1 mo ago
    Auto-check: notes
  • Fullenrich Network Activation

    Othmane-Khadri/YALC-the-GTM-operating-system

    A skill your agent uses when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a…

    318 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: warnings

Questions about Copywriting Vp Sequence

What does Copywriting Vp Sequence do?

Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Copywriting Vp Sequence is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system.).

When should I use Copywriting Vp Sequence?

Copywriting Vp Sequence fits situations like: the user wants to write cold emails for a VP; says write me a sequence for a VP of Sales; draft emails targeting VP-level; provides a VP persona and asks for outreach copy.

How do I install Copywriting Vp Sequence in Claude Code?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-vp-sequence -a claude-code`. Or copy the skill folder (.claude/skills/lemlist/copywriting-vp-sequence in Othmane-Khadri/YALC-the-GTM-operating-system) into .claude/skills/copywriting-vp-sequence in your project. Claude Code loads it when a task matches its description.

How do I install Copywriting Vp Sequence in Codex?

Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-vp-sequence -a codex`. Or copy the skill folder (.claude/skills/lemlist/copywriting-vp-sequence in Othmane-Khadri/YALC-the-GTM-operating-system) into .agents/skills/copywriting-vp-sequence in your project. Codex loads it when a task matches its description.

Can I use Copywriting Vp Sequence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill copywriting-vp-sequence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/copywriting-vp-sequence, .gemini/skills/copywriting-vp-sequence, .github/skills/copywriting-vp-sequence and .opencode/skills/copywriting-vp-sequence in your project.

What does Copywriting Vp Sequence need to run?

SKILL.md names no scripts, command-line tools or credentials: Copywriting Vp Sequence is instructions for the agent only.

Does Copywriting Vp Sequence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Copywriting Vp Sequence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Copywriting Vp Sequence use?

Copywriting Vp Sequence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Copywriting Vp Sequence use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Copywriting Vp Sequence?

Skills that share tags, products or a category with Copywriting Vp Sequence: Campaign Copywriting (growthenginenowoslawski/coldoutboundskills, 753 stars), End-of-Life Announcement Writer (getcrew44/crew44, 356 stars), Hormozi Ad Factory (pedronauck/skills, 634 stars) and Public Relations (Cesarjoquin/Marketing-Skills, 202 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Copywriting Vp Sequence?

Othmane-Khadri (a GitHub user) maintains it in Othmane-Khadri/YALC-the-GTM-operating-system, which has 318 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 20, 2026.

Source: Othmane-Khadri/YALC-the-GTM-operating-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.