email-safety

Validate outbound email requests against CASL, cooldown, and volume limits.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/CC90210/CMO-Agent --skill email-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-safety
Source: https://github.com/CC90210/CMO-Agent/tree/main/skills/email-safety
Command: npx skills add https://github.com/CC90210/CMO-Agent --skill email-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents catastrophic reputation damage and revenue loss caused by accidental, unauthorized, or poorly formatted outbound communications from AI agents.

Core Features & Use Cases

  • Centralized Gateway: Enforces a single, mandatory path for all outbound email and outreach to ensure compliance and safety.
  • Automated Guardrails: Implements CASL compliance, strict cooldown periods, daily volume caps, and adversarial draft criticism.
  • Use Case: Before sending a marketing blast to a client list, use this Skill to run a dry-run simulation that validates the content against brand identity and cooldown rules without actually triggering an email.

Quick Start

Run the email doctor script to verify that the safety gateway is fully operational and that all outbound commands are correctly configured for your current session.

Frequently Asked Questions about email-safety

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

FAQPage Schema
How do I enforce CASL compliance and volume limits for automated AI outreach?

To enforce CASL compliance and volume limits for automated AI outreach, you must route all outbound requests through a centralized gateway. This gateway validates cooldown periods and daily caps before execution to ensure communications remain compliant.

What is a centralized email gateway and how does it prevent unauthorized outbound communications?

A centralized email gateway is a mandatory architectural path that intercepts and validates all outbound requests. It prevents unauthorized outbound communications by enforcing strict safety protocols, including adversarial draft criticism and volume limits, before any email is sent.

Can I run a dry-run simulation to test outbound email safety without actually sending messages?

Yes, you can run a dry-run simulation to test outbound email safety without sending messages. This validates your draft content against brand identity rules and cooldown periods, ensuring compliance without triggering actual emails.

How do I manage automated cooldown periods across multiple marketing brands?

Managing automated cooldown periods across multiple marketing brands requires an architectural gatekeeper to track communication channels. This gateway enforces strict cooldown rules and daily volume caps across all active brands before any outbound request is executed.

What are the limitations of relying on AI agents for direct outbound email without architectural guardrails?

Without architectural guardrails, relying on AI agents for direct outbound email risks catastrophic reputation damage and revenue loss. Poorly formatted, accidental, or unauthorized communications bypass compliance rules, leading to potential CASL violations and brand harm.

Do I need a central send gateway script to validate outbound email requests?

Yes, you need a central send gateway script to validate outbound email requests. The safety architecture requires integration with this gateway module to intercept and enforce all compliance protocols before executing any AI-driven communications.