email

Generate email advertising concepts with compelling subject lines, body copy, CTAs, and HTML previews. Produces multiple creative variations optimized for inbox engagement and conversions.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with clear phased workflows, but it runs long for a SKILL.md and its referenced bundle files do not actually exist, weakening progressive disclosure.

Suggestions

Create the referenced bundle files (references/card-templates.md, references/html-preview-templates.md, examples.md) or remove the dead references.

Trim general marketing best-practice explanations Claude already knows to improve token efficiency, moving extended detail into the reference files.

Dimension	Reasoning	Score
Conciseness	The ~300-line body is mostly actionable but contains best-practice padding Claude already knows (e.g., "Trackable - Opens, clicks, conversions all measurable", mobile-open stats) and could be tightened.	2 / 3
Actionability	Provides concrete CTA examples, subject-line templates, a worked body-copy structure, an executable base64 logo-selection script, and an explicit HTML generation workflow with named tool calls and file-naming formats.	3 / 3
Workflow Clarity	The two-phase flow (text concepts -> user confirmation -> HTML preview) is clearly sequenced with an explicit gating checkpoint and a numbered HTML workflow; no destructive/batch operation requiring a validate-retry loop is present.	3 / 3
Progressive Disclosure	The body signals one-level-deep references (card-templates.md, html-preview-templates.md, examples.md) but none of those files or bundle directories exist, and substantial detail (logo algorithm, best-practice lists) is inline rather than offloaded.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive but stops short of completeness: it names concrete capabilities yet omits an explicit "Use when" trigger clause and lacks full coverage of natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause naming when Claude should invoke this skill (e.g., 'Use when the user needs email ad concepts, email copy, or HTML email previews').

Broaden trigger terms to cover natural user phrasings like 'email ad', 'email campaign', 'newsletter copy', and 'email creative'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - "compelling subject lines, body copy, CTAs, and HTML previews" and "Produces multiple creative variations" - matching the multi-action anchor.	3 / 3
Completeness	Clearly states what it does but lacks any "Use when..." trigger clause; per the rubric a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Has relevant keywords ("email advertising concepts", "subject lines", "HTML previews") but misses common natural variations a user would say ("email ad", "email campaign", "newsletter", "email copy").	2 / 3
Distinctiveness Conflict Risk	The email-advertising niche is distinct with email-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: treasure-data/td-skills
Commit: 50d5a57

Reviewed: 8 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.