CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emails

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," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.

Quality

92%

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

86%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 strong, highly actionable skill body: concrete sequence blueprints, timings, and a copy-paste output format, with excellent reference routing and a verified one-level-deep bundle structure. Its main weaknesses are mild token waste on generic copywriting principles and tone advice Claude already knows, and a workflow that is ordered by implication rather than by one explicit step sequence with a post-draft validation checkpoint.

Suggestions

Cut or compress the 'Core Principles' section and the generic Tone/Formatting bullets (e.g., 'Don't try to do everything', 'Read it out loud. Does it sound like a person?') — they restate copywriting knowledge Claude already has and the copy-guidelines reference covers structure and tone in detail.

Add an explicit ordered workflow (assess context → route reference → design sequence → draft → output) with a final validation step, e.g., 'Before delivering, check every subject line, preview text, and body against the AI-tells blacklist above.'

Trim the per-email 'Key emails' lists under Sequence Types Overview (they duplicate sequence-templates.md) down to length/goal/timing, leaving per-email detail to the reference.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics (email counts, day-by-day timing, word counts, output templates), but includes generic copywriting knowledge Claude already has — the 'Core Principles' aphorisms ('Don't try to do everything', 'Quality > frequency'), tone/formatting basics ('Read it out loud. Does it sound like a person?'), and sequence-type summaries that partially duplicate sequence-templates.md. These are minor over-explanation instances that could be trimmed, matching anchor 4 rather than anchor 3's 'some unnecessary explanation'.

4 / 5

Actionability

Fully concrete guidance for an instruction-only skill: routing table mapping user intent to reference files, exact sequence lengths and delays ('Welcome: 5-7 emails over 12-14 days', 'Quick win (day 1-2)'), literal subject-line patterns ('[First name], your [thing] is ready'), word-count ranges per email type, a copy-paste output template with named fields, and a tool integration table. Specific examples cover the common sequence cases, matching anchor 5.

5 / 5

Workflow Clarity

A clear sequence is conveyed through explicit ordering cues — 'Check for product marketing context first', 'Load the matching reference before drafting or auditing', 'Before creating a sequence, understand' — followed by the structured output format, plus a pre-draft checkpoint (verify the Learnings section so tested angles aren't re-proposed). It falls short of anchor 5 because the sequence is scattered across sections rather than stated as one ordered workflow, and there is no post-draft validation step (e.g., auditing drafted emails against the AI-tells blacklist it defines).

4 / 5

Progressive Disclosure

A routing table at the top maps each user intent to one of three real, one-level-deep reference files (verified: references/sequence-templates.md, email-types.md, copy-guidelines.md exist and contain no further nested references), each with a 'Covers' column, reinforced by inline 'For detailed templates: See references/...' pointers at section ends. The split is appropriate: ~290-line overview with planning numbers in SKILL.md, ~800 lines of detail in the references. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

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.

An exemplary description: concrete third-person capabilities, comprehensive natural trigger phrases, explicit 'use when' guidance, and explicit boundary routing to adjacent skills. The only improvement space is mentioning the audit and individual-email-copy capabilities the body actually delivers.

DimensionReasoningScore

Specificity

It states several concrete actions — 'create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program' plus a distinctive behavior ('Emails avoid AI tells like "it's not X, it's Y" reveals... fake "Re:" subject lines') — all in third person. It stops short of anchor 5 because the body covers capabilities the description omits (lifecycle email audits, writing individual emails), leaving minor gaps in coverage per anchor 4; it exceeds anchor 3, which expects only 1-2 actions.

4 / 5

Completeness

It explicitly answers 'when' three ways — 'When the user wants to create or optimize...,' 'Also use when the user mentions [14 trigger phrases],' 'Use this for any multi-email automated flow' — and 'what' through the named artifacts (email sequence, drip campaign, automated email flow, lifecycle email program) and the AI-tells behavior. Both are present with concrete trigger phrases, exactly matching anchor 5's exemplar.

5 / 5

Trigger Term Quality

Fourteen quoted natural phrases users would actually say — 'email sequence,' 'drip campaign,' 'nurture sequence,' 'onboarding emails,' 'welcome sequence,' 're-engagement emails,' 'email automation,' 'lifecycle emails,' 'trigger-based emails,' 'email funnel,' 'email workflow,' 'what emails should I send,' 'welcome series,' 'email cadence' — plus a plain-English catch-all ('Use this for any multi-email automated flow'). Synonym coverage is comprehensive for this domain (file extensions are not applicable), matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (multi-email automated flows) and explicitly disambiguates the two nearest competitors — 'For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding.' — minimizing wrong-skill triggering, matching anchor 5's clear niche with distinct triggers and 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/emails/SKILL.md

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.