# Build responsive email HTML with render QA

Email HTML can fail across clients, dark mode, and image-off settings. This skill creates table-based builds and documents rendering, accessibility, and plain-text checks.

## Install

```bash
npx skillstore add aaron-he-zhu/email-render-builder
```

## Metadata

- Status: approved
- Slug: aaron-he-zhu-email-render-builder
- Version: 19.0.0
- Author version: 19.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 54686c8bfd4fd09dbf774299498db66425b452222537e8d1a85c5eb1b943aa7b
- Author: aaron-he-zhu
- GitHub username: aaron-he-zhu
- License: Apache-2.0
- Repository: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/email/engage/email-render-builder
- Ref: adcb3549b15782055d0beb6d29f113d20de08f92
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/aaron-he-zhu-email-render-builder
- Manifest: https://skillstore.pages.dev/api/skills/aaron-he-zhu-email-render-builder/manifest

## Capabilities

- Creates single-column, table-based email HTML from approved creative.
- Recommends responsive layout patterns for Gmail, Outlook, Apple Mail, and mobile clients.
- Checks dark-mode color pairs, image-off fallbacks, and bulletproof CTA requirements.
- Produces an accessibility checklist for alt text, reading order, language, contrast, and mobile font size.
- Builds a client-render matrix that distinguishes estimated results from measured tests.
- Compares HTML and plain-text content for message, CTA, and destination parity.

## Use Cases

- Build a promotion email: Turn approved campaign copy into a responsive table-based email with a clear CTA and image-off fallbacks.
- Repair an Outlook layout: Review supplied email HTML and identify table, dark-mode, or image fallback changes for Outlook and other target clients.
- Prepare a newsletter handoff: Create a render matrix, accessibility checklist, and plain-text parity notes before ESP delivery.

## Prompt Templates

### Create a basic email build

```
Build responsive email HTML from this approved subject, preheader, body, CTA, and destination URL: [paste creative]. Use a single-column table layout.
```

### Check client rendering

```
QA this email HTML for Gmail, Outlook desktop and web, Apple Mail, iOS, and Android. List dark-mode, image-off, and responsive risks as Estimated unless tested: [paste HTML].
```

### Fix a rendering issue

```
This email breaks in Outlook and loses meaning when images are off. Revise the supplied HTML with table-safe structure, bulletproof CTAs, and fallbacks. Keep the approved copy unchanged: [paste HTML].
```

### Prepare an audited handoff

```
Build and QA this newsletter from the approved creative. Return HTML, a client-render matrix, accessibility results, image-off notes, and a plain-text alternate with matching CTA and destination: [paste creative].
```

## Limitations

- It does not write or revise email marketing copy.
- It cannot claim measured rendering without a real seed or preview test.
- It does not replace ESP-specific validation or paid rendering-preview services.
- Live render-test sends require an approved sender, user-owned test inboxes, and explicit confirmation.

## Best Practices

- Provide approved copy, the destination URL, target clients, and brand constraints before requesting a build.
- Treat untested client behavior as estimated and verify critical sends with user-owned seed inboxes.
- Keep the plain-text message, CTA, and destination aligned with the HTML version.

## Anti Patterns

- Do not use image-only offers or CTA buttons that disappear when images are blocked.
- Do not present support-matrix expectations as measured rendering results.
- Do not ask this skill to rewrite approved marketing copy or score campaign quality.

## Security Audit

- Audited at: 2026-07-26T10:17:01.997\+00:00
- Summary: Most static matches are false positives caused by Markdown fences, relative documentation links, and email-client terminology. Two operational behaviors remain: an optional live render-test email command and a user-confirmed local result save; neither shows malicious intent, but both require confirmation and path validation.

## Stats

- Views: 0
- Downloads: 2
- Favorites: 0
- Popularity score: 0