CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/email-sequence/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This skill provides a comprehensive framework for email sequence design with good structural organization and useful timing/length benchmarks. Its main weaknesses are verbosity (too much general email marketing knowledge Claude already possesses), lack of concrete worked examples showing actual email copy, and missing validation steps in the workflow. The progressive disclosure structure is well-intentioned but undermined by inline content that duplicates referenced files.

Suggestions

Add at least one fully worked example showing a complete email (subject, preview, body, CTA) within a sequence context, rather than only empty templates.

Trim sections that teach Claude general knowledge it already has—e.g., 'Tone' advice, basic formatting rules, and the explanation of what preview text is. Focus on project-specific conventions and non-obvious patterns.

Add explicit validation checkpoints: e.g., 'Before finalizing, verify: no two consecutive emails have the same CTA type, timing gaps match the audience type, exit conditions are defined for every branch.'

Move the 'Email Types by Category' section entirely into the referenced email-types.md file to reduce main file length and avoid duplication with the reference.

DimensionReasoningScore

Conciseness

The skill contains useful information but is verbose in places—listing sequence types, email categories, and copy guidelines that Claude already knows well. Sections like 'Tone' advice ('Read it out loud—does it sound human?') and basic formatting tips add little value for Claude. However, the structured templates and specific timing recommendations earn their place.

2 / 3

Actionability

The skill provides structured output templates and specific timing/length recommendations, which are concrete. However, it lacks executable examples—no actual email copy examples, no complete sequence walkthrough showing a real email with subject/preview/body filled in. The output format section shows templates but they're empty placeholders rather than worked examples.

2 / 3

Workflow Clarity

The initial assessment checklist and sequence type overviews provide a reasonable workflow, and the output format gives structure. However, there are no validation checkpoints—no step to verify sequence coherence, check for email overlap with existing campaigns, or validate timing logic. The process from assessment to output is implied rather than explicitly sequenced.

2 / 3

Progressive Disclosure

The skill references several external files (references/sequence-templates.md, references/email-types.md, references/copy-guidelines.md, tools registry) which is good progressive disclosure structure. However, no bundle files were provided, so these references may be broken. The main file itself is quite long (~300 lines) with content that could be offloaded to the referenced files (e.g., the full Email Types by Category section duplicates what should be in email-types.md).

2 / 3

Total

8

/

12

Passed

Description

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 clear 'when to use' guidance. The disambiguation note is a nice touch that reduces conflict with related skills. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., writing email copy, setting cadence, defining segments).

Suggestions

Add more specific concrete actions beyond 'create or optimize,' such as 'write email copy, define send cadence, set up triggers, segment audiences, plan A/B tests' to improve specificity.

DimensionReasoningScore

Specificity

The description names the domain (email sequences/drip campaigns) and mentions some actions ('create or optimize'), but doesn't list multiple specific concrete actions like 'write subject lines, set timing intervals, define segmentation rules, draft email copy.'

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' equivalent with trigger terms listed). Also includes a helpful disambiguation note pointing to onboarding-cro 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

Very distinct niche focused specifically on email sequences and drip campaigns. The disambiguation note ('For in-app onboarding, see onboarding-cro') actively reduces conflict risk with related skills.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.