react-email

React Email renderer for json-render that turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render. Use when working with @json-render/react-email, building transactional or marketing emails from JSON, creating email catalogs, rendering AI-generated email specs, or when the user mentions react-email, HTML email, or transactional email.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An efficient, actionable reference skill with executable examples and clear organization. The main gap is the absence of any bundle/reference files, leaving moderately large reference tables inline rather than split out for progressive disclosure.

Suggestions

Move the Standard Components tables and Sub-path Exports into a reference file (e.g. references/components.md) and link to it from the body to improve progressive disclosure.

Add a short end-to-end numbered workflow (define catalog -> build registry -> render to HTML/plain-text -> verify output) so the advanced path is as clear as the Quick Start.

Include a brief validation step (e.g. render to plain text as a smoke test, or check that root is Html and children are Head/Body) so the render flow has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and dense reference material that assumes Claude's competence; no padded concept explanations and every section earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready Quick Start and Catalog/Registry examples plus specific export and sub-path tables covering the common cases.	5 / 5
Workflow Clarity	The catalog -> spec -> renderToHtml flow is sequenced clearly across sections with concrete code; not a 5 because there is no single explicit numbered sequence or validation checkpoint tying the advanced registry flow together, though no destructive/batch cap applies.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and tables for easy navigation; not a 5 because no bundle files exist and some reference bulk (Standard Components, Sub-path Exports) is inlined that could be split into separate files.	4 / 5
	Total	18 / 20 Passed

Description

87%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, well-structured description that clearly states capability and trigger conditions with natural keywords and correct third-person voice. Minor room to add file-extension triggers and a few more action synonyms for maximal coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('turns JSON specs into HTML or plain-text emails', 'building transactional or marketing emails', 'creating email catalogs', 'rendering AI-generated email specs'); not a 5 because the distinct rendering actions could be enumerated more comprehensively.	4 / 5
Completeness	Explicitly answers both 'what' ('turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render') and 'when' ('Use when working with...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage with 'react-email, HTML email, transactional email' plus 'marketing emails' and 'JSON'; not a 5 because file-extension and a few synonym variations are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (React Email / json-render) with distinct triggers and minimal conflict risk; third-person voice is correct with no first/second-person slips.	5 / 5
	Total	18 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: vercel-labs/json-render
Path: skills/react-email/SKILL.md
Commit: 0f6798b

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.