agentsclimarketplace

Codexemailskill

Skill Sequenzy/skills/skills/codexemailskill

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 codexemailskill

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 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.

SKILL.md

3.0 KB, as published. Nobody here has run it

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. Dynamic fields have fallbacks and do not leak undefined values into copy.
  3. Rendering constraints are considered before using modern CSS.
  4. Tests or previews cover the user-visible behavior when risk justifies it.
  5. No live send, import, DNS, or suppression action is performed as part of a code edit.

Output Pattern

Return repo-aware implementation plans, template diffs, QA scripts, render checks, content patches, and concise change reports. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.