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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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-structured, actionable skill body with effective progressive disclosure into verified reference files. It could be tightened by trimming the role preamble and abstract principles, and by adding explicit verification checkpoints.

Suggestions

Remove or condense the "You are an expert in email marketing…" role preamble and convert abstract Core Principles (e.g. "Lead with usefulness") into concrete do/don't rules to lift conciseness and actionability.

Add an explicit validation/verification step before the Output Format—e.g., "Confirm each email has one CTA, a send timing, and serves the sequence goal"—to give the workflow a feedback checkpoint.

De-duplicate the body's per-sequence "Key emails" lists against references/sequence-templates.md so the body stays a true overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet-structured guidance with no padding about concepts Claude already knows, but the role preamble ("You are an expert in email marketing and automation…") and abstract Core Principles add minor over-explanation.	4 / 5
Actionability	Concrete email counts, day-by-day timing, subject-line patterns with examples, and a copy-paste Output Format template are highly actionable, but Core Principles like "Lead with usefulness" and "Build trust through content" remain abstract.	4 / 5
Workflow Clarity	A clear sequence runs from Initial Assessment through Strategy, Types, Copy, and Output, with assessment checklists and a Metrics Plan, but explicit validation/feedback-loop checkpoints are absent.	4 / 5
Progressive Disclosure	The body is a well-organized overview that splits detail into three real, one-level-deep reference files (sequence-templates.md, email-types.md, copy-guidelines.md), each clearly signaled with "See [references/…]" links.	5 / 5
	Total	17 / 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 that clearly states capability, triggers, and scope with comprehensive natural-language keywords and explicit disambiguation. The only minor gap is limited action-verb variety (create/optimize).

Dimension	Reasoning	Score
Specificity	"create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program" names concrete actions applied across multiple specific deliverable types, though only two action verbs (create, optimize) are used.	4 / 5
Completeness	It explicitly answers "what" (create or optimize sequences/flows/programs) and "when" ("When the user wants to…" and "Also use when the user mentions…") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," and "lifecycle emails" give comprehensive coverage of natural synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	A clear email-automation niche with distinct triggers, plus explicit disambiguation ("For in-app onboarding, see onboarding-cro"), keeps conflict risk minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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: TheCraigHewitt/seomachine
Path: .claude/skills/email-sequence/SKILL.md
Commit: e818d5e

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.