A guide for planning a series of automated or scheduled emails, such as welcome, onboarding, sales, educational, or re-engagement messages. A lifecycle email program sends messages based on a person's stage or actions.

Use it to design welcome flows, lead-nurture sequences, post-purchase emails, event-triggered messages, and other multi-email campaigns.

It helps ensure each email has a clear purpose and moves the reader toward the intended next step.

emails — Skill for Claude Code by Cesarjoquin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Cesarjoquin/Marketing-Skills --skill emails

Clone the repo

git clone --depth 1 https://github.com/Cesarjoquin/Marketing-Skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 45 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cesarjoquin/marketing-skills/emails/github.svg)](https://agentmods.dev/skills/cesarjoquin/marketing-skills/emails)

Your own site

<a href="https://agentmods.dev/skills/cesarjoquin/marketing-skills/emails"><img src="https://agentmods.dev/badge/skills/cesarjoquin/marketing-skills/emails/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cesarjoquin/marketing-skills/emails"><img src="https://agentmods.dev/badge/skills/cesarjoquin/marketing-skills/emails.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,196 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00126	$0.02196
Opus 5	$0.00063	$0.01098
Sonnet 5	$0.00025	$0.00439
Haiku 4.5	$0.00013	$0.00220

Measured 9d ago against content hash 1fbd54df4c59, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

emails scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to emails — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/emails/SKILL.md · 312 lines

How it starts

The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before creating a sequence, understand:

Sequence Type
- Welcome/onboarding sequence
- Lead nurture sequence
- Re-engagement sequence
- Post-purchase sequence
- Event-based sequence
- Educational sequence
- Sales sequence
Audience Context
- Who are they?
- What triggered them into this sequence?
- What do they already know/believe?
- What's their current relationship with you?
Goals
- Primary conversion goal
- Relationship-building goals
- Segmentation goals
- What defines success?

Core Principles

1. One Email, One Job

Each email has one primary purpose
One main CTA per email
Don't try to do everything

2. Value Before Ask

Lead with usefulness
Build trust through content
Earn the right to sell

3. Relevance Over Volume

Fewer, better emails win
Segment for relevance
Quality > frequency

4. Clear Path Forward

Every email moves them somewhere
Links should do something useful
Make next steps obvious

Email Sequence Strategy

Sequence Length

Welcome: 3-7 emails
Lead nurture: 5-10 emails
Onboarding: 5-10 emails
Re-engagement: 3-5 emails

Depends on:

Sales cycle length
Product complexity
Relationship stage

Timing/Delays

Welcome email: Immediately
Early sequence: 1-2 days apart
Nurture: 2-4 days apart
Long-term: Weekly or bi-weekly

Consider:

B2B: Avoid weekends
B2C: Test weekends
Time zones: Send at local time

Read the full file on GitHub · 312 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 312 lines · 126 tokens per session scan A 1fbd54df4c59

Subscribe to this mod's changes

emails is a skill published in the GitHub repository Cesarjoquin/Marketing-Skills (185 stars, last pushed 5d ago), licensed MIT. It adds 126 tokens to every session and 2,196 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to emails, differing in 0 lines, and is treated as a copy.

Marketing and SEO agent ai ai-agent ai-skills marketing-agent skills-agent

skillpack-creator

Create a reusable SkillPack from a successful completed task. Use when the user wants to convert a one-off research, coding, analysis, or content workflow into a distributable local SkillPack with skillpack.json, local skills under skills/, starter prompts, start scripts, and an optional zip package.

CreminiAI/skillpack · 67 tokens

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

CreminiAI/skillpack · 64 tokens

emails