skills/tier3-advanced/email-system-builder/SKILL.md
Transactional and marketing emails with templates and tracking
npx skillsauth add abcnuts/manus-skills email-system-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Set up complete email systems with beautiful templates, tracking, and deliverability best practices.
Send transactional emails (welcome, password reset, receipts) and marketing emails (newsletters, campaigns) with professional templates.
python3 /home/ubuntu/skills/email-system-builder/scripts/setup_email.py \
/path/to/project \
resend
import { Resend } from 'resend'
import WelcomeEmail from '@/emails/welcome'
const resend = new Resend(process.env.RESEND_API_KEY)
await resend.emails.send({
from: '[email protected]',
to: user.email,
subject: 'Welcome!',
react: WelcomeEmail({ name: user.name })
})
Manual: 2-3 hours
With Skill: 15-20 minutes
Saved: ~2 hours per project
scripts/setup_email.py - Automated setuptemplates/welcome-email.tsx - React Email templatereferences/email_patterns.md - Best practicesuser-authentication-system - Send password reset emailsanalytics-dashboard - Track email engagementdatabase-schema-generator - Create email tracking tablesProfessional emails in minutes, not hours.
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code