React Email renderer that converts JSON specs into HTML or plain-text email output.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreact-emailExecute the skills CLI command in your project's root directory to begin installation:
Fetches react-email from vercel-labs/json-render and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate react-email. Access via /react-email in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
14.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14.0K
stars
React Email renderer that converts JSON specs into HTML or plain-text email output.
import { renderToHtml } from "@json-render/react-email";
import { schema, standardComponentDefinitions } from "@json-render/react-email";
import { defineCatalog } from "@json-render/core";
const catalog = defineCatalog(schema, {
components: standardComponentDefinitions,
});
const spec = {
root: "html-1",
elements: {
"html-1": { type: "Html", props: { lang: "en", dir: "ltr" }, children: ["head-1", "body-1"] },
"head-1": { type: "Head", props: {}, children: [] },
"body-1": {
type: "Body",
props: { style: { backgroundColor: "#f6f9fc" } },
children: ["container-1"],
},
"container-1": {
type: "Container",
props: { style: { maxWidth: "600px", margin: "0 auto", padding: "20px" } },
children: ["heading-1", "text-1"],
},
"heading-1": { type: "Heading", props: { text: "Welcome" }, children: [] },
"text-1": { type: "Text", props: { text: "Thanks for signing up." }, children: [] },
},
};
const html = await renderToHtml(spec);
Same flat element tree as @json-render/react: root key plus elements map. Root must be Html; children of Html should be Head and Body. Use Container (e.g. max-width 600px) inside Body for client-safe layout.
import { defineCatalog } from "@json-render/core";
import { schema, defineRegistry, renderToHtml } from "@json-render/react-email";
import { standardComponentDefinitions } from "@json-render/react-email/catalog";
import { Container, Heading, Text } from "@react-email/components";
import { z } from "zod";
const catalog = defineCatalog(schema, {
components: {
...standardComponentDefinitions,
Alert: {
props: z.object({
message: z.string(),
variant: z.enum(["info", "success", "warning"]).nullable(),
}),
slots: [],
description: "A highlighted message block",
},
},
actions: {},
});
const { registry } = defineRegistry(catalog, {
components: {
Alert: ({ props }) => (
<Container style={{ padding: 16, backgroundColor: "#eff6ff", borderRadius: 8 }}>
<Text style={{ margin: 0 }}>{props.message}</Text>
</Container>
),
},
});
const html = await renderToHtml(spec, { registry });
| Function | Purpose |
|---|---|
renderToHtml(spec, options?) |
Render spec to HTML email string |
renderToPlainText(spec, options?) |
Render spec to plain-text email string |
RenderOptions: registry, includeStandard (default true), state (for $state / $cond).
Supports visible conditions, $state, $cond, repeat (repeat.statePath), and the same expression syntax as @json-render/react. Use state in RenderOptions when rendering server-side so expressions resolve.
Import schema and catalog without React or @react-email/components:
import { schema, standardComponentDefinitions } from "@json-render/react-email/server";
| Export | Purpose |
|---|---|
defineRegistry |
Create type-safe component registry from catalog |
Renderer |
Render spec in browser (e.g. preview); use with JSONUIProvider for state/actions |
createRenderer |
Standalone renderer component with state/actions/validation |
renderToHtml |
Server: spec to HTML string |
renderToPlainText |
Server: spec to plain-text string |
schema |
Email element schema |
standardComponents |
Pre-built component implementations |
standardComponentDefinitions |
Catalog definitions (Zod props) |
| Path | Purpose |
|---|---|
@json-render/react-email |
Full package |
@json-render/react-email/server |
Schema and catalog only (no React) |
@json-render/react-email/catalog |
Standard component definitions and types |
@json-render/react-email/render |
Render functions only |
All components accept a style prop (object) for inline styles. Use inline styles for email client compatibility; avoid external CSS.
| Component | Description |
|---|---|
Html |
Root wrapper (lang, dir). Children: Head, Body. |
Head |
Email head section. |
Body |
Body wrapper; use style for background. |
| Component | Description |
|---|---|
Container |
Constrain width (e.g. max-width 600px). |
Section |
Group content; table-based for compatibility. |
Row |
Horizontal row. |
Column |
Column in a Row; set width via style. |
| Component | Description |
|---|---|
Heading |
Heading text (as: h1–h6). |
Text |
Body text. |
Link |
Hyperlink (text, href). |
Button |
CTA link styled as button (text, href). |
Image |
Image from URL (src, alt, width, height). |
Hr |
Horizontal rule. |
| Component | Description |
|---|---|
Preview |
Inbox preview text (inside Html). |
Markdown |
Markdown content as email-safe HTML. |
<style> blocks.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
asyrafhussin/agent-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
react-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in react-email — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
react-email has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: react-email is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in react-email — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
react-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: react-email is focused, and the summary matches what you get after install.
Registry listing for react-email matched our evaluation — installs cleanly and behaves as described in the markdown.
react-email reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend react-email for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 38