email-sequence
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.
78
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 ./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 description with excellent trigger term coverage and completeness, including a helpful disambiguation clause. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., writing copy, setting cadence, segmentation strategy). Overall, it would serve well for skill selection among many options.
Suggestions
Add more specific concrete actions beyond 'create or optimize,' such as 'write email copy, define send cadence, plan segmentation, structure A/B tests' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (email sequences/drip campaigns) and mentions actions like 'create or optimize,' but doesn't list multiple specific concrete actions (e.g., write subject lines, set timing intervals, segment audiences, A/B test). The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or optimize email sequences, drip campaigns, automated email flows, lifecycle email programs) and 'when' (explicit 'Use when' triggers with specific terms). Also includes a disambiguation note pointing to another skill for in-app onboarding. | 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.' These are all terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around email sequences and automation, with explicit disambiguation from the onboarding-cro skill for in-app onboarding. The trigger terms are specific to this domain and unlikely to conflict with other skills. | 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 skill with good progressive disclosure and reasonable coverage of email sequence design. Its main weaknesses are verbosity (explaining concepts Claude already knows like email copy tone and formatting basics) and lack of concrete, filled-in examples showing what a complete email sequence output should look like. Adding a worked example and trimming known-concept explanations would significantly improve it.
Suggestions
Add one complete worked example of a 3-4 email sequence with actual subject lines, preview text, and body copy filled in—not just empty template scaffolds.
Remove or drastically condense the Email Copy Guidelines section (structure, tone, formatting)—Claude already knows how to write conversational copy with short paragraphs and active voice.
Add a validation step to the workflow: after drafting the sequence, review for coherence (does each email logically follow the previous?), check for conflicts with other active sequences, and verify exit conditions are properly defined.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose in places—explaining basic concepts like email structure (hook, context, value, CTA) and tone guidelines (active voice, conversational) that Claude already knows. The sequence type overviews and email type categories add value but could be tighter. | 2 / 3 |
Actionability | Provides structured templates and specific timing recommendations, but lacks executable code/commands or concrete email copy examples. The output format templates are helpful but are empty scaffolds rather than filled-in examples showing what good output looks like. | 2 / 3 |
Workflow Clarity | The sequence types provide clear step-by-step progressions with timing, and the initial assessment section establishes a discovery workflow. However, there are no validation checkpoints—no guidance on reviewing sequence coherence, checking for conflicts with existing emails, or verifying exit conditions before finalizing. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with clear one-level-deep references to sequence-templates.md, email-types.md, copy-guidelines.md, and tool integration guides. The main file serves as a well-organized overview with appropriate signposting to detailed materials. | 3 / 3 |
Total | 9 / 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 | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- 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.