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

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-structured, actionable skill body with a clear six-type framework, concrete numeric guidance, and a copy-paste output format. The workflows include test and measure steps but lack explicit error-recovery loops, and a small reference-annotation mismatch (6 vs. 5 sequence types) slightly mars navigation.

Suggestions

Trim commonly-known email basics (e.g. 'Short paragraphs (2 to 3 lines)', 'Mobile-first formatting') to tighten conciseness while keeping the non-obvious numbers and rules.

Add an explicit feedback loop to the workflows, e.g. 'if open rate is low after the first sends, rewrite the subject using a different pattern from references/subject-line-patterns.md and re-test'.

Fix the reference mismatch: the body says 'Skeleton templates for the 6 sequence types' but sequence-templates.md covers 5 — align the count or add a broadcast template.

DimensionReasoningScore

Conciseness

The body is mostly lean, domain-specific guidance ('Email 2 (day 1 or 2): First-value step. Help them get to a quick win') but includes a few email basics Claude already knows, such as 'Short paragraphs (2 to 3 lines)' and 'Mobile-first formatting', that could be trimmed. It sits at anchor 4 rather than 5 because a handful of tokens do not earn their place, and above anchor 3 because there is no padded conceptual explaining.

4 / 5

Actionability

Guidance is concrete and executable throughout: per-email timing ('Email 4 (day 8)'), character budgets ('Length: 30 to 50 characters'), word counts ('Welcome and transactional: under 100 words'), example subject lines ('Your week 1 progress: 3 of 5 steps done'), and a copy-paste output template ('# Sequence: [Name] ... **Subject:** [text]'). Specific examples cover the common cases, matching the anchor-5 pattern rather than anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Two clearly numbered workflows ('1. Define the trigger ... 9. Measure. Open rate, click rate, completion rate') with explicit test steps ('Test the sequence. Send to yourself. Read on mobile.'). It is not anchor 5 because there are no error-recovery feedback loops, e.g. no guidance on what to change when open rate or completion rate is low.

4 / 5

Progressive Disclosure

Good structure: framework and components stay inline while details live in two real, well-signaled, one-level-deep reference files. The body promises 'Skeleton templates for the 6 sequence types' but sequence-templates.md actually covers 'the 5 standard sequence types' — a small navigation/accuracy mismatch that keeps it below the anchor-5 'easy navigation' bar.

4 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: concrete capabilities, explicit use-when guidance, and an exhaustive list of natural trigger terms with synonyms, all scoped tightly to the email-campaign niche. It matches the rubric's good overall examples in structure and quality.

DimensionReasoningScore

Specificity

'Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails' plus 'write email copy, plan an email sequence, design an onboarding drip, set up lifecycle email campaigns' lists multiple concrete actions with comprehensive coverage of the domain. Anchor 5 fits; anchor 4 would require coverage gaps, and none are present.

5 / 5

Completeness

Explicit what ('Design and write email campaigns and sequences including...') and explicit when ('Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip') with concrete trigger phrases — the anchor-5 example pattern exactly. Not anchor 4, because the 'when' clause is fully explicit rather than merely present or under-specified.

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' — fourteen natural trigger terms with synonyms (drip campaign/nurture sequence, win-back/re-engagement) and no file extensions relevant to this domain. Comprehensive coverage matches anchor 5, not anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

A clear email-channel niche with distinct, email-scoped triggers ('onboarding email', 'email broadcast', 'abandoned cart', 'transactional email') that adjacent copywriting or content skills would not claim. Minimal conflict risk matches anchor 5; anchor 4 would require overlap with closely related skills, which the email-specific scoping avoids.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

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.