indranilbanerjee/digital-marketing-pro / skills/content-engine
content-engine
VerifiedDraft content in brand voice through a gated pipeline: blogs, ads, emails. Brief only → content-brief. "write a blog post about X"
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 35.1 KB |
| accessibility.md | markdown | 3.5 KB |
| ad-copy.md | markdown | 4.5 KB |
| ai-content-quality.md | markdown | 4.9 KB |
| brand-voice.md | markdown | 4.5 KB |
| case-studies.md | markdown | 16.9 KB |
| content-calendar.md | markdown | 4.5 KB |
| content-decay.md | markdown | 4.5 KB |
| draft-deliverables.md | markdown | 5.1 KB |
| email-automation.md | markdown | 4.3 KB |
| email-infrastructure.md | markdown | 5.5 KB |
| email-sequences.md | markdown | 5.5 KB |
| evals/evals.json | config | 2.6 KB |
| landing-pages.md | markdown | 4.5 KB |
| multilingual.md | markdown | 4.7 KB |
| personalization.md | markdown | 20.0 KB |
| seo-content.md | markdown | 5.5 KB |
| social-content.md | markdown | 5.0 KB |
| video-scripting.md | markdown | 16.5 KB |
email-automation.md
View on GitHub# Email Automation — Workflows & Triggers
## Trigger Taxonomy
| Trigger Type | Examples | Use Case |
|-------------|---------|----------|
| **Behavioral** | Page visit, form submit, link click, cart add, product view | Respond to user actions |
| **Time-based** | X days after signup, X days before renewal, anniversary | Lifecycle timing |
| **Attribute-based** | Segment change, lead score threshold, tag added | Profile changes |
| **Engagement** | Email opened, not opened in X days, clicked specific link | Email behavior |
| **Transactional** | Purchase made, subscription started, payment failed | Commerce events |
| **Predictive** | Churn risk score increase, predicted next purchase date | ML-based triggers |
---
## Common Automation Workflows
### Welcome Flow
```
Trigger: New subscriber / signup
→ Email 1 (immediate): Welcome + value delivery
→ Wait 2 days
→ Email 2: Quick-start guide
→ Wait 3 days
→ Email 3: Social proof / success story
→ Wait 4 days
→ Email 4: Feature highlight or tip
→ Wait 7 days
→ Email 5: Upgrade / next step CTA
→ Exit: Move to regular nurture
```
### Browse Abandonment
```
Trigger: Viewed product page, did NOT add to cart (within 1 hour)
→ Wait 2 hours
→ Email 1: "Still interested in [Product]?" + product image + reviews
→ Wait 24 hours
→ Check: Did they purchase? → Yes: Exit | No: Continue
→ Email 2: Related product recommendations
→ Exit
```
### Re-Engagement
```
Trigger: No email open or click for 60 days
→ Email 1: "We miss you" + what's new
→ Wait 7 days
→ Check: Engaged? → Yes: Return to active | No: Continue
→ Email 2: Exclusive offer or content
→ Wait 7 days
→ Check: Engaged? → Yes: Return to active | No: Continue
→ Email 3: "Last email unless you want to stay"
→ Wait 7 days
→ Check: Engaged? → Yes: Return to active | No: Suppress from marketing
```
---
## Dynamic Content Rules
| Rule Type | Logic | Example |
|-----------|-------|---------|
| **Segment-based** | Show different content per segment | Enterprise sees case study; SMB sees quick-start guide |
| **Behavioral** | Based on past actions | Show "upgrade" CTA to free users; "renew" to expiring |
| **Location** | Based on geography | Local event invites, regional offers |
| **Product interest** | Based on browsing/purchase history | Product recommendations matching viewed categories |
| **Lifecycle stage** | Based on customer stage | New customer sees onboarding; active sees advanced tips |
---
## Send Time Optimization
### Methods
1. **Historical analysis**: Send at times with highest open rates from past campaigns
2. **Per-subscriber optimization**: ML-based prediction of each subscriber's optimal time
3. **Time zone adjustment**: Send at target time in each subscriber's local time zone
4. **Day optimization**: Test different days, analyze by segment
### General Benchmarks
- B2B: Tuesday-Thursday, 9-11 AM local time
- B2C: Tuesday-Thursday, 10 AM or 7-9 PM local time
- eCommerce: Sunday evenings, Tuesday mornings (varies by industry)
---
## Frequency Capping
| Subscriber Segment | Max Emails/Week | Types |
|-------------------|----------------|-------|
| New subscriber (first 30 days) | 3-4 | Welcome + 1 marketing |
| Active engaged | 2-3 | Marketing + triggered |
| Moderately engaged | 1-2 | Marketing only |
| Low engagement | 1/2 weeks | Re-engagement only |
| Transactional-only | As needed | Receipts, notifications |
### Priority Rules
When multiple automations trigger for the same subscriber:
1. Transactional emails always send (receipts, confirmations)
2. Triggered automations take priority over scheduled campaigns
3. Most recent trigger takes priority if multiple trigger simultaneously
4. Always respect global frequency cap
---
## Automation Performance Metrics
| Metric | Target | Action if Below |
|--------|--------|----------------|
| Open rate (directional only: Apple Mail Privacy Protection inflates opens) | >25% | Test subject lines, send time, from name; confirm with clicks |
| Click rate | >3% | Improve content, CTA, personalization |
| Conversion rate | Varies by flow | Optimize offer, landing page, segmentation |
| Unsubscribe rate | <0.5% per email | Reduce frequency, improve targeting |
| Revenue per email | Increasing trend | Optimize product recommendations, offers |
| Automation completion rate | >60% | Check for friction points, improve content |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |