react-email

Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/react-email/SKILL.md

Quality

Content

65%

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

A highly actionable skill body with concrete executable code and real, well-signaled reference files, weakened by package-manager repetition, missing error-recovery feedback loops, and inline duplication of content already in the reference bundle.

Suggestions

Collapse the npm/yarn/pnpm/bun variants for install and dev into a single command with a short "or: yarn/pnpm/bun equivalent" note to cut repeated tokens.

Add an explicit validate→fix→retry feedback loop for the setup and render/send workflows (e.g., what to do when `npm run dev` fails or the Resend send returns an error) to raise workflow clarity.

Remove the inlined component list and full i18n quick example from SKILL.md, keeping only a concise pointer to references/COMPONENTS.md and references/I18N.md to avoid duplicating content already in the bundle.

Dimension	Reasoning	Score
Conciseness	Mostly actionable and free of concept-explaining fluff, but repeats every command across four package managers (npm/yarn/pnpm/bun) for both install and dev sections and includes a lengthy full basic template, so it could be tightened to respect token budget.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance — `npx create-email@latest`, `npm run dev`, complete TSX template with imports, `render()` examples, and a Resend SDK send snippet — with specific concrete details throughout.	3 / 3
Workflow Clarity	The scaffold→cd→install→dev→verify sequence is clearly ordered and includes an explicit "Verify Installation" checkpoint, but error-recovery feedback loops (validate→fix→retry) and checklists for the fragile steps are absent, so it stops short of the top anchor.	2 / 3
Progressive Disclosure	References are real, one-level-deep, and clearly signaled via markdown links (COMPONENTS.md, SENDING.md, I18N.md, PATTERNS.md all exist), but substantial content that duplicates those files is inlined — a full component list plus a complete i18n example — so content that should be separate remains inline.	2 / 3
	Total	9 / 12 Passed

Description

90%

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, third-person description with an explicit "Use when" trigger and a rich set of natural trigger terms; its only weakness is that it states a single action verb rather than enumerating multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	Quotes one concrete action ("creating HTML email templates with React components") and enumerates six specific email kinds ("welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails"), but only a single verb is stated, so it names the domain and some actions rather than listing multiple distinct concrete actions.	2 / 3
Completeness	Explicitly answers both what ("creating HTML email templates with React components") and when via the explicit "Use when ..." trigger clause enumerating concrete scenarios; not merely implied.	3 / 3
Trigger Term Quality	Includes natural terms a user would actually say — "welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails" plus "HTML email templates" and "React components" — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The React-component / HTML-email niche with enumerated transactional-email triggers is clearly distinguishable from other skills and unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (519 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: novuhq/novu
Path: .agents/skills/react-email/SKILL.md
Commit: 67de0fa

Reviewed: about 14 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.