When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/email-sequence/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and explicit boundary-setting against related skills. The main weakness is that the 'what' portion is somewhat light on specific concrete actions—it says 'create or optimize' but doesn't enumerate the specific deliverables or capabilities (e.g., writing email copy, setting cadence timing, defining segments). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'Designs email sequence structure, writes email copy, sets send timing and cadence, defines audience segments and trigger conditions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (email sequences, drip campaigns, lifecycle emails) and mentions 'create or optimize' as actions, but doesn't list multiple specific concrete actions like 'write subject lines, set timing intervals, define segmentation rules, map trigger conditions.' | 2 / 3 |
Completeness | Clearly answers both 'what' (create or optimize email sequences, drip campaigns, automated email flows, lifecycle email programs) and 'when' with an explicit 'Use when' clause and extensive trigger term list. Also includes helpful boundary guidance distinguishing from cold-email and onboarding-cro skills. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'email sequence,' 'drip campaign,' 'nurture sequence,' 'onboarding emails,' 'welcome sequence,' 're-engagement emails,' 'email automation,' 'lifecycle emails,' 'email funnel,' 'email cadence,' 'what emails should I send,' and more. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carves out a distinct niche for multi-email automated flows and explicitly differentiates from related skills (cold-email for cold outreach, onboarding-cro for in-app onboarding), which significantly reduces conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured email sequence design skill with strong progressive disclosure and reasonable organization. Its main weaknesses are the lack of concrete, filled-in examples (showing actual email copy for at least one sequence) and some verbosity in areas where Claude already has competence (basic copywriting principles, formatting advice). Adding a complete worked example and trimming obvious guidance would significantly improve it.
Suggestions
Add one complete worked example showing a 3-email welcome sequence with actual subject lines, preview text, and body copy filled in—not just the structural template.
Trim the 'Core Principles' and 'Email Copy Guidelines' sections significantly—Claude already knows basic copywriting principles like 'short paragraphs' and 'active voice.' Focus only on email-specific insights that are non-obvious.
Add a validation/review checkpoint in the workflow, such as 'Review the full sequence for consistency in tone, escalating CTAs, and proper timing before presenting to user.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content Claude already knows (email formatting basics, tone advice like 'read it out loud', general copy structure). The sequence type overviews are useful but could be more compressed. Some sections like 'Core Principles' state obvious marketing truisms. | 2 / 3 |
Actionability | Provides concrete sequence structures with specific timing and email purposes, plus output format templates. However, it lacks actual email copy examples—the templates are structural outlines rather than executable content. The output format section gives a useful schema but no filled-in example to demonstrate quality. | 2 / 3 |
Workflow Clarity | The initial assessment section provides a clear discovery workflow, and sequence types give ordered steps with timing. However, there's no validation or feedback loop—no guidance on reviewing sequence performance, iterating based on metrics, or checkpoints before launching. For a multi-step creative process, there should be review/approval steps. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with clear references to separate files: sequence-templates.md, email-types.md, copy-guidelines.md, and tool integration guides. All references are one level deep and clearly signaled with descriptive labels. The main file serves as a solid overview without being monolithic. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
2c7c108
Table of Contents
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.