CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-sequences

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is email-sequences in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable guide: concrete structures, lengths, examples, and an output template, with detailed patterns and templates correctly split into two verified one-level-deep reference files. Its main gaps are minor: some generic email best practices Claude already knows, and workflows that include testing and measurement but lack explicit iteration/error-recovery loops.

Suggestions

Trim common-knowledge guidance (ALL CAPS, excessive punctuation, short paragraphs, mobile-first) from the Subject line and Body sections; Claude already knows these, and the detailed rules live in references/subject-line-patterns.md anyway.

Add an explicit iteration step to the workflows, e.g. after 'Measure' specify what to do when an email underperforms (rewrite subject line, adjust timing, or drop the email from the sequence).

In the 5 components section, replace the inline pattern list with two or three examples plus a pointer to references/subject-line-patterns.md to reduce duplication with the reference file.

DimensionReasoningScore

Conciseness

The body is efficient and imperative with no concept tutorials, but includes general knowledge Claude already has, e.g. "Avoid: ALL CAPS", "Excessive punctuation (!!!)", "Short paragraphs (2 to 3 lines)" and "Mobile-first formatting". It sits at 4 (minor over-explanation that could be trimmed) rather than 5, where every token would earn its place.

4 / 5

Actionability

Guidance is concrete and copy-paste ready: per-email timing structures ("Email 1 (immediate)... Email 5 (day 14)"), word-count ranges ("under 100 words", "30 to 50 characters"), concrete good/bad examples ("Your receipt for order #12345" vs "Newsletter #23"), and a full output format template. For an instruction-only skill this is fully actionable guidance covering the common cases.

5 / 5

Workflow Clarity

Both workflows ("For a new sequence" 1-9, "For a single broadcast" 1-7) are clearly sequenced and include checkpoints ("Test the sequence. Send to yourself. Read on mobile." and "Measure. Open rate, click rate..."). It falls short of 5 because there is no explicit error-recovery loop, e.g. what to change when a given email underperforms; validation is present but feedback-driven iteration is only implied.

4 / 5

Progressive Disclosure

The body is a well-organized overview (when to use / not use, framework, components, workflow, failure patterns, output format) and the two detail files are clearly signaled one level deep: "references/subject-line-patterns.md - Subject line patterns with examples for each sequence type" and "references/sequence-templates.md - Skeleton templates for the 6 sequence types". Both files exist, are substantive, and contain no nested references, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities in third person, exhaustively enumerates the email types it covers, and provides an explicit 'Use this skill when...' clause backed by a comprehensive list of natural trigger terms. The only weakness is minor overlap risk with general copywriting skills around newsletters and announcement emails, with no boundary guidance to disambiguate.

DimensionReasoningScore

Specificity

"Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails" lists multiple concrete actions (design, write, plan, set up) with comprehensive coverage of email types. It matches the 5 anchor rather than 4 because no meaningful capability gaps remain in the domain it claims.

5 / 5

Completeness

Explicitly answers both what ("Design and write email campaigns and sequences including...") and when ("Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns") with concrete trigger phrases. Matches the 5 anchor exactly; the 4 anchor requires a 'when' that could be more explicit, which does not apply here.

5 / 5

Trigger Term Quality

"Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back" comprehensively covers natural user phrasing including synonyms. Not 4 because virtually no common natural variation for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

"newsletter, email broadcast, launch email, announcement email" give it a clear email-copywriting niche with mostly distinct triggers, but these terms have minor overlap risk with general copywriting/content skills and the description offers no boundary disambiguation. It is mostly distinct (4) rather than a clear niche with minimal conflict (5).

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/email-sequences/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.