EDM Review
RexYen/edm-review
Revisa templates de email com feedback não-técnico para time de marketing
Ver no GitHubSkill para revisar templates HTML de emails transacionais (EDM) com feedback em linguagem acessível para profissionais de marketing e conteúdo. Traduz problemas técnicos reais (limitações Gmail, quirks Outlook, dark mode, acessibilidade) em orientações práticas e acionáveis, priorizando por severidade.
Instalação
npx convez-ai RexYen/edm-review1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Revisar templates de notificação transacional antes do envio
- Validar compatibilidade com Gmail, Outlook e clientes mobile
- Identificar problemas de acessibilidade e contraste em emails
- Traduzir erros HTML/CSS para feedback compreensível por marketers
Veredito

Ferramenta bem pensada que preenche lacuna real entre engenheiros e times de marketing em fluxos de email. A documentação é sólida e as regras mapeiam bugs reais de produção; requer configuração inicial por projeto mas economiza ciclos de revisão.
README
A tradução para o português deste README ainda está na fila.
edm-review
A Claude Code skill for reviewing transactional EDM (email marketing / notification) HTML templates. Translates engineering findings into plain-language feedback for marketing, content, and brand reviewers.
Every rule traces to a real production bug — Gmail SVG limitations, <style> all-or-nothing stripping, dark-mode forcing, CTA specificity battles, Outlook (Word engine) border-radius quirks, and New Outlook (Chromium) post-processing quirks.
What it does
- Reviews the HTML against four reference checklists: structure / syntax, visual styling, client compatibility, and accessibility
- Surfaces issues grouped by severity — 🔴 有風險 (will break for real users) vs. 🟢 可以更好 (polish)
- Lets you pick which issues to fix via a multi-select prompt
- Applies the fixes and returns a diff (or a full file for large edits)
The review output is written for non-engineers. No specificity, selector, MSO, or color-scheme jargon — just "Gmail 使用者會看不到按鈕的字" with a plain-language reason.
Install
Clone into your Claude Code skills directory. Pinning to a tagged release is recommended so you only update when you choose to:
# Recommended — pinned to a release
git clone --branch v1.1 --depth 1 https://github.com/RexYen/edm-review.git ~/.claude/skills/edm-review
If you'd rather track main and git pull for updates, drop the --branch and --depth flags. Note that anything on main ends up auto-loaded into Claude's context the next time the skill triggers, so pinning gives you a chance to review changes first.
Use
Paste EDM HTML into Claude Code and ask for a review. Triggers include:
幫我看一下這個 edmreview this email template這個信件模板有沒有問題幫我檢查 edm看一下這個 Mailgun template
Or just paste raw email HTML with no instructions — the skill auto-triggers.
Configure
Project-specific values (brand name, brand domain, primary language, sending platform, icon system, deeplink provider, dark-mode policy) live in SKILL.md under the "Project conventions" section. Edit those to fit your team's stack before first use.
Default assumptions out of the box: Mailgun template variables, Iconify Lucide CDN for icons, Branch deeplinks (optional per CTA), force light mode. See SKILL.md for the full list.
Repo layout
SKILL.md Skill manifest + workflow
references/
structure-syntax.md HTML validity, comments, escaping
visual-styling.md CTA, dark mode, border-radius, fonts
client-compat.md Gmail / Outlook / iOS / Branch gotchas
accessibility.md alt text, lang, contrast