CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-sequence-designer

Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-specialist; not for writing each email's copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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, highly actionable skill body with a genuinely clear workflow: ordered instructions, a done-when checklist, decision gates, and feedback loops for the risky send operations, plus a properly split one-level-deep reference bundle. Its main weakness is token efficiency — the same scope-exclusion statements are repeated across at least five sections, adding recurring redundancy.

Suggestions

State the four scope exclusions (win-back, preference-center, copywriting, EQS) once in the Scope Guard and drop their verbatim restatements from the intro paragraph, instructions 2 and 7, and Next Best Skill — a short pointer to the Scope Guard suffices where routing context is needed.

Move the "Zero-dependency flow activation (when Resend is the ESP)" protocol detail into references/send-control.md, keeping only a one-line create-vs-send rule in the body, since send-control.md already specifies the create/send separation and receipt semantics.

Merge the Reference Materials and Next Best Skill sections into a single routing table (skill → purpose → when to route), eliminating the duplicate one-line descriptions of reactivation-specialist and preference-frequency-manager that currently appear in both.

DimensionReasoningScore

Conciseness

The nine instructions, contract, and decision gates are dense and non-obvious, but the same boundary exclusions (win-back → reactivation-specialist, preference-center → preference-frequency-manager, copy → email-creative-builder, EQS → email-quality-auditor) are restated nearly verbatim in the intro, instructions 2 and 7, the scope guard, Reference Materials, and Next Best Skill — recurring padding that could be consolidated to one canonical statement.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact typed-profile weights ("0.15 / 0.30 / 0.15 / 0.20"), concrete scoring rules ("Pass=10 / Partial=5 / Fail=0, report the 0–100 N dimension score"), specific binding fields (`segment_ref`, `definition_version`, `definition_hash`), an exact save path, and three Quick Start templates covering the common cases — matching the anchor-5 standard of specific examples covering common cases.

5 / 5

Workflow Clarity

The nine numbered instructions give a clear sequence (profile → inventory → design → bind → goal logic → governance → sunset → bind sends → score) with explicit validation: a "Done when" checklist, Stop/Continue decision gates with concrete examples, consent-snapshot replay and preview-before-send checkpoints for the batch send operation, and a feedback loop ("if it returns BLOCK on N1, route back here to add the opt-out path rather than chaining onward").

5 / 5

Progressive Disclosure

The bundle's one reference file (references/send-control.md) is real, one level deep, and clearly signaled with purpose in the Reference Materials section; however the body's "Zero-dependency flow activation" paragraph partially duplicates send-control.md content inline rather than deferring it, which is a minor organization gap consistent with anchor 4.

4 / 5

Total

17

/

20

Passed

Description

92%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: explicit what/when with verbatim natural trigger phrases, comprehensive and concrete capability enumeration, and unusually good conflict-risk handling through explicit negative boundaries naming the sibling skills to use instead. The only gap is a few missing natural synonyms (e.g., drip campaign, nurture sequence).

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — flow types ("welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound"), per-flow components ("trigger, step timing, branch/exit conditions, goal"), governance items ("send caps, quiet hours, fatigue guardrail"), "a sunset path, and a SEND N-dimension score" — comprehensive coverage with no gaps, matching the anchor-5 example rather than the minor-gaps anchor 4.

5 / 5

Completeness

It explicitly answers both questions: what ("produces general lifecycle automation flows ... with trigger, step timing, branch/exit conditions, goal, frequency governance ... a sunset path, and a SEND N-dimension score") and when ("Use when the user asks to 'design a welcome flow', 'set up an abandoned-cart sequence' ..."), with concrete quoted trigger phrases — the exact anchor-5 pattern.

5 / 5

Trigger Term Quality

Quoted trigger phrases are natural user utterances ("design a welcome flow", "set up an abandoned-cart sequence", "plan a cold-outbound sequence") with good lifecycle-stage coverage, but common synonyms like "drip campaign" or "nurture sequence" are absent, which is the anchor-4 pattern of good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

It actively routes away from the three nearest-neighbor skills ("Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-specialist; not for writing each email's copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor"), giving a clear niche with minimal conflict risk rather than anchor 4's minor overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 36 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/nurture/email-sequence-designer/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.