Gmail Outreach — Buzz BD Agent

Generate Gmail API-ready outreach emails with HTML signatures and CC recipients.

5|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/buzzbysolcex/buzz-bd-agent --skill gmail-outreach-buzz-bd-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Gmail Outreach — Buzz BD Agent
Source: https://github.com/buzzbysolcex/buzz-bd-agent/tree/main/skills/gmail-outreach
Command: npx skills add https://github.com/buzzbysolcex/buzz-bd-agent --skill gmail-outreach-buzz-bd-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent or non-compliant outreach emails by enforcing the exact sender, CC list, HTML formatting, and Buzz-branded signature required for Gmail API outreach.

Core Features & Use Cases

  • Standards-compliant outreach composition: Ensures every email is sent from [email protected], CCs [email protected] and [email protected], and uses mimeType: text/html for the body.
  • Automatic HTML signature appending: Concatenates the required HTML signature block after the email body to keep branding and required details uniform.
  • Professional first-contact messaging guidance: Guides subject and tone (warm, concise, value-led) and applies constraints like keeping the first email body under 150 words and avoiding sensitive topics like listing fees or commission details.

Quick Start

Draft an outreach email to a specific prospect, then generate the HTML MIME message with the required CCs, From address, and the mandated HTML signature appended at the end.

Frequently Asked Questions about Gmail Outreach — Buzz BD Agent

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

FAQPage Schema
Why does HTML email outreach require MIME type text/html for the body content?

HTML email outreach requires using MIME type text/html for the body content. This ensures the email renders correctly and allows the automatic concatenation of the required HTML signature block.

Does Gmail outreach compliance require a specific sender identity and fixed CC list?

No, business development email outreach generated by this skill avoids sensitive topics like listing fees or commission details. It applies constraints to keep the first email body under 150 words with a value-led tone.

What is the best way to structure initial and follow-up outreach messages for prospecting?

Yes, Gmail outreach compliance requires sending from a specific sender identity and including a fixed CC list. This enforces sender policy constraints and ensures all required recipients receive the message.

How do I generate Gmail API outreach emails with required CC recipients and HTML signatures?

The best way to structure initial and follow-up outreach messages is to use a warm, concise, value-led tone. This skill guides the subject and body structure while appending the mandated HTML signature automatically.