Emaildesignskill

Skill Sequenzy/skills/skills/emaildesignskill

Agent skills for operating Sequenzy lifecycle, campaign, and transactional email workflows from Claude Code, Codex, Hermes, and OpenClaw-compatible agents.

Install

npx -y skills add Sequenzy/skills --skill emaildesignskill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on responsive email design, component systems, dark-mode behavior, and accessibility checks. Triggers include requests about template critique, module system planning, dark-mode QA, layout fixes, accessibility reviews, and design-to-email handoff.

SKILL.md

2.9 KB, as published. Nobody here has run it

Email Design Skill

Design for inbox constraints first. Treat every layout decision as a tradeoff across clients, viewports, accessibility, and production maintainability.

Scope

responsive email design, component systems, dark-mode behavior, and accessibility checks.

Request Signals

template critique, module system planning, dark-mode QA, layout fixes, accessibility reviews, and design-to-email handoff.

Guardrails

Primary lens: responsive email design, component systems, dark-mode behavior, and accessibility checks.
Common request signals: template critique, module system planning, dark-mode QA, layout fixes, accessibility reviews, and design-to-email handoff.
Default posture: Design for inbox constraints first. Treat every layout decision as a tradeoff across clients, viewports, accessibility, and production maintainability.
Useful output family: template audits, module specs, responsive QA tables, accessibility notes, implementation diffs, and design handoff checklists.

Execution Path

Identify the design artifact: raw HTML, React Email component, Figma concept, screenshot, ESP builder template, or module library.
Audit the hierarchy before aesthetics: preview text, primary message, CTA order, scannability, and fallback content.
Check responsive structure: container width, column collapse, image ratios, button tap targets, and long-copy behavior.
Evaluate client risk: Outlook tables, Gmail clipping, dark mode inversions, unsupported CSS, webfont fallbacks, and image blocking.
Review accessibility: semantic heading order where possible, alt text, contrast, link affordance, plain-language CTA, and text-image balance.
Return implementation notes that a developer or ESP operator can apply without redesigning the whole message.

Reviewer Notes

The design works without relying on image-only content.
The CTA remains visible and tappable on mobile.
Dark mode, image blocking, and long names do not break the message.
Reusable modules have clear constraints and do not require one-off overrides.
The final recommendation distinguishes rendering defects from brand preferences.

Output Pattern

Return template audits, module specs, responsive QA tables, accessibility notes, implementation diffs, and design handoff checklists. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.