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," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
83
Quality
80%
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 ./config/claude/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 skill description with excellent trigger term coverage and clear disambiguation from related skills. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'create or optimize.' The explicit listing of trigger terms and cross-reference to related skills demonstrates good skill design practices.
Suggestions
Add 2-3 specific concrete actions to strengthen specificity, e.g., 'Creates email sequences with optimized subject lines, timing, and segmentation logic'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (email sequences/drip campaigns) and mentions actions like 'create or optimize,' but doesn't list specific concrete actions like 'write subject lines, set timing delays, segment audiences, A/B test content.' | 2 / 3 |
Completeness | Clearly answers both what (create/optimize email sequences and drip campaigns) and when (explicit 'Use when' equivalent with comprehensive trigger terms). Also includes helpful disambiguation pointing to another skill for in-app onboarding. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'email sequence,' 'drip campaign,' 'nurture sequence,' 'onboarding emails,' 'welcome sequence,' 're-engagement emails,' 'email automation,' 'lifecycle emails' - these are all terms users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on email sequences and automation. The explicit disambiguation ('For in-app onboarding, see onboarding-cro') shows awareness of potential conflicts and actively prevents them. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 skill with excellent progressive disclosure and clear workflow sequencing. The main weaknesses are moderate verbosity (explaining concepts Claude knows) and lack of concrete, copy-paste-ready email examples - it tells Claude what to write rather than showing complete examples. The reference architecture is strong but the core content could be more actionable.
Suggestions
Remove the opening persona statement ('You are an expert...') and trim explanatory content about basic email marketing concepts Claude already understands
Add 1-2 complete, copy-paste-ready email examples with full subject line, preview text, and body copy rather than just describing structure
Replace the output format templates with a concrete filled-in example showing what a complete sequence deliverable looks like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('You are an expert...') and explanatory content Claude already knows (basic email marketing concepts). The lists are comprehensive but could be tighter in places. | 2 / 3 |
Actionability | Provides good structural templates and timing guidelines, but lacks executable code examples for email platform integrations. The output format templates are helpful but the actual email copy examples are missing - it describes what to include rather than showing complete examples. | 2 / 3 |
Workflow Clarity | Clear sequencing with explicit timing, triggers, and exit conditions. The sequence types have well-defined steps with day-by-day progression. The output format section provides a clear checklist structure for deliverables. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview in main file and well-signaled one-level-deep references to detailed templates (references/sequence-templates.md, references/email-types.md, references/copy-guidelines.md). Tool integrations appropriately linked to external guides. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
355d067
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.