outbound-copywriter
Use this skill when a cold outbound sequence needs to be written or rewritten and the messages go to people who have never replied to you - "write the cold email sequence for this segment", "our reply rate has tanked, rewrite the copy", "we need a new angle for this campaign", "write the LinkedIn connection message and the follow-ups", "this campaign is dead, what do we say instead", "draft the breakup email", "make this sequence sound less like a template", "we just pulled a signal list, what do we send them". Reads the ICP definition, the proof points and any prior reply data, then produces a full sequence: subject lines, a four-step body sequence with one job per step, the archetype chosen and the reason, and a QA pass against a copy checklist. It drafts only. It never sends, and it never uploads to a sequencer without approval. NOT organic posts published to your own audience, which is a different reader and the linkedin-post-writer skill. NOT the diagnosis of an underperforming ca
Workflowsio · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Workflowsio/company-os-starter-kit --skill outbound-copywriterAbout this skill
name: outbound-copywriter description: | Use this skill when a cold outbound sequence needs to be written or rewritten and the messages go to people who have never replied to you - "write the cold email sequence for this segment", "our reply rate has tanked, rewrite the copy", "we need a new angle for this campaign", "write the LinkedIn connection message and the follow-ups", "this campaign is dead, what do we say instead", "draft the breakup email", "make this sequence sound less like a template", "we just pulled a signal list, what do we send them". Reads the ICP definition, the proof points and any prior reply data, then produces a full sequence: subject lines, a four-step body sequence with one job per step, the archetype chosen and the reason, and a QA pass against a copy checklist. It drafts only. It never sends, and it never uploads to a sequencer without approval. NOT organic posts published to your own audience, which is a different reader and the linkedin-post-writer skill. NOT the diagnosis of an underperforming campaign whose cause is deliverability, list quality or channel choice, which is the gtm-strategist skill and has to be ruled out first, because no rewrite fixes a domain reputation problem.
Outbound copywriter
When this applies
A sequence is going to strangers who have no reason to reply, and the copy has to earn the first response on its own. That covers a new segment, a rebuild of something underperforming, a scheduled refresh of a long-running campaign, and the first sequences off a newly warmed domain. It also covers cold LinkedIn connection notes and their follow-ups, which are the same job in a shorter format.
Maturity: the frameworks here have been run against real campaigns and the thresholds are the ones we use. They are not tuned to your business until you run the interview below and write your own numbers into this file.
What it produces
- One archetype selection with the reason it beat the other six.
- Ten subject lines, narrowed to two for the test.
- A four-step sequence, each step with one job, in plain text at 60 to 120 words per email.
- A completed QA checklist with every failed line named.
- A test plan: what varies between the two variants, and the sends per variant before anyone reads the result.
- A ledger entry per shipped variant, so the next rebuild starts from measured copy rather than taste.
Fill these in
The interview writes these into this file on the first run. Until then they are placeholders and the skill will ask.
{{SEQUENCER}}- where sequences are built and sent{{CRM}}- where prospect and reply data lives{{APPROVAL_OWNER}}- who approves copy before it reaches a sequencer, and who approves the send{{SEND_FLOOR}}- sends per variant before a verdict is allowed (default: 200){{LEDGER}}- where scored variants are kept between campaigns
First run: the customization interview
Run this as a one-time setup step, outside any live engagement, and never mid-run. It edits files, and editing a skill or its reference material while it is being used against real work is how a run half-follows two versions of its own instructions. Company-level answers belong in these files; anything specific to one account or one person belongs in clients/<slug>/ or company-wiki/, not in a reference file every account's run reads.
Research first, then ask. Before the first question, read whatever already exists: past sequences in {{SEQUENCER}}, reply data in {{CRM}}, the ICP definition, the website, any case studies. Pre-fill every answer you can and present it for correction. Never ask for something you could have detected.
Then ask what is left, one question at a time, waiting for each answer.
Business context
- What do you sell, in one sentence a buyer would recognise?
- Who is the buyer? Title, company size, industry, seniority.
- What is your strongest proof point, with the number in it?
- What does the buyer do about this problem today, without you?
Voice and position
5. Paste two or three messages you have sent that felt right. Voice gets extracted from these rather than described.
6. What words must never appear in your copy? These go into the banned list in references/copy-qa.md.
7. Premium, mid-market or budget? This decides how hard the CTA can push.
Operating context 8. What sends the mail, what holds the data, and what is the current positive reply rate? 9. Average deal size, because a high-value deal takes a softer ask and a low-value one takes a direct one.
Then write the answers into the files: voice patterns and banned words into references/copy-qa.md, proof points into the SPARK examples in references/spark-and-archetypes.md, and the placeholders above into this file. Say which files you changed.
Reference routing
| File | What it contains | When to read it | What breaks if you skip it |
|---|---|---|---|
references/spark-and-archetypes.md | The five SPARK elements with good and bad examples, ten subject line formulas, the seven archetypes and the selection tree | Before writing any first draft, and whenever the archetype choice is not obvious | The email becomes a generic five-paragraph pitch with no structural job per line |
references/persuasion-patterns.md | Seven power patterns and the calibrated-question layer, each with the place in the sequence where it belongs | While drafting, once the archetype is chosen | The copy is structurally correct and reads flat, because nothing in it makes the reader stop and self-assess |
references/sequence-templates.md | Steps 1 to 5 with the job of each, filled examples, and the rule for when step 5 should not exist | When writing anything past the opener | Follow-ups turn into "just bumping this", which is the fastest way to train a list to ignore you |
references/copy-qa.md | The anti-pattern table, voice rules, banned words, the QA checklist, the A/B protocol, the performance thresho |