email-sequences
boringmarketer/boring-marketing-skillsMarketing & growthBusiness & productivity
email-sequences is a skill in boringmarketer/boring-marketing-skills, last changed 16 Nov 2026. It can run shell commands, reach the network, name web addresses and bundle scripts — read the findings before installing.
Build email (and text) sequences that turn leads into customers, including welcome, nurture, conversion, launch, re-engagement and post-purchase, plus local-service follow-ups (quote and treatment-plan follow-up, appointment reminders, review ask, seasonal reminder, win-back, missed-call text-back) and a cold outbound mode for prospecting sequences. Covers every reasonable reading of the request and leads with the revenue lever. Checks SPF, DKIM and DMARC on the real sending domain and can push drafts to Kit or Beehiiv. Use when a lead magnet needs a welcome sequence, an offer needs a sales sequence, quotes or treatment plans aren't closing, a list needs re-engaging, or an agency needs a cold email sequence.
At a glance
What it can touch
How much a skill can do, not whether it is risky.
Pattern check
Nothing flagged
That isn't proof the skill is harmless.
Commit bd5aaed · 20 Nov 2026
How the check worksPattern check: nothing flagged
That isn't proof the skill is harmless.
QAI Index
We rate every listed skill the same way, from 0 to 100.
A guide to compare by, not a verdict on the skill.
How it's scoredGet an email when its check changes.
Keep it with the other skills you use, installed with one command.
Install
Sign in to see how to install it
Free with Google or an email link, no password needed. Then pick your agent and copy its steps.
What it can touch
Sign in to see the file and line behind each one
The summary at the top stays open to everyone. Signing in is free, with Google or an email link.
Pattern check
Pattern check: nothing flagged · commit bd5aaed · 20 Nov 2026
We checked every text file in this skill, at commit bd5aaed on 20 Nov 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.
How the check worksReport an incorrect finding
Outside links we did not follow
- https://api.kit.com
- https://api.kit.com/v4/sequences
- https://api.kit.com/v4/sequences/
- https://api.beehiiv.com/v2
- https://api.resend.com
- https://app.loops.so/api
Format check
Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.
Agent Skills specPasses with warnings
The format our Agent Skills docs set out, held to the strictest version of each rule among the agents we check.
- Warning
The frontmatter uses [ ] or { } values. Most agents accept them, but strict validators reject the file. F4
Fix: Write lists as "- item" lines and maps as indented key: value lines, without anchors or tags.
- Warning
Fields outside the spec: when_to_use (read by Claude Code) and argument-hint (read by Claude Code and VS Code). Uploads to the Claude apps and API, and strict validators, reject the file; most agents ignore these fields. O1
Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.
- Warning
metadata values should be text; boring (a map) is not. Some readers turn them into text; others may not. O4
Fix: Quote each value, for example version: "1.0".
- Warning
The body is about 6,078 tokens (approx.); the spec suggests under 5,000. B2
Fix: Move detail into reference files that the agent reads only when needed.
- Note
The first sentence of the description is 351 characters. Agents shorten long descriptions, so lead with the main job. D8
Fix: Start with one short sentence that names the job.
- Note
There is no license field, so readers can't tell whether they may reuse the skill. O2
Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.
- Note
Reference files over 100 lines with no table of contents at the top: references/cold-outbound.md (170 lines), references/deliverability-2026.md (107 lines), references/esp-apis.md (135 lines) and references/local-templates.md (203 lines). B5
Fix: Add a short list of the sections at the top of each.
- Note
Line 200 has dated wording ("since Oct 2024"), which goes stale. B8
Fix: Describe the current way, and move old patterns into their own clearly marked section.
- Warning
Claude CodePasses
Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.
- Note
The first sentence of the description is 351 characters. Agents shorten long descriptions, so lead with the main job. D8
Fix: Start with one short sentence that names the job.
- Note
The body is about 6,078 tokens (approx.); the spec suggests under 5,000. After compaction Claude Code keeps only the first 5,000 tokens of a skill. B2
Fix: Move detail into reference files that the agent reads only when needed.
- Note
Reference files over 100 lines with no table of contents at the top: references/cold-outbound.md (170 lines), references/deliverability-2026.md (107 lines), references/esp-apis.md (135 lines) and references/local-templates.md (203 lines). B5
Fix: Add a short list of the sections at the top of each.
- Note
Line 200 has dated wording ("since Oct 2024"), which goes stale. B8
Fix: Describe the current way, and move old patterns into their own clearly marked section.
- Note
Claude apps & API uploadFails
Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.
- Error
Upload and packaging fail on fields outside the spec: when_to_use and argument-hint. O1
Fix: Delete them, and keep your own data under metadata as text values.
- Note
The description is 717 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4
Fix: If the claude.ai upload refuses it, trim the description to 200 characters.
- Note
metadata values should be text; boring (a map) is not. The spec defines metadata as text to text. O4
Fix: Quote each value, for example version: "1.0".
- Note
The body is about 6,078 tokens (approx.); the spec suggests under 5,000. Anthropic's guidance says the same. B2
Fix: Move detail into reference files that the agent reads only when needed.
- Note
Reference files over 100 lines with no table of contents at the top: references/cold-outbound.md (170 lines), references/deliverability-2026.md (107 lines), references/esp-apis.md (135 lines) and references/local-templates.md (203 lines). B5
Fix: Add a short list of the sections at the top of each.
- Note
Line 200 has dated wording ("since Oct 2024"), which goes stale. B8
Fix: Describe the current way, and move old patterns into their own clearly marked section.
- Error
OpenAI (Codex & API)Passes with warnings
Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.
- Warning
Fields outside the spec: when_to_use and argument-hint. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1
Fix: Delete them, or move your own data under metadata as text values.
- Warning
metadata values should be text; boring (a map) is not. OpenAI's upload follows the spec's text-to-text rule. O4
Fix: Quote each value, for example version: "1.0".
- Note
The first sentence of the description is 351 characters. Agents shorten long descriptions, so lead with the main job. D8
Fix: Start with one short sentence that names the job.
- Warning
VS Code & CopilotPasses
VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.
- Note
VS Code ignores fields it doesn't support: when_to_use. O1
Fix: Delete them unless another agent you target reads them.
- Note
SKILL.md
Files
6 files
Changelog
Newest first: each commit that changed its folder on GitHub, and each change to its listing here.
- Listed on QAI
- Updated: 4.1.1: sharper visual check for ad creative (brand name, offer line, … (7c6678c (opens in a new tab))
- Updated: Boring Marketing Skills 4.1.0 (3f2b695 (opens in a new tab))
- Updated: Sharper deliverables: finished work first, claim checks, cold outboun… (2e2251f (opens in a new tab))
- Updated: Link the Boring Marketing community (3f1feb9 (opens in a new tab))
- Updated: Boring Marketing Skills 4.0.0 (42f2599 (opens in a new tab))
QAI Index badge
Show this skill's QAI Index in a README or on a website. It links back to this page and changes when we refresh the catalog.
[](https://qai.io/skills/boringmarketer/boring-marketing-skills/email-sequences)More from boringmarketer/boring-marketing-skills
Other Marketing & growth skills
Same category, most repo stars first.