extension-email-raw

Send emails with separate to, cc, and bcc lists via sendRawEmail.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/caffeinelabs/skills --skill extension-email-raw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extension-email-raw
Source: https://github.com/caffeinelabs/skills/tree/main/skills/extension-email-raw
Command: npx skills add https://github.com/caffeinelabs/skills --skill extension-email-raw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables sending a single email to multiple recipients while allowing separate TO, CC, and BCC lists, preserving privacy and avoiding bulk‑service exposure.

Core Features & Use Cases

  • Multi‑Recipient Support: Specify up to 50 total addresses across to, cc, and bcc fields.
  • Consistent Content: All recipients receive the same email body and subject.
  • Use Case: Send meeting reminders or notifications where each participant should see only the relevant address lists.

Quick Start

Use the email-raw skill to send a raw email specifying the to, cc, and bcc addresses.

Frequently Asked Questions about extension-email-raw

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

FAQPage Schema
How do I send an email to multiple recipients with separate TO, CC, and BCC lists?

To send an email to multiple recipients, use the sendRawEmail function to specify up to 50 addresses across separate TO, CC, and BCC fields, ensuring privacy between address lists while delivering the same content.

What is the maximum number of recipients I can include in a single raw email?

The maximum number of recipients for a single raw email is 50 total addresses. You can distribute these across the TO, CC, and BCC fields according to your notification requirements.

Can I use BCC to send meeting reminders without exposing recipient addresses to others?

You can use BCC fields for meeting reminders to hide recipient addresses. This ensures each participant sees only the relevant address lists while receiving the same email body and subject.

Does sending raw email with multi-recipient CC and BCC require a bulk email service?

Sending raw email with CC and BCC does not require a bulk email service. It uses the caffeineai-email backend to send notifications directly, avoiding bulk-service exposure while preserving address list privacy.

When should I use separate TO, CC, and BCC fields instead of a standard email send?

You should use separate TO, CC, and BCC fields when sending notifications or meeting reminders where participants need the same content but the address lists require privacy between each other.

Are there limitations when sending multi-recipient emails with TO, CC, and BCC?

The limitation is a maximum of 50 total recipients per email. All recipients receive the same subject and body, and the privacy between address lists is maintained through the separate TO, CC, and BCC fields.