Email Spintax Generator

Smartlead Spintax Skill

by growthenginenowoslawski · MIT license · ★ 730 on GitHub

Smartlead Spintax Skill cover

Adds Smartlead-compatible spintax to cold email sequences for deliverability. Use this skill whenever the user asks to add spintax, spin text, add variations, or improve deliverability of email copy — especially when they mention…

---
name: smartlead-spintax
description: Adds Smartlead-compatible spintax to cold email sequences for deliverability. Use this skill whenever the user asks to add spintax, spin text, add variations, or improve deliverability of email copy — especially when they mention Smartlead, cold email sequences, or paste HTML email content. Also trigger when the user says "spintax", "spin", "variations", "deliverability spintax", or references adding randomized alternatives to email copy. Works with both plain text and HTML input.
---

# Smartlead Spintax Skill

Add deliverability-improving spintax to cold email sequences using Smartlead's syntax, without changing the meaning or tone of the original messaging.

## Core Concept

Spintax lets Smartlead randomly pick one option per send, so no two emails are identical. This reduces pattern detection by spam filters and improves deliverability.

**Smartlead syntax:** `{option1|option2|option3}`

Each option inside the curly braces is separated by a pipe `|`. Smartlead picks one at random per email send.

---

Overview

Add deliverability-improving spintax to cold email sequences using Smartlead's syntax, without changing the meaning or tone of the original messaging.

Manual install (npx, ZIP)
Claude Codenpx skills add growthenginenowoslawski/coldoutboundskills --skill smartlead-spintax -g -a claude-code
Claude Code (degit)npx degit growthenginenowoslawski/coldoutboundskills/skills/smartlead-spintax#main ~/.claude/skills/smartlead-spintax
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.0 KB
Read SKILL.md here
growthenginenowoslawski/main1 file shown
SKILL.md
Show the full text169 lines

Smartlead Spintax Skill

Add deliverability-improving spintax to cold email sequences using Smartlead's syntax, without changing the meaning or tone of the original messaging.

Core Concept

Spintax lets Smartlead randomly pick one option per send, so no two emails are identical. This reduces pattern detection by spam filters and improves deliverability.

Smartlead syntax: {option1|option2|option3}

Each option inside the curly braces is separated by a pipe |. Smartlead picks one at random per email send.


Input Handling

HTML Input (preferred workflow)

Users often paste HTML from Smartlead because copy-pasting plain text loses formatting (spaces, line breaks). When the user provides HTML:

  1. Mentally parse the text content from the HTML
  2. Add spintax to the text content
  3. Return the full HTML with spintax baked in, preserving all HTML tags, <br>, <div>, structure exactly as received
  4. Output as a code block so the user can copy-paste straight back into Smartlead
Plain Text Input

If the user pastes plain text, add spintax and return plain text.


The Golden Rule: No Broken Combinations

Every possible combination that Smartlead could randomly assemble MUST read as a natural, grammatically correct, complete sentence. This is the single most important rule.

What "broken combo" means

When spintax options are placed near each other, every possible pairing across adjacent spintax blocks must work together. If option A from block 1 combines with option B from block 2 to form a weird or ungrammatical sentence, that's a broken combo.

How to prevent broken combos

Make each spintax block a self-contained phrase. The options within one block should be interchangeable without depending on what another nearby block picks.

BAD — dependent blocks that can break:

{let me know if|would} {{employeeline}} {would be better to speak to|be a better person to chat with}

Problem: "would" + "would be better to speak to" = "would {{name}} would be better to speak to" — broken.

GOOD — each option is a full standalone phrase:

{let me know if {{employeeline}} would be better to speak to about this?|would {{employeeline}} be a better person to chat with about this?|should I be reaching out to {{employeeline}} about this instead?}

Each option is a complete sentence on its own. No cross-block dependency.

Verification step

After adding spintax, mentally walk through every combination across adjacent blocks. If any pairing sounds off, restructure so each block is independent. When the sentence structure makes independent blocks risky, wrap the entire sentence in one spintax block with full sentence alternatives.


What to Spin

Add 2-3 options per spintax block. Target these elements:

Always spin
  • Greetings: {Hey|Hi} — simple, always safe
  • Opt-out / unsubscribe lines: These are repetitive across emails and easy to spin without tone change
  • CTAs: Different phrasings of the same ask
  • Transition words and connectors: "just", "also", "actually", etc.
Spin when natural
  • Verb choices: {help|work with}, {built|made}, {handles|manages|tackles}
  • Descriptors: {completely free|on us|100% free}
  • Sentence-level rephrasings: When a line can be said 2-3 different ways without changing meaning
Never spin
  • Smartlead variables: {{first_name}}, {{company_name}}, {{custom_variable}} — leave these exactly as-is
  • Signature placeholders: %signature% — never touch
  • Specific data points: Numbers, stats, brand names, product names, pricing
  • Technical terms or product descriptions that need to be precise

Tone Preservation

The spintax options must match the tone and register of the original. If the original is casual, all options should be casual. If it's direct, keep all options direct. Don't introduce formality where there was none, and don't add slang where the original was professional.

Original tone: casual/direct

  • ✅ {Worth a shot?|Want to give it a try?|Open to trying it out?}
  • ❌ {Would you be amenable to a trial?|Worth a shot?} — register mismatch

Output Format

For HTML input

Return the spintaxed HTML inside a code block:

{Hey|Hi} {{first_name}}, {open to a free backlink on|interested in a free backlink from} Forbes, WSJ, or Tech Times for {{company_name}}?
<br>
<br>{We work with|We partner with} a network of over 1,200 publishers...
For plain text input

Return the spintaxed text inside a code block:

{Hey|Hi} {{first_name}}, {open to a free backlink on|interested in a free backlink from} Forbes, WSJ, or Tech Times for {{company_name}}?
After each email

State: "All combos clean." — confirming you verified every combination. If you found and fixed something, note what you changed and why.

Then ask: "Next?" or "Drop the next one." to keep the flow moving.


Multi-Email Sequences

When the user is doing a full sequence, process one email at a time. After each:

  1. Output the spintaxed version
  2. Confirm combos are clean
  3. Prompt for the next email

Keep a mental count of which email in the sequence you're on (Email 1, Email 2, etc.) so you can reference them if the user asks.


Flagging Issues

If you spot something in the original copy that's awkward or could be improved (independent of spintax), flag it briefly after the spintax output. For example:

One small flag: "does QA differently" reads a bit awkward — consider swapping to {handles|approaches|tackles} instead.

Keep flags minimal. Only flag things that would actually hurt the email's performance. Don't rewrite their copy unless asked.


Quick Reference

Element Example
Syntax {option1|option2|option3}
Greeting {Hey|Hi}
Verb swap {help|work with|partner with}
Full sentence {Is this worth exploring?|Want to give it a try?|Open to a quick chat?}
Opt-out {If this isn't relevant, just reply and I won't follow up.|Not relevant? Just reply and I won't reach out again.}
Never touch {{first_name}}, {{company_name}}, %signature%

What to do next

Launch the spintaxed copy via /smartlead-campaign-upload-public — the spintax gets embedded in the variants.yaml body fields and renders per-recipient on send.

Or wait: skip this skill until your copy is final. Spintax complicates later debugging.

  • /campaign-copywriting — writes the base copy this skill varies
  • /smartlead-campaign-upload-public — launches the spintaxed campaign
1---
2name: smartlead-spintax
3description: Adds Smartlead-compatible spintax to cold email sequences for deliverability. Use this skill whenever the user asks to add spintax, spin text, add variations, or improve deliverability of email copy — especially when they mention Smartlead, cold email sequences, or paste HTML email content. Also trigger when the user says "spintax", "spin", "variations", "deliverability spintax", or references adding randomized alternatives to email copy. Works with both plain text and HTML input.
4---
5 
6# Smartlead Spintax Skill
7 
8Add deliverability-improving spintax to cold email sequences using Smartlead's syntax, without changing the meaning or tone of the original messaging.
9 
10## Core Concept
11 
12Spintax lets Smartlead randomly pick one option per send, so no two emails are identical. This reduces pattern detection by spam filters and improves deliverability.
13 
14**Smartlead syntax:** `{option1|option2|option3}`
15 
16Each option inside the curly braces is separated by a pipe `|`. Smartlead picks one at random per email send.
17 
18---
19 
20## Input Handling
21 
22### HTML Input (preferred workflow)
23 
24Users often paste HTML from Smartlead because copy-pasting plain text loses formatting (spaces, line breaks). When the user provides HTML:
25 
261. Mentally parse the text content from the HTML
272. Add spintax to the text content
283. Return the full HTML with spintax baked in, preserving all HTML tags, `<br>`, `<div>`, structure exactly as received
294. Output as a code block so the user can copy-paste straight back into Smartlead
30 
31### Plain Text Input
32 
33If the user pastes plain text, add spintax and return plain text.
34 
35---
36 
37## The Golden Rule: No Broken Combinations
38 
39Every possible combination that Smartlead could randomly assemble MUST read as a natural, grammatically correct, complete sentence. This is the single most important rule.
40 
41### What "broken combo" means
42 
43When spintax options are placed near each other, every possible pairing across adjacent spintax blocks must work together. If option A from block 1 combines with option B from block 2 to form a weird or ungrammatical sentence, that's a broken combo.
44 
45### How to prevent broken combos
46 
47**Make each spintax block a self-contained phrase.** The options within one block should be interchangeable without depending on what another nearby block picks.
48 
49**BAD — dependent blocks that can break:**
50```
51{let me know if|would} {{employeeline}} {would be better to speak to|be a better person to chat with}
52```
53Problem: "would" + "would be better to speak to" = "would {{name}} would be better to speak to" — broken.
54 
55**GOOD — each option is a full standalone phrase:**
56```
57{let me know if {{employeeline}} would be better to speak to about this?|would {{employeeline}} be a better person to chat with about this?|should I be reaching out to {{employeeline}} about this instead?}
58```
59Each option is a complete sentence on its own. No cross-block dependency.
60 
61### Verification step
62 
63After adding spintax, mentally walk through every combination across adjacent blocks. If any pairing sounds off, restructure so each block is independent. When the sentence structure makes independent blocks risky, wrap the entire sentence in one spintax block with full sentence alternatives.
64 
65---
66 
67## What to Spin
68 
69Add 2-3 options per spintax block. Target these elements:
70 
71### Always spin
72- **Greetings:** `{Hey|Hi}` — simple, always safe
73- **Opt-out / unsubscribe lines:** These are repetitive across emails and easy to spin without tone change
74- **CTAs:** Different phrasings of the same ask
75- **Transition words and connectors:** "just", "also", "actually", etc.
76 
77### Spin when natural
78- **Verb choices:** `{help|work with}`, `{built|made}`, `{handles|manages|tackles}`
79- **Descriptors:** `{completely free|on us|100% free}`
80- **Sentence-level rephrasings:** When a line can be said 2-3 different ways without changing meaning
81 
82### Never spin
83- **Smartlead variables:** `{{first_name}}`, `{{company_name}}`, `{{custom_variable}}` — leave these exactly as-is
84- **Signature placeholders:** `%signature%` — never touch
85- **Specific data points:** Numbers, stats, brand names, product names, pricing
86- **Technical terms or product descriptions** that need to be precise
87 
88---
89 
90## Tone Preservation
91 
92The spintax options must match the tone and register of the original. If the original is casual, all options should be casual. If it's direct, keep all options direct. Don't introduce formality where there was none, and don't add slang where the original was professional.
93 
94**Original tone: casual/direct**
95- ✅ `{Worth a shot?|Want to give it a try?|Open to trying it out?}`
96- ❌ `{Would you be amenable to a trial?|Worth a shot?}` — register mismatch
97 
98---
99 
100## Output Format
101 
102### For HTML input
103Return the spintaxed HTML inside a code block:
104 
105```html
106{Hey|Hi} {{first_name}}, {open to a free backlink on|interested in a free backlink from} Forbes, WSJ, or Tech Times for {{company_name}}?
107<br>
108<br>{We work with|We partner with} a network of over 1,200 publishers...
109```
110 
111### For plain text input
112Return the spintaxed text inside a code block:
113 
114```
115{Hey|Hi} {{first_name}}, {open to a free backlink on|interested in a free backlink from} Forbes, WSJ, or Tech Times for {{company_name}}?
116```
117 
118### After each email
119State: "All combos clean." — confirming you verified every combination. If you found and fixed something, note what you changed and why.
120 
121Then ask: "Next?" or "Drop the next one." to keep the flow moving.
122 
123---
124 
125## Multi-Email Sequences
126 
127When the user is doing a full sequence, process one email at a time. After each:
1281. Output the spintaxed version
1292. Confirm combos are clean
1303. Prompt for the next email
131 
132Keep a mental count of which email in the sequence you're on (Email 1, Email 2, etc.) so you can reference them if the user asks.
133 
134---
135 
136## Flagging Issues
137 
138If you spot something in the original copy that's awkward or could be improved (independent of spintax), flag it briefly after the spintax output. For example:
139 
140> One small flag: "does QA differently" reads a bit awkward — consider swapping to `{handles|approaches|tackles}` instead.
141 
142Keep flags minimal. Only flag things that would actually hurt the email's performance. Don't rewrite their copy unless asked.
143 
144---
145 
146## Quick Reference
147 
148| Element | Example |
149|---|---|
150| Syntax | `{option1\|option2\|option3}` |
151| Greeting | `{Hey\|Hi}` |
152| Verb swap | `{help\|work with\|partner with}` |
153| Full sentence | `{Is this worth exploring?\|Want to give it a try?\|Open to a quick chat?}` |
154| Opt-out | `{If this isn't relevant, just reply and I won't follow up.\|Not relevant? Just reply and I won't reach out again.}` |
155| Never touch | `{{first_name}}`, `{{company_name}}`, `%signature%` |
156 
157---
158 
159## What to do next
160 
161**Launch the spintaxed copy** via `/smartlead-campaign-upload-public` — the spintax gets embedded in the `variants.yaml` body fields and renders per-recipient on send.
162 
163**Or wait:** skip this skill until your copy is final. Spintax complicates later debugging.
164 
165## Related skills
166 
167- `/campaign-copywriting` — writes the base copy this skill varies
168- `/smartlead-campaign-upload-public` — launches the spintaxed campaign
169 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 730
Checked
Source
growthenginenowoslawski/coldoutboundskills ↗
Creator
growthenginenowoslawski · 52 listings
View creator

Similar skills

See all →
SkillLead Magnet Buildercoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillEmail Newsletter Writercwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillSignal Based Cold Emailkami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Email Marketinghostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsAgentEmail Lifecycle Strategistmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillB2B Email Writercoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k GitHub stars

More from growthenginenowoslawski

SkillCold Email Automationgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiAutonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".★ 736 GitHub starsSkillCompany Decision-Maker Findergrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiUse the Blitz API to find decision-makers at specific companies when you already have a list of company domains. Best for SMB owner-finding, domain-to-people lookup, or supplementing Prospeo results. Outputs a CSV you can feed to the email-waterfall or directly to /cold-email-starter-kit for Smartlead upload. Use when your targeting is company-first (not title-first).★ 736 GitHub starsSkillCold Outreach Strategistgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiGenerates 15-25+ cold outbound campaign ideas with targeting strategies, AI personalization approaches, and value propositions. Use when planning campaign experiments for a client, given their website or business context.★ 736 GitHub starsSkillClay Signal Playbooksgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiIndex and shared harness for the 19 signal playbooks. Each playbook turns one buying signal (new in role, raised a round, hiring surge, pricing page, tech on website, ...) into one copy-ready sentence you can drop into a cold email. Every playbook ships three ways to run it: as a Claude skill, as a Clay table built through a browser harness, and as a Clay workflow built from the clay CLI. Use when someone says "personalize this list", "what signal should I use", "build the Clay column for X", or names any of the 19 signals.★ 736 GitHub starsSkillCompetitor Engager Findergrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiFind people actively engaging with competitor LinkedIn posts. Given a website URL, discovers competitors, fetches their company and employee posts, collects all commenters and reactors, and outputs a deduplicated CSV of engaged prospects. Use when someone wants to find leads from competitor engagement, build outreach lists from LinkedIn activity, or analyze who interacts with competitor content.★ 736 GitHub starsSkillEmail Deliverability Crisisgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiTriage playbook for when cold email deliverability breaks. Decision-tree guidance for "I landed in spam", "bounce rate spiked", "domain blacklisted", "inbox blocked in warmup", "reply rate dropped". Tells you what to check first, what to fix, and how long the fix takes. Pair with /email-deliverability-audit for diagnosis.★ 736 GitHub stars