email-systems
CommunityMITEmail has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.
The ZIP contains only this skill. It lives on GitHub Releases of the public orlandoneto/agent-skills repo — Ontoom is the showcase. A daily crawler refreshes the catalog.
How to install
- Download the ZIP and extract the skill folder.
- Cursor:
.agents/skills/aitmpl-email-systems/or.cursor/skills/aitmpl-email-systems/ - Claude Code:
.claude/skills/aitmpl-email-systems/ - Other AIs:
.agents/skills/aitmpl-email-systems/
Source / credits: davila7/claude-code-templates
Other skills in this collection
- environment-setup-guide
Guide developers through setting up development environments with proper tools, dependencies, and configurations
- Error Resolver
Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior. Supports replay functionality to record and reuse solutions.
- eval-genius
Decide whether an AI/LLM/agent/retrieval system needs an eval, where it fits in the dev process, which one to run, and how to read the result; then design, gate, judge, and defend it. Not ordinary unit tests.
- event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
- excalidraw
Use when working with *.excalidraw or *.excalidraw.json files, user mentions diagrams/flowcharts, or requests architecture visualization - delegates all Excalidraw operations to subagents to prevent context exhaustion from verbose JSON (single files: 4k-22k tokens, can exceed read limits)
- executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints