# Improve Email Code Workflows

Email implementation often spans templates, content, tests, and rollout approvals. This skill helps AI agents make scoped repository changes with QA checks and approval boundaries.

## Install

```bash
npx skillstore add sequenzy/codexemailskill
```

## Metadata

- Status: approved
- Slug: sequenzy-codexemailskill
- Skillstore revision: r1
- Version status: missing
- Tree hash: 13f51df04e2bde379e53456fefd8b0334550219641eb7185cebf879b8f5f8060
- Author: Sequenzy
- GitHub username: Sequenzy
- License: MIT
- Repository: https://github.com/Sequenzy/skills/tree/main/skills/codexemailskill
- Ref: e397ce5a135369cd6def89cb6400d013e2f68f2f
- 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
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/sequenzy-codexemailskill
- Manifest: https://skillstore.pages.dev/api/skills/sequenzy-codexemailskill/manifest

## Capabilities

- Identifies email templates, components, content files, preview routes, tests, and export scripts in a repository.
- Plans scoped email changes that match existing naming, styling, localization, and data-loading patterns.
- Guides implementation of copy updates, layout fixes, template modules, data fields, and tracking parameters.
- Recommends focused verification with render checks, type checks, snapshots, lint, unit tests, or preview builds.
- Separates code changes from live sends, contact imports, DNS changes, suppression edits, and production automations.

## Use Cases

- Fix a Template Regression: Update a React Email template while preserving local patterns and verifying the rendered result.
- Prepare Campaign Content Changes: Change MDX or content-system email copy with tracking checks and production approval boundaries.
- Review Email System Risk: Audit proposed email code changes for scope, verification, rollout risk, and approval needs.

## Prompt Templates

### Find the Email Surface

```
Use this skill to identify the email templates, content files, preview routes, and tests related to this request.
```

### Plan a Scoped Email Edit

```
Use this skill to create a repo-aware plan for updating this email template while preserving existing patterns.
```

### Implement and Verify a Change

```
Use this skill to make the smallest coherent email code change and run the narrowest useful verification.
```

### Audit a Production Email Change

```
Use this skill to review this email change for rollout risk, approval gates, tracking behavior, and verification gaps.
```

## Limitations

- It does not send live email or approve production rollout actions.
- It depends on accessible repository email files, previews, or tests.
- It cannot guarantee rendering across every email client without external preview tooling.
- It provides workflow guidance, not an ESP-specific migration engine.

## Best Practices

- Read adjacent email files before editing so local structure and naming stay consistent.
- Keep production actions separate from repository changes and require explicit approval for live-system operations.
- Run the narrowest verification that proves the user-visible email behavior changed correctly.

## Anti Patterns

- Do not create a parallel email framework when established templates already exist.
- Do not change DNS, suppressions, imports, sends, or automations as part of a code-only request.
- Do not skip fallback handling for dynamic fields that may be empty or undefined.

## Security Audit

- Audited at: 2026-07-06T21:07:52.57\+00:00
- Summary: AI review found both static system reconnaissance matches are false positives in Markdown guidance. SKILL.md line 23 is a heading, and line 32 limits edits to small scoped changes. No prompt injection, executable code, network activity, credential access, or data exfiltration intent was found.

## Stats

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