victor-shulga/outbound-engine-skills

cold-email-playbook

Cold-email reference playbook for the parts the rest of the outbound toolkit does not cover.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill cold-email-playbook

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Cold Email Playbook

A reference skill with four modules. It answers infrastructure, framework, benchmark and re-engagement questions from its own files and hands every copywriting or audit job to the skill built for it.

Routing

All paths are relative to this skill's folder. Read only the file the request needs.

RequestRead
Build sending infrastructure; how many domains or mailboxes; Workspace / M365 setup; DNS records; warm-up; going live; monitoring; blacklist or bounce recovery; "it's broken / in spam"resources/email-infra.md
A named framework or structure for a cold email (Do the Math, Pattern Interrupt, Josh Braun's problem-first, etc.), first-line types, value-prop styles, the three-email arcresources/copy-frameworks.md
"Is this campaign healthy", reply / bounce / positive benchmarks, sequence length, TAM reuse, Golden ICP, seasonal dipsresources/benchmarks-and-rules.md
Reactivate a ghosted, no-show, closed-lost or old leadresources/re-engagement.md
Request
├─ infrastructure: build / size / set up / broken      → resources/email-infra.md
├─ which framework or structure for the copy           → resources/copy-frameworks.md
├─ benchmarks, health check, TAM reuse, Golden ICP     → resources/benchmarks-and-rules.md
├─ reviving old, ghosted or closed-lost leads          → resources/re-engagement.md
└─ writing a sequence, subject lines, auditing replies → Hand-off below

Quick answers (no file read needed)

  • Sizing: monthly emails ÷ 20 working days = daily volume; ÷ 20-25 per mailbox = mailboxes; × 1.5

buffer; ÷ 2 = domains. Mix about 60% Google Workspace and 40% Microsoft 365.

  • Never: send cold from the main domain; put more than 2 mailboxes on a domain; put several domains

in one tenant; switch warm-up off while live; raise per-mailbox limits to scale.

  • DNS: MX, SPF (one record only), DKIM, DMARC on every domain; DMARC moves from p=none to

enforcement once SPF and DKIM pass. Every sending domain points at a live page.

  • Warm-up: two weeks minimum, three recommended; plan the first campaign at setup day + 3 weeks.
  • Ramp per mailbox per day: Google 10-15 → 15-20 → 20-25 over about four weeks; Microsoft 5-10 →

10-12 → 12-15.

  • Health: bounce under 2% (pause over 5%), spam complaints under 0.1%, opens unreliable.
  • Copy: about 60-90 words, plain text, one interest-based ask, 2-3 emails, 3-5 days apart, a new

angle in each.

For DNS values, recovery steps and anything beyond these lines, read the file; do not improvise DNS records.

How to answer

  1. Pick the module from the routing table and read its file.
  2. State the benchmark that applies to the user's scenario, with its source as given in the file.
  3. Name the most common mistake for that scenario.
  4. If the request is really a hand-off case, say so and point to the right skill instead of

half-answering here.

Rules for any email text this skill produces (frameworks, re-engagement templates):

  • The CTA is interest-based: an interest question, an offer to send something, or a routing question.

Never a call, meeting or time-slot ask. If installed, cta-interest-based (pack outbound-engine-skills) has the CTA bank and wins over any template.

  • No invented results, client names or figures. Unfilled placeholders stay visible.

Hand-off

If installed (pack outbound-engine-skills unless noted):

The askSkill
Write a first-touch email or a full sequencesequence-writer
Follow-ups inside an active sequencefollowup-sequence
Subject linessubject-line-generator
P.S. lines and personalisation at scaleps-line-generator, personalization-pipeline
Choose the angle before writingangle-finder
Answer one inbound reply or objectionreply-objection-handler
Analyse a batch of repliesreply-audit
Judge whether campaign numbers are goodoutbound-analyst
Audit an existing setup's deliverability (this skill builds; that one audits)deliverability-audit
ICP, signals, hypothesesicp-builder, signal-research, hypothesis-builder

Credits

Modules condensed and rewritten from a public cold-outreach playbook collection, including its email-infrastructure guide and an outbound agency's lessons from 10M+ emails; framework names credited to their creators. Further figures from a cold-email playsheet built on a sending platform's data (2025) and Google's email sender guidelines. Router, practitioner rules and re-engagement templates: Victor Shulga (victorshulga.com).

Terms and plain-language output

<!-- glossary:start terms=spf-dkim-dmarc,warmup,bounce-rate,reply-rate,positive-reply-rate,open-rate,secondary-domain,blacklist,send-caps,sequence,tam,cta --> Rules for every document a client or their team will read (review, roast, canvas, offer cards, instruction):

  1. Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
  2. No internal codes or letter scales in the text (A/B/C, D L T E, BLEND numbers without words, Own/Shared/Generic, Z1.4, GATE 2.5, T1–T6). Write the meaning instead: «є цифра з клієнтом», not «A».
  3. Use the plain form from the table below. English stays only for tool names and for copy that ships in English (promises, hooks, subject lines). If the document is in another language, translate the plain form, never the internal term.
  4. Do not score what cannot exist yet. A block that depends on work not done (signal catalog, case studies, a previous step) gets «пропущено: спершу потрібно <що саме>», not a score.
  5. Every section of a review opens with one concrete action («до наступного дзвінка: …»), then at most five lines of why. No paragraph that only restates the framework.
Internal term (this skill)Write for the readerWhat it means
SPF / DKIM / DMARC, MXSPF, DKIM, DMARC (записи, що підтверджують домен)Технічні записи в налаштуваннях домену, які доводять поштовим сервісам, що лист справді від вас; без них листи йдуть у спам.
warmupпрогрів поштових скриньокпоступове збільшення кількості листів з нової скриньки, щоб пошта не потрапила в спам.
bounceвідмови доставкичастка листів, які не дійшли, бо адреса неправильна чи мертва.
reply rateчастка відповідейскільки людей з тих, кому написали, відповіли.
positive reply rateчастка позитивних відповідейскільки з тих, кому написали, відповіли з інтересом, а не «відпишіть мене»
open rate, opensчастка відкриттівСкільки листів відкрили; число неточне, бо поштові сервіси самі відкривають листи, тож це лише підказка.
secondary domain, sending domainокремий домен для розсилкиДомен, схожий на основний, лише для холодних листів, щоб проблеми з доставкою не зачепили основну пошту.
blacklist, listedчорний список поштових сервісівПерелік доменів, яким сервіси не довіряють; потрапили туди, тож розсилку зупиняємо і шукаємо причину.
send caps, daily volume per mailbox, rampденний ліміт на скринькуСкільки листів одна скринька надсилає за день; ліміт піднімаємо поступово і масштабуємось кількістю скриньок.
sequences and templatesланцюжки листів і шаблонисерія з кількох листів чи повідомлень одному проспекту з паузами між ними.
TAM, TAM reuseвесь ринок (TAM)Усі компанії, що підходять під ICP; раз на квартал проходимо цей список знову з новим аргументом.
CTAпрохання в кінці листаконкретний маленький наступний крок: відповісти, подивитися, погодитися на дзвінок

<!-- glossary:end -->

do mesmo repositório

Mais Skills

Todos os Skills