email

Resolve contact handles, draft .eml files, and send via SMTP.

Updated May 7, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill email-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/email
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill email-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of drafting and sending emails by resolving contact handles to emails, creating draft files for audit, and optionally sending via SMTP.

Core Features & Use Cases

  • Contact Resolution: Automatically resolves contact handles to email addresses.
  • Email Drafting: Creates draft .eml files for email audits.
  • SMTP Sending: Sends emails via SMTP if credentials are configured.
  • Use Case: Easily draft and send professional emails to team members or external contacts by simply using a handle or email address.

Quick Start

Use the email skill to draft an email to 'andrew' with the subject 'deploy check-in' and a reminder about the latest deployment.

Frequently Asked Questions about email

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

FAQPage Schema
How do I automate email drafting and sending via SMTP?

Automate email drafting and sending by generating .eml draft files for auditing and optionally transmitting them via SMTP. The workflow resolves contact handles to email addresses and requires explicit user confirmation before sending.

Can I resolve contact handles to email addresses programmatically?

Yes, contact resolution maps user handles to valid email addresses automatically. This mechanism streamlines organizational communication workflows by eliminating manual lookup before drafting or sending messages.

Does email automation require SMTP credentials to function?

SMTP credentials are only required for transmitting messages. Without configured credentials, the system still drafts emails and creates .eml files for review, ensuring auditability without sending.

What is the best way to audit automated emails before sending them?

The best way to audit emails is leveraging the draft creation feature, which outputs .eml files for review. This ensures organizational communication workflows maintain compliance through user confirmation before transmission.

Why does automated email sending require user confirmation?

Automated email sending requires user confirmation to prevent unauthorized or accidental transmissions. This safeguard ensures proper credential handling and verifies resolved contact handles before delivering messages via SMTP.

Are there limitations when using SMTP for email automation in organizational settings?

SMTP email automation is limited by credential configuration requirements and mandates user confirmation before sending. It is not suited for autonomous background delivery, focusing instead on auditable draft generation and verified transmission.