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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized, actionable skill body with a real validation checkpoint. Its main weakness is progressive disclosure: the sole reference contains broken nested references and the Core Principles section is only a pointer with no inline substance.

Suggestions

Fix or remove the dead references inside email-sequence-playbook.md (references/copy-guidelines.md, email-types.md, sequence-templates.md) — either ship those files or delete the links.

Add a brief inline summary of the Core Principles in SKILL.md instead of leaving the section as only '→ See references/... for details'.

Tighten the redundancy between 'Initial Assessment' and 'Task-Specific Questions' (e.g., drop the duplicate trigger/goal/knowledge questions).

DimensionReasoningScore

Conciseness

Efficient, well-sectioned body with no concept padding and pointers like '→ See references/...'; minor redundancy between 'Initial Assessment' and 'Task-Specific Questions' keeps it just below lean.

4 / 5

Actionability

Concrete output-format templates and an executable analyzer invocation backed by a real script provide mostly executable guidance, though the per-email blocks are fill-in skeletons rather than complete copy-paste examples.

4 / 5

Workflow Clarity

Clear sequence from initial assessment through running the analyzer and attaching the score, with an explicit checkpoint ('fix anything it flags below 70'); not a full validate→fix→retry loop with recovery detail.

4 / 5

Progressive Disclosure

Body points to one real reference and a script one level deep, but the playbook itself references three files (copy-guidelines.md, email-types.md, sequence-templates.md) that do not exist, and the Core Principles section is a bare pointer with no inline summary.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description: clear what/when, rich natural trigger terms, and explicit boundary guidance to a related skill. Only mild weakness is that the action verbs are limited to 'create or optimize.'

DimensionReasoningScore

Specificity

Names the domain and concrete actions 'create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program' across four object types, but relies on only two verbs so coverage is not fully comprehensive.

4 / 5

Completeness

Explicitly answers both what ('create or optimize an email sequence...') and when ('Also use when the user mentions...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural synonyms users would say — 'email sequence,' 'drip campaign,' 'nurture sequence,' 'onboarding emails,' 'welcome sequence,' 're-engagement emails,' 'email automation,' 'lifecycle emails' — matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

Clear email-sequence niche with distinct triggers and an explicit boundary deferral ('For in-app onboarding, see onboarding-cro'), giving minimal conflict risk.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.