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.

57

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 instruction skill whose phase-gated workflow and concrete tooling details are its strengths. It is held back by verbosity from generic email-marketing knowledge, a missing validation loop, and a broken reference layer — all cited reference files are absent from the bundle and paths are inconsistent.

Suggestions

Ship the referenced bundle files (card-templates.md, html-preview-templates.md, examples.md) and normalize their paths — currently both 'references/...' and '../references/...' are used and none of the files exist.

Trim generic marketing knowledge (subject-line strategy taxonomy, CTA best practices, mobile-open stats) and the repeated mcp__tdx-studio workflow statements; state the requirement once.

Move the dual-logo luminance algorithm and its Python code to a reference file, and add a small validation step for Phase 2 (e.g., confirm the preview opened, handle a missing/unreadable logo file).

DimensionReasoningScore

Conciseness

The body is mostly efficient, task-specific instruction (phase gating, card format, file naming, MCP calls), but includes unnecessary explanation Claude already knows: generic email marketing advice ('60%+ opens on mobile', 'Vague CTAs don't drive action', subject-line strategy taxonomy), a ~35-line WCAG luminance routine, and the mcp__tdx-studio workflow requirement stated three times. Not a 2 because the padding is a minority of the content and most sections carry project-specific value.

3 / 5

Actionability

Guidance is largely executable: exact file-naming format ('email-preview-{timestamp}.html ... YYYYMMDD-HHMMSS'), the exact MCP call 'mcp__tdx-studio__open_file', the base64 data-URI pattern, runnable Python for logo selection, and a fully worked concept example. Not a 5 because the central card markup is delegated to '../references/card-templates.md', which does not exist in the bundle, leaving a gap in the most important output format.

4 / 5

Workflow Clarity

The two-phase workflow is clearly sequenced with an explicit gating checkpoint ('ONLY generate HTML previews AFTER user confirms text concepts') and numbered steps including automatic file-write and preview-open. Not a 5 because there are no validation or error-recovery steps (e.g., what to do if the preview fails to open or the logo file is unreadable), though the operations are non-destructive so the batch/destructive cap does not apply.

4 / 5

Progressive Disclosure

The body is well-sectioned and references are clearly signaled, but every referenced file ('../references/card-templates.md', 'references/html-preview-templates.md' referenced under two inconsistent paths, 'examples.md') is absent from the bundle, which contains no references/ directory at all. Additionally, self-contained material like the dual-logo selection algorithm and its Python implementation is inlined where a reference file would be the stated pattern. This fits 'some structure but could be better organized' rather than score 4's 'most content appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

71%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, concrete description that clearly names the skill's deliverables. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness and weakens discovery. Adding explicit usage triggers with natural synonyms (email campaign, newsletter, email marketing) would lift it to top-tier.

Suggestions

Append an explicit trigger clause, e.g.: 'Use when the user asks for email ads, email campaigns, newsletters, or marketing emails with subject lines and CTAs.'

Add common synonyms users would naturally say ('email marketing', 'newsletter', 'email campaign') to broaden trigger coverage.

Drop or sharpen 'optimized for inbox engagement and conversions' — it reads as buzzword padding without adding capability information.

DimensionReasoningScore

Specificity

The description lists multiple concrete deliverables — 'compelling subject lines, body copy, CTAs, and HTML previews' plus 'multiple creative variations' — giving comprehensive coverage of the skill's outputs. The trailing 'optimized for inbox engagement and conversions' is mild buzzword, but the action list matches the top anchor; score 4 would require notable coverage gaps that aren't present.

5 / 5

Completeness

The 'what' is clearly stated ('Generate email advertising concepts...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'email advertising concepts', 'subject lines', 'CTAs', 'HTML previews'. Common variations like 'email campaign', 'newsletter', or 'email marketing' are missing, which fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym/extension coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The email-advertising niche with subject lines/CTAs/HTML previews is mostly distinct, with only minor overlap risk against closely related creative or copywriting skills. It is not a 5 because adjacent marketing-copy skills (e.g., a broader ad-copy or multi-channel ideation skill) could plausibly compete for the same requests.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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