gmail

Send and draft emails via the Gmail API with RFC 1342 encoding.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/uriva/p2b-skills --skill gmail-uriva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmail
Source: https://github.com/uriva/p2b-skills/tree/main/gmail
Command: npx skills add https://github.com/uriva/p2b-skills --skill gmail-uriva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of programmatically interacting with Gmail while ensuring that non-ASCII characters, such as those in Hebrew or other international languages, are correctly encoded to prevent garbled text or mojibake in email headers.

Core Features & Use Cases

  • Automated Email Dispatch: Send HTML-formatted emails directly through the Gmail API with robust character encoding.
  • Draft Management: Create and save email drafts for later review or automated follow-ups.
  • Use Case: A business agent can use this to send personalized, multi-language customer support responses or marketing communications without worrying about character corruption in the subject line.

Quick Start

Use the gmail skill to send an email to [email protected] with the subject Hello and the body content set to your message.

Frequently Asked Questions about gmail

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

FAQPage Schema
How do I automate sending emails with non-ASCII characters in Gmail?

You can automate sending emails with non-ASCII characters using the Gmail API by leveraging automated RFC 1342 encoding. This ensures proper rendering of international languages like Hebrew in email headers, preventing garbled text or mojibake.

Can I use the Gmail API to create email drafts for later review?

Yes, you can use the Gmail API to create and save email drafts for later review or automated follow-ups. This allows you to prepare HTML-formatted messages programmatically before final dispatch.

What do I need to authenticate Gmail API requests for automated messaging?

To authenticate Gmail API requests for automated messaging, you need a valid OAuth token secret. This credential is required to securely execute messaging operations and dispatch emails on your behalf.

Why does my automated email subject line show garbled text when using the Gmail API?

Garbled text or mojibake in automated email subject lines occurs when non-ASCII characters are not properly encoded. Applying RFC 1342 encoding to the Gmail API headers ensures international characters are correctly rendered.

Does this Gmail automation approach support HTML-formatted email dispatch?

Yes, this Gmail automation approach supports sending HTML-formatted emails directly through the Gmail API. It combines HTML dispatch with robust character encoding for secure multi-language messaging operations.

What is the best way to send multi-language customer support emails via the Gmail API?

The best way to send multi-language customer support emails via the Gmail API is to use a script that applies automated RFC 1342 encoding to headers. This prevents character corruption in subject lines while dispatching HTML-formatted messages.