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.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, information-dense skill body: the strategy heuristics, sequence blueprints, and output template are concrete and actionable, and reference files are real, well-labeled, and one level deep. The main gaps are verbatim duplication between the inline copy-guidelines section and its reference file, an undeveloped Metrics Plan section, and the absence of an explicit confirm-before-drafting checkpoint.

Suggestions

Replace the inline 'Email Copy Guidelines' Structure/Formatting lists (which duplicate references/copy-guidelines.md verbatim) with a two-line summary plus the existing reference link, keeping only the copy-length and CTA specifics that are unique to SKILL.md.

Flesh out the Metrics Plan section with the actual metrics and benchmark ranges to measure (e.g., open rate, click rate, unsubscribe rate per sequence type), or point to a metrics reference — currently it promises benchmarks but gives none.

Add an explicit checkpoint after the Initial Assessment (e.g., confirm the sequence type, goal, and audience assumptions with the user before drafting the full sequence) to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

The body is lean, bullet-driven domain knowledge Claude does not already have (sequence lengths, send timing, subject-line patterns, copy length ranges) with essentially no padding or explanation of known concepts. It falls short of 5 because the 'Email Copy Guidelines' Structure and Formatting lists duplicate references/copy-guidelines.md almost verbatim, and the 'Sequence Types Overview' key-email breakdowns overlap references/sequence-templates.md.

4 / 5

Actionability

Concrete, executable guidance throughout: specific numbers ('5-7 emails over 12-14 days,' '40-60 characters ideal,' '50-125 words for transactional'), named subject-line patterns with examples, and a fill-in Output Format template. Not a 5 because the 'Metrics Plan' section says 'What to measure and benchmarks' but supplies no actual metrics or benchmark values, leaving that step underspecified.

4 / 5

Workflow Clarity

A coherent, ordered process is present: check the product-marketing context file first, run the Initial Assessment questions, apply strategy by sequence type, then produce output in the defined format. It is not a 5 because there is no explicit checkpoint (e.g., confirm the chosen sequence type and goal with the user before drafting) — validation between steps is implicit rather than stated.

4 / 5

Progressive Disclosure

Good structure with three well-signaled, one-level-deep references ('For detailed templates: See references/sequence-templates.md,' etc.), all of which exist and match their described content. It falls short of 5 because content that also lives in the references (copy guidelines, sequence-type email breakdowns) is substantially inlined in SKILL.md rather than cleanly split, creating mild duplication.

4 / 5

Total

16

/

20

Passed

Description

90%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 with an explicit 'Use when' trigger clause, comprehensive natural-language synonyms, and proactive disambiguation against the adjacent onboarding skill. The only weakness is that the capability statement is limited to two verbs (create/optimize) without enumerating more specific actions.

DimensionReasoningScore

Specificity

The description names the domain and exactly two concrete actions — "create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program" — but offers no further specific capabilities, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several distinct actions (e.g., writing copy, planning timing, choosing send tools).

3 / 5

Completeness

Both halves are explicit: 'when' via "When the user wants to create or optimize..." and "Also use when the user mentions [eight concrete trigger phrases]," and 'what' via create/optimize of sequences, flows, and lifecycle programs. It clearly exceeds level 4, where the 'when' would be less explicit or specific.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and variations: "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," and "lifecycle emails." This matches the level-5 anchor for comprehensive natural-term coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear email-sequence niche with distinct trigger phrases, and it explicitly routes the nearest overlap away: "For in-app onboarding, see onboarding-cro." This matches the level-5 anchor (clear niche, distinct triggers, minimal conflict risk) rather than level 4's 'minor overlap risk.'

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 6 suspicious

Warning

Total

14

/

16

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.