CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

email-creative-builder

Use when the user asks to "write the email", "draft subject lines", or "build email creative"; produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt — message-matched to the destination page and claims-ledger-aware. Not for pre-scoring or ranking subject-line variants (spam/truncation/render pre-score) — use subject-line-lab; not for scoring the email or computing EQS — use email-quality-auditor; not for the multi-step flow — use email-sequence-designer; not for the A/B test plan — use send-experiment-designer. 邮件文案/主题行/邮件创意

Quality

84%

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

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

The body is a well-engineered orchestration document: an 11-step workflow with genuine validation checkpoints, decision gates, a quality-bar feedback loop, and appropriately split-out reference files. Its weaknesses are repetition — the sibling-skill routing disclaimers appear three times and the quality bar duplicates the done-when criteria — and reliance on out-of-bundle files for a few core contract details.

Suggestions

State the not-for boundaries (subject-line-lab, email-quality-auditor, email-sequence-designer, send-experiment-designer) once — in the Scope guard — and let the Next Best Skill section link without re-arguing them; this removes ~3 redundant sentences and lets the conciseness score improve.

Merge the 5-item Quality bar into the 'Done when' criteria (or replace it with a pointer), since they enumerate the same checks; keep the single "fix it or report it, do not ship silently" feedback instruction.

Add the natural trigger variations the skill supports (newsletter, cold email, email copy) to the description's 'Use when' clause so trigger coverage matches the three modes the body implements.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but the not-X routing disclaimers are repeated three times (intro paragraph, Scope guard, and Next Best Skill: "It does not score the email, run the D1 veto... that is email-quality-auditor... it does not design the multi-step flow... or the test"), and the Quality bar restates the "Done when" criteria nearly verbatim. Not 4: this redundancy is noticeable tightening work, not minor over-explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: an 11-step procedure, Quick Start invocations, a specific output structure ("3-5 subject-line variants, a preheader, structured body copy, a single primary CTA, and a plain-text alternate"), an exact save path (memory/email/email-creative-builder/YYYY-MM-DD-<offer>.md), and an idempotent "operation: propose" event through registry-events.py. Not 5: there is no worked example of a finished creative, and registry-events.py plus the handoff-summary template live outside the bundle, so the guidance is not fully self-contained.

4 / 5

Workflow Clarity

Clear 11-step sequence with explicit validation checkpoints and error recovery: Decision Gates define stop-and-ask vs continue-silently paths with NEEDS_INPUT naming the missing URL, step 8 enforces message-match by dropping lines the page cannot deliver, unresolved claims block ready-to-send status, and a 5-item Quality bar checklist ends with "If any item fails, fix it or report it in the handoff — do not ship silently." Not 4: the feedback loop and checklist are explicit, matching the top anchor; no destructive/batch cap applies since this is a generative skill.

5 / 5

Progressive Disclosure

Good structure: the SKILL.md body is an overview, and the mode pattern sets and render limits are correctly split into two real, one-level-deep bundle references (references/email-creative-modes.md, references/subject-line-specs.md), each clearly signaled with a description in the Reference Materials section. Not 5: several load-bearing details — the handoff summary shape (skill-contract.md), the slop check, send-control rules, and registry-events.py — live outside the bundle via ../../../ paths, so navigation is not fully self-contained.

4 / 5

Total

16

/

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.

The description is a strong example: it states concrete deliverables, quotes natural trigger phrases, answers both what and when explicitly, and cleanly fences off four sibling skills with per-skill not-for clauses. The only gap is a few missing natural trigger variations (newsletter, cold email, email copy) that the skill itself lists as supported modes.

DimensionReasoningScore

Specificity

"produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt — message-matched to the destination page and claims-ledger-aware" lists multiple specific concrete deliverables with comprehensive coverage of the skill's outputs. Not 4: the coverage has no gaps — every output artifact of the skill is enumerated.

5 / 5

Completeness

Explicitly answers both: what ("produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt") and when ("Use when the user asks to 'write the email', 'draft subject lines', or 'build email creative'") with concrete trigger phrases, plus explicit not-for boundaries. Not 4: the 'when' is fully explicit with quoted trigger phrases, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say are quoted directly ("write the email", "draft subject lines", "build email creative") plus Chinese synonyms (邮件文案/主题行/邮件创意). Not 5: common natural variations the skill itself supports — "newsletter", "cold email", "email copy" — are absent from the trigger set.

4 / 5

Distinctiveness Conflict Risk

A clear niche (the pre-click creative unit) with explicit routing away from four named sibling skills (subject-line-lab, email-quality-auditor, email-sequence-designer, send-experiment-designer). Not 4: the negative boundaries are enumerated per adjacent skill, leaving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 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: 19 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/engage/email-creative-builder/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.