email-template-builder

Build complete transactional email systems: React Email templates, provider integration (Resend, Postmark, SendGrid, AWS SES), preview server, i18n support, dark mode, spam optimization, analytics tracking. Use when adding transactional email to a new product, migrating between email providers, refactoring legacy email templates for accessibility, or adding internationalization to existing templates.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering-team/skills/email-template-builder/SKILL.md

Quality

Content

61%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 highly actionable with executable, copy-paste-ready code, but it is verbose and monolithic — full templates and styles are inlined rather than split into the referenced file structure, and the build/send workflow lacks explicit validation checkpoints.

Suggestions

Split the full template implementations (welcome, invoice, base layout) into files under emails/ and reference them from SKILL.md, keeping only a compact representative example inline to improve progressive disclosure.

Add an explicit build/send workflow with validation checkpoints (e.g., run email:dev preview → verify render → run spam checklist / Mail-Tester → send a test via sendEmail) to raise workflow clarity.

Trim inline marketing copy and redundant full style objects to reduce token cost; keep only the structural patterns that are non-obvious to Claude.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and accurate, but three full TSX templates with complete inline style objects and marketing copy ('You've got X days to explore everything... no credit card required') pad the body; these could be trimmed or referenced rather than inlined.	3 / 5
Actionability	Provides fully executable, copy-paste-ready TSX/TS code covering the common cases — base layout, welcome and invoice templates, unified send function, tracking, i18n, and preview-server scripts — with concrete imports and runnable commands.	5 / 5
Workflow Clarity	The project-structure tree and build commands imply a sequence, but there is no explicit multi-step workflow with validation checkpoints (e.g., render → preview → test deliverability → send) or feedback loops for the build/send flow.	3 / 5
Progressive Disclosure	No bundle files exist and all full template implementations, complete style objects, and per-template code are inlined in one ~440-line document; content that the project structure itself treats as separate files is not split out or referenced.	2 / 5
	Total	13 / 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 strong: specific, comprehensive, and explicitly covering both what the skill does and when to use it with natural trigger terms. Minor room to add file-extension synonyms for trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'React Email templates, provider integration (Resend, Postmark, SendGrid, AWS SES), preview server, i18n support, dark mode, spam optimization, analytics tracking' — giving comprehensive coverage of actions rather than vague claims.	5 / 5
Completeness	Explicitly answers both 'what' (build complete transactional email systems with the listed capabilities) and 'when' ('Use when adding transactional email to a new product, migrating between email providers...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('transactional email', 'email providers', 'email templates', 'internationalization') and specific provider names, but omits synonyms/file extensions like 'emails', 'HTML email', or '.html'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — transactional email infrastructure with named providers — and uses distinct, domain-specific triggers, making it unlikely to fire for unrelated skills. Third-person voice is used correctly.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering-team/skills/email-template-builder/SKILL.md
Commit: 19392f7

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