Sequence Writer Skill

The Sequence Writer Skill takes any trigger event — a funding round, an executive hire, a hiring surge, an intent spike — and turns it into a complete cold outreach sequence. It pulls the verified contact details via the Lusha in Claude connector, confirms the account context, and writes a multi-step sequence where every touchpoint is grounded in the specific signal that created the reason to reach out in the first place.

Generic sequences fail because they could have been sent to anyone. This skill writes sequences that could only have been sent to this person at this company at this moment — because the signal is real, the contact is verified, and the context is specific. A VP of Sales who just joined a company scaling its SDR team gets a different sequence than a VP of Sales at a company that just raised a Series B. Same title, same function, completely different opening, completely different hook.

The skill writes up to five steps — email one through email five — with subject lines, body copy, and a suggested send cadence for each. Every step builds on the previous one without repeating it. The sequence ends when there’s nothing left worth saying, not when a step count is hit.

What it does

  • Signal-grounded opening — Step one is always built around the specific trigger event. The signal is the reason to reach out. Not a generic introduction, not a product pitch — a specific observation about something that happened at the account that makes the conversation relevant right now.
  • Verified contact details — Pulls the contact’s current title, tenure, and verified email via Lusha before writing a single word. If the contact has departed or the title has changed, it flags it before the sequence is written — not after it bounces.
  • Multi-step cadence — Writes up to five steps with suggested timing between each. Each step has a different angle, a different subject line, and a different ask — escalating from observation to relevance to social proof to urgency to final close.
  • Tone calibration — Adjusts tone based on seniority and context. A C-suite sequence reads differently from a VP sequence. A sequence triggered by a funding round reads differently from one triggered by a competitor intent signal.
  • Stacked signal enrichment — If additional signals are present at the account beyond the primary trigger, the skill weaves them into later steps of the sequence rather than front-loading everything into step one.

Use cases

New executive hire

A VP of Sales just joined a target account. Step one acknowledges the new role. Step two connects the company’s current growth signals to a specific problem your product solves. Step three introduces a relevant customer in a similar position. Step four surfaces urgency — the vendor evaluation window closes fast. Step five is the final ask.

Funding event

A Series B just closed. Step one leads with the round and what it signals about the company’s next phase. Step two connects the scaling motion to your product’s value proposition. Step three brings in a customer who went through the same growth stage. Steps four and five close on timing before the budget gets allocated elsewhere.

Competitor intent signal

The account is actively researching your category. Step one references the research activity without revealing the signal source. Step two differentiates your approach from the alternatives they’re likely evaluating. Step three through five build the case for a conversation before the shortlist gets set.

Skill definition

---
name: sequence-writer-skill
description: >
  Turn any trigger event into a full cold outreach sequence.
  Takes a signal, a contact identifier, and product context.
  Verifies the contact via Lusha, confirms account signals,
  and writes a multi-step sequence grounded in the specific
  trigger — not a generic template. Up to 5 steps with
  subject lines, body copy, and send cadence.
connectors:
  required: lusha
campus_url: https://www.lusha.com/campus/plays/sequence-writer-skill/
category: Skills
---

# Sequence Writer Skill

Write a complete cold outreach sequence grounded in a
specific trigger event. Verify the contact first. Build
every step around what actually happened at the account.
Stop when there's nothing left worth saying.

## Input

The user will provide via $ARGUMENTS:

- Trigger event: what happened at the account
  (e.g. "new VP of Sales joined", "Series B closed",
  "hiring surge in SDR roles", "intent signal on
  prospecting data")
- Contact: name and company, email, or LinkedIn URL
- What you sell: one sentence — product and the problem
  it solves
- Target outcome: what you want the sequence to achieve
  (e.g. "book a 20-minute discovery call")
- Tone: [optional] — direct / conversational / formal
- Steps: [optional] — number of steps, default is 5

If trigger event or contact is missing, ask once.
If what you sell is missing, ask once.
Never write the sequence before verifying the contact.

## Workflow

1. CONTACT VERIFICATION
   Resolve and verify the contact via Lusha before
   writing anything:
   - Current title and company confirmed
   - Tenure in current role
   - Verified email address
   - Flag if contact has departed — do not write
     sequence until user confirms new contact
   - Flag if title has changed since signal fired

2. ACCOUNT SIGNAL CONFIRMATION
   Confirm the trigger event via Lusha and check for
   additional signals at the account:
   - Verify the primary trigger is current and accurate
   - Surface any stacked signals — additional events
     at the same account in the last 90 days
   - Note signal recency — older signals get less
     prominence in the sequence

3. SEQUENCE ARCHITECTURE
   Before writing, define the arc:
   - Step 1: Lead with the trigger — specific, observed,
     no product pitch
   - Step 2: Connect signal to a problem your product
     solves — relevance, not features
   - Step 3: Social proof — a customer in a similar
     position who had the same problem
   - Step 4: Stacked signal or urgency — why now
     matters, not just why you
   - Step 5: Final close — direct ask, easy to say
     yes to

   Adjust arc if fewer steps requested.
   Never repeat the same angle twice.
   Each step must stand alone — assume previous
   steps were not read.

4. WRITE THE SEQUENCE
   For each step:
   - Subject line: specific, not clickbait, references
     the signal or the account where possible
   - Body copy: under 120 words for steps 1-3,
     under 80 words for steps 4-5
   - CTA: one ask per step, specific and low-friction
   - Send timing: suggested days after previous step

5. PRIVACY RULES
   - Mask contact name to initials in output
   - Show email domain only: i.e. j.k@[company].com
   - Mask phone numbers if shown: +1 415 555 ••••
   - Tag output: Contact confirmed live via Lusha
     connector, [date]

## Output Format

### Contact verified

| Field | Value |
|---|---|
| Name | [initials] |
| Title | |
| Tenure | |
| Company | |
| Verified email | [domain only] |
| Status | Active / Departed / Title changed |

Contact confirmed live via Lusha connector, [date]

---

### Trigger confirmed

| Signal | Type | Date | Score |
|---|---|---|---|

Additional signals at this account:
[list if present, note if none]

---

### Sequence — [Company], [Contact initials]

Target: [outcome the sequence is built toward]
Tone: [direct / conversational / formal]

---

STEP 1 — Send on day 0

Subject: [subject line]

[body copy]

[CTA]

---

STEP 2 — Send on day [X]

Subject: [subject line]

[body copy]

[CTA]

---

STEP 3 — Send on day [X]

Subject: [subject line]

[body copy]

[CTA]

---

STEP 4 — Send on day [X]

Subject: [subject line]

[body copy]

[CTA]

---

STEP 5 — Send on day [X]

Subject: [subject line]

[body copy]

[CTA]

---

Sequence complete. 5 steps. Suggested total cadence:
[X] days from first touch to final step.

If the contact has departed or the trigger is no longer
current, flag it here and recommend next action before
sending.
Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Lusha
Type: Skill

FAQ

  • What trigger events work best with this skill?

    The strongest triggers are named, time-stamped events tied to a specific person or account — a new executive in seat, a funding round that just closed, a hiring surge in the target function, or an intent signal on your category above a meaningful threshold. The more specific the trigger, the stronger the sequence. A VP of Sales who joined three weeks ago produces a better sequence than a general “company is growing” observation. If you don’t have a specific trigger, run the Find ICP-fit accounts showing intent right now play first to surface one before writing the sequence.

  • How is this different from the Cold Sequence From a Trigger Event play?

    The Cold Sequence From a Trigger Event play is a prompt you run once for a specific contact and trigger. This skill is an installable instruction set you save in Claude once and run repeatedly — any contact, any trigger, any product context — without rebuilding the prompt each time. The skill also adds contact verification before writing, stacked signal enrichment, and a structured sequence architecture that the standalone play doesn’t enforce. Use the play for a one-off sequence. Use this skill when writing sequences is a regular part of your workflow.

  • Can I adjust the tone for different personas?

    Yes. Pass “formal” for C-suite sequences where a more measured tone matches the seniority of the contact. Pass “conversational” for VP and director-level sequences where a peer-to-peer register works better. Pass “direct” for sequences where brevity and a strong ask are more important than relationship-building — typically for high-intent signals where the contact is already in a buying cycle and you want to get to the point fast. If no tone is specified, the skill defaults to direct.

  • What happens if the contact has departed since the signal fired?

    The skill flags the departure before writing a single word of the sequence and asks you to confirm a new contact before continuing. Sending a sequence to a departed contact is the most common and most avoidable outbound mistake — a bounced email on step one poisons the domain, and reaching out to someone who left the company tells every person who sees it that your data isn’t current. The verification step exists specifically to catch this before it happens.


  • Can I use this skill for re-engagement sequences, not just cold outreach?

    Yes — pass the re-engagement context as the trigger. “Contact went dark after two calls six months ago — company just raised a Series B” is a valid trigger input. The skill will build the sequence around the new signal rather than re-opening the previous conversation directly, which is almost always the better angle. If you want a dedicated re-engagement workflow, the Find the right moment to re-engage your closed-lost accounts play is built specifically for that motion and pairs well with this skill for the sequence writing step.

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.