About email-systems
An email-systems skill for teams working on transactional email, marketing automation, deliverability, and scalable email infrastructure. It emphasizes measuring returns for the actual audience and attribution window, without promising universal ROI or inbox placement.
Key features
- 01Transactional email guidance
- 02Marketing automation
- 03Deliverability practices
- 04Email infrastructure planning
- 05Audience- and attribution-aware measurement
Use cases
- 01Designing a password-reset email flow
- 02Reviewing email campaign performance
- 03Planning email systems for greater scale
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill email-systemsAfter installing, type/email-systemsin Claude Code to confirm it loaded.
Bundled filesreferences/detailed-guide.md
Details
From the project READMEEmail Systems
Measure email return and deliverability for the actual audience and attribution window; no universal ROI or inbox-delivery guarantee applies.
This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale.
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
Use this skill when the request clearly matches the capabilities and patterns described above.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Example
For a password reset, enqueue a short-lived opaque reference, fetch the token server-side without logging it, and deduplicate provider submission by event ID. A timeout is an unknown send outcome: reconcile before resending; show the same user-facing response whether or not the account exists.