CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

48

Quality

51%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./creative-skills/multi-channel-ad-ideation/channels/email/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

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 strong in specificity and distinctiveness, clearly listing concrete deliverables like subject lines, body copy, CTAs, and HTML previews for email advertising. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger terms could also be expanded to cover more natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create marketing emails, email campaigns, promotional emails, or newsletter content.'

Expand trigger terms to include common user variations like 'marketing email', 'email campaign', 'newsletter', 'promotional email', 'email template', or 'drip sequence'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: generating subject lines, body copy, CTAs, and HTML previews. Also mentions producing multiple creative variations optimized for engagement and conversions.

3 / 3

Completeness

Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant terms like 'email', 'subject lines', 'body copy', 'CTAs', 'HTML previews', but misses common user variations like 'marketing email', 'newsletter', 'email campaign', 'promotional email', or 'email template'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'email advertising', 'subject lines', 'CTAs', and 'HTML previews' creates a clear niche that is unlikely to conflict with general copywriting or web development skills.

3 / 3

Total

10

/

12

Passed

Implementation

35%

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

This skill suffers primarily from excessive verbosity, spending significant token budget on general email marketing knowledge that Claude already possesses (subject line strategies, CTA best practices, body copy structure). The core workflow (Phase 1 text concepts → Phase 2 HTML previews with tool integration) is reasonably well-defined, but it's buried in tutorial-level marketing content. The skill would benefit greatly from moving reference material to supporting files and focusing the main SKILL.md on the specific generation workflow, output format, and tool usage.

Suggestions

Move 'Subject Line Strategies', 'Body Copy Structure', 'CTA Button Best Practices', and 'Visual Layout Approaches' sections to a reference file (e.g., references/email-best-practices.md) and link from the main skill—these are general knowledge that bloats the primary instruction set.

Remove explanatory marketing content Claude already knows (e.g., 'The Email Advantage' section, explanations of what subject lines and CTAs are) and focus on the specific output format and workflow requirements.

Condense the logo embedding section significantly—the full Python algorithm for luminance calculation is excessive; a brief rule ('use light logo on dark backgrounds, dark logo on light backgrounds, threshold at luminance 128') would suffice.

Add explicit validation steps for Phase 1 output (e.g., verify character counts internally, check concept count matches request) to strengthen the workflow with error-checking checkpoints.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines. It explains concepts Claude already knows (what email marketing is, what CTAs are, basic HTML concepts, what subject lines do). Sections like 'The Email Advantage', 'Body Copy Structure', 'CTA Button Best Practices', and 'Subject Line Strategies' are general marketing knowledge that Claude possesses. The dual logo variant section includes a full Python algorithm that could be much more concise. Much of this content is padded tutorial material rather than skill-specific instruction.

1 / 3

Actionability

The skill provides some concrete guidance—the Phase 2 HTML workflow with specific tool calls (mcp__tdx-studio__open_file), file naming conventions, and the card template format requirements are actionable. However, much of the content is descriptive best practices rather than executable instructions. The Python logo selection code is executable but most other guidance is advisory rather than copy-paste ready. Key templates are deferred to reference files that aren't provided.

2 / 3

Workflow Clarity

The Phase 1 → Phase 2 workflow is reasonably clear with explicit triggers for when to generate HTML vs. text concepts. The HTML generation workflow has numbered steps with validation-like checkpoints (steps 3-4 are mandatory). However, there's no explicit validation or error recovery for the overall concept generation process, and the interaction between standalone vs. delegated usage could be clearer in terms of step sequencing.

2 / 3

Progressive Disclosure

The skill references external files appropriately (examples.md, ../references/card-templates.md, ../references/html-preview-templates.md) for detailed templates and examples. However, the main SKILL.md itself contains far too much inline content that should be in reference files—the entire 'Subject Line Strategies', 'Body Copy Structure', 'CTA Button Best Practices', and 'Visual Layout Approaches' sections are reference material bloating the main file. No bundle files were provided to verify references exist.

2 / 3

Total

7

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
treasure-data/td-skills
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.