Channel Playbook -- Email / CRM

Validates and guides email CRM campaign content against editorial, design, and commercial rules.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill channel-playbook-email-crm-superreal-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Channel Playbook -- Email / CRM
Source: https://github.com/Superreal-io/maia-campaign-skills/tree/main/channel-playbook-email
Command: npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill channel-playbook-email-crm-superreal-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Marketing teams producing CRM email campaigns often overload pieces with competing messages, multiple CTAs, product grids, and generic discount language, which erodes brand perception and conversion. This playbook gives agents and marketers a single operational standard to plan, write, design, and validate email pieces before they ship. ## Core Features & Use Cases - Editorial and design principles: Enforces one dominant idea per email, a single CTA, hero-driven storytelling, scan-friendly layouts, and limits on SKUs, modules, and hero copy length. - Automatic validation rules (R01-R12): Classifies issues as RECHAZO (rejection), CORRECCION (correction), or ALERTA (warning), covering CTA count, grid placement, hero value proposition, Swap and Ventaja Personal usage, and artificial urgency. - Email type architecture and cadence rules: Defines five email types (brand, singular offer, curated catalog, personal benefit, transactional) plus contact frequency, post-purchase cooldown, and pressure-by-customer-value guidelines. - Use Case: A copywriter drafts a Movistar promotional email featuring Swap as the hero message and three different CTAs; the playbook flags R01 (multiple CTAs, rejection) and R09 (Swap as protagonist, correction) and guides the rewrite toward a single value proposition. ## Quick Start Review my draft CRM email against the channel playbook validation rules and tell me which issues require rejection, correction, or editorial justification.

Frequently Asked Questions about Channel Playbook -- Email / CRM

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a CRM email before sending it?

Check the email against the twelve automatic validation rules R01-R12, which classify issues as rejection, correction, or alert. Key checks include a single primary CTA, no product grid in the upper half, an explicit hero value proposition, and hero copy under 25 words.

How many CTAs should a marketing email have?

An email must have exactly one primary CTA, repeated at most two or three times, plus optionally one secondary exploration CTA in the lower zone. Multiple competing CTAs such as Buy, Discover, and View catalog in the same email trigger automatic rejection under rule R01.

What are the email content limits for product showcases?

An email may feature up to three highlighted products in the hero or main block, one optional secondary category, and six total SKUs. Product grids are prohibited in the upper and middle zones and may only appear compressed at the bottom as a secondary exploration area.

When should Swap be the main message of an email?

Swap should never be the hero or headline; it functions as a facilitator that resolves the objection of wanting to change devices later. Rule R09 requires correction when Swap appears as the protagonist, since the value proposition must lead and Swap explains how.

How often can I send CRM emails to the same customer?

The baseline is no more than two sends per week to the same segment, with a minimum 15-day post-purchase cooldown for similar offers. Customers who ignore three consecutive sends should receive reduced frequency or a changed approach.

What types of CRM emails does this playbook define?

Five types are defined: brand email, singular offer email, curated catalog email, personal benefit email, and transactional email. Each has its own editorial logic, product count, and CTA rules, and mixing logics from two types requires rejection or redesign.