Agent skill · writing content · aiskillstore
codexemailskill
Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on repo-aware email implementation workflows for codebases, content systems, templates, and tests. Triggers include requests about template implementation, React Email edits, MDX content changes, QA scripts, codebase diffs, and testable email fixes.
Why this skill is useful
Provides domain-specific workflows and QA scripts for implementing email changes in codebases that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Codex Email Skill Treat email work as a code change. Read the repo, keep edits scoped, preserve existing patterns, and make the result verifiable. Fit Check 1. Primary lens: repo-aware email implementation workflows for codebases, content systems, templates, and tests. 2. Common request signals: template implementation, React Email edits, MDX content changes, QA scripts, codebase diffs, and testable email fixes. 3. Default posture: Treat email work as a code change. Read the repo, keep edits scoped, preserve existing patterns, and make the result verifiable. 4. Useful output family: repo-aware implementation plans, template diffs, QA scripts, render checks, content patches, and concise change reports. 5. Production boundary: separate recommendation from execution. 6. Evidence boundary: say which source material supports the recommendation. Use This For repo-aware email implementation workflows for codebases, content systems, templates, and tests. Avoid Using It For Generic email advice with no audience, platform, lifecycle, evidence, or approval context. Procedure 1. Locate the email surface in the repository: components, templates, content files, campaign config, preview routes, tests, or ESP export scripts. 2. Read adjacent files before editing so naming, styling, localization, and data-loading patterns match the codebase. 3. Define the intended behavior as a diffable change: copy update, layout fix, template module, data field, tracking parameter, or QA assertion. 4. Implement the smallest coherent change and avoid unrelated refactors, dependency churn, or broad style rewrites. 5. Run the narrowest useful verification: type check, template render, snapshot, unit test, lint, preview build, or visual smoke check. 6. Report changed files, verification result, remaining risk, and any production steps that still need approval. Acceptance Checks 1. The edit follows local patterns instead of inventing a parallel email system. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/codexemailskill