Systems Lab

Agent skill

outbound-sequence-writer

Write a complete cold outbound sequence (email + LinkedIn) for one B2B SaaS segment: 4–6 touches, each earning the next, grounded in a real trigger and a specific point of view.

activeSelf-containedInstructions only523 words

Filed under Outbound email.

From vcxcvii/pipeline-skills · 10 skill entries · 0 · pushed 2026-09-25

What it does when it runs

Write a complete cold outbound sequence (email + LinkedIn) for one B2B SaaS segment: 4–6 touches, each earning the next, grounded in a real trigger and a specific point of view. Use when the user asks for cold emails, an outbound sequence, SDR messaging, or wants to activate a new segment or launch outbound for the first time.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about outbound-sequence-writer

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/vcxcvii/pipeline-skills.git /tmp/pipeline-skills
git -C /tmp/pipeline-skills sparse-checkout set "skills/outbound-sequence-writer"
mkdir -p ~/.claude/skills/outbound-sequence-writer
cp -R "/tmp/pipeline-skills/skills/outbound-sequence-writer/." ~/.claude/skills/outbound-sequence-writer/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 10 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add vcxcvii/pipeline-skills
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from vcxcvii/pipeline-skills/blob/d284df833e7dd2f21ff15384461ea6fcd3f454c4/skills/outbound-sequence-writer/SKILL.md, which is licensed MIT (repository). 523 words, 11 headings.

Outbound Sequence Writer (B2B SaaS)

Write outbound that reads like a sharp colleague noticed something, not like a tool merged fields into a template.

Prerequisites, refuse to write without these

  1. One segment, not "our ICP": a specific slice with a shared situation. If the user gives a broad target, narrow it first (offer 2–3 candidate slices and pick one together).
  2. A trigger: the observable event that makes now the right time (hired a RevOps lead, migrated stacks, posted a job, raised, shipped a feature).
  3. A point of view: one opinion about the prospect's situation the sender actually holds. No POV = no sequence; help the user find one by asking what they see broken in how these companies handle the problem today.
  4. The offer: what a reply gets the prospect. A meeting is not an offer; an audit, a teardown, a benchmark, a relevant asset is.

Sequence architecture

Default: 5 touches over ~3 weeks. Adjust to deal size (higher ACV = more patience, more personalization per touch).

TouchChannelJob
1EmailName the trigger + situation, state the POV, small ask
2Email (+2d)New angle on same POV, evidence or example, not "bumping this"
3LinkedInConnect, no pitch. One line referencing something true about them
4Email (+5d)The give: the offer itself, no strings
5Email (+7d)Straight close: honest, short, permission to say no

Writing rules, apply to every touch

  • Under 90 words for emails. Touch 5 under 50.
  • First line is about them, verifiable, and impossible to send to anyone else in the segment... but templatable via the trigger. Never "I hope this finds you well", never "My name is".
  • One idea per email. One link max. One question max.
  • Subject lines: 2–4 words, lowercase, specific ("your sdr ramp", "re: the pricing page"). No clickbait, no "quick question".
  • No sequence-speak: "just floating this to the top", "any thoughts?", "did you get my last email?", banned.
  • The ask ladder: interest ("worth a look?") before time ("15 minutes?"). Never open with a calendar link.

Output format

## Sequence: <segment> · trigger: <trigger>
**POV**: <one sentence>
**Offer**: <what a reply earns them>

### Touch 1, Email · Day 0
Subject: <subject>
<body>
*Why this works*: <one line>

...(all touches)...

### Personalization slots
<List each {variable} used, with 2 real-looking example values and where an SDR finds it in 2 minutes>

### Kill criteria
<When to stop: replies handling, opt-out language, and the signal that means this segment/angle is dead (e.g. <1% reply after 100 sends)>

Quality bar

Read each email aloud. If it sounds like software wrote it, rewrite it. If every email in the sequence could be sent by any vendor to any company, start over from the POV step.

Related skills

icp-sharpener-b2b before writing, so the list deserves the message. positioning-canvas for the claim the emails carry. sales-one-pager for what happens after the reply.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what outbound-sequence-writer does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.