react-email

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

Quality

75%

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

67%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 thorough, largely actionable skill body with good reference structure and a clear setup workflow. It loses points mainly to verbosity (repeated package-manager variants) and a navigation gap where STYLING.md is unreferenced.

Suggestions

Collapse the repeated npm/yarn/pnpm/bun blocks: state the command once per step and note 'or the equivalent for your package manager', cutting ~9 redundant code blocks.

Link references/STYLING.md from the 'Styling considerations' section (and the Additional Resources list) so the dedicated styling reference is discoverable.

Replace the vague tsconfig guidance with the concrete compilerOptions needed for jsx (e.g. "jsx": "react-jsx") or point to a snippet, so the step is executable.

Dimension	Reasoning	Score
Conciseness	Mostly useful and concrete, but noticeably padded: the npm/yarn/pnpm/bun variants are repeated across three separate steps (12 near-identical code blocks), plus unnecessary prose like 'a modern, component-based approach to email development' and the odd 'Your task is to start the local preview server' phrasing.	3 / 5
Actionability	Largely copy-paste-ready guidance (full welcome-email component, render, Resend send, i18n example, image baseURL pattern) with a minor gap in the tsconfig section which only says to 'ensure proper support for jsx' without providing the actual config.	4 / 5
Workflow Clarity	Setup is clearly sequenced (scaffold -> cd -> install -> dev -> verify) with an explicit 'Verify Installation' checkpoint, a 'ask clarifying questions FIRST' pre-check, and error handling in the send example, though feedback loops are light and there is no checklist.	4 / 5
Progressive Disclosure	References are one level deep and well-signaled ('See [references/X.md] for...'), but references/STYLING.md exists in the bundle yet is never linked from the body, and the inline styling section is sizable despite a dedicated file existing.	4 / 5
	Total	15 / 20 Passed

Description

82%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 concise, well-targeted description that explicitly covers both what the skill does and when to invoke it, with strong natural trigger terms and a distinct niche. The only weakness is that the 'what' describes a single action (creating) rather than a fuller action set.

Dimension	Reasoning	Score
Specificity	Names the domain ('HTML email templates with React components') and one concrete action ('creating') plus six example email types, but the listed email types are instances of a single action rather than distinct actions like extract/fill/merge, so it does not reach 'several specific actions'.	3 / 5
Completeness	Explicitly answers both: 'what' (creating HTML email templates with React components) and 'when' (an explicit 'Use when...' clause with six concrete trigger phrases), matching the anchor that requires both with concrete triggers.	5 / 5
Trigger Term Quality	Strong natural keywords users actually say ('email templates', 'welcome emails', 'password resets', 'notifications', 'order confirmations', 'newsletters', 'transactional emails'), but missing common synonyms like 'React Email', 'responsive emails', and any file-extension cues, so not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	'HTML email templates with React components' carves a clear niche (React Email) with distinct triggers, giving minimal overlap risk with generic React or HTML/CSS skills.	5 / 5
	Total	17 / 20 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: dc9caee

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