Gmail logo

Gmail

Organization
hyperfx-ai
gmail

Manage Gmail end-to-end — send, reply, search, drafts, labels, attachments, and inbox organization. Use when the user wants to send or reply to email, clean up an inbox, build label systems, manage drafts, or pull attachments.

Overview

Publisherhyperfx-ai
Repositorymarketing-skills
Skill namegmail
Stars
107
Forks
21
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by hyperfx-ai on GitHub. Read the source before you install it.

Installation

Install the Gmail AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hyperfx-ai/marketing-skills/tree/main/skills/gmail
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hyperfx-ai/marketing-skills.git /tmp/marketing-skills
mkdir -p .claude/skills
cp -r /tmp/marketing-skills/skills/gmail .claude/skills/gmail
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gmail in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gmail on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gmail is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Gmail Email Management

This skill provides comprehensive guidance for managing Gmail emails, labels, and organization.

Requirements

How to run the tools in this skill

Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:

SurfaceFind a toolRun it
Hyper chatCall the tool by its name; search_tools(queries=["<provider> <action>"]) shows its parameters<name>(...)
MCP client (Claude, Cursor, Codex, ChatGPT)search("<what you want to do>"), then describe("<name>")call_read("<name>", {...}), call_write or call_destructive: the one that describe names in call_with
Hyper CLIhyperai search "<what you want to do>", then hyperai describe <name>hyperai call <name> --json '{...}'

If a tool is not found: in Hyper chat, find its toolkit id with discover_toolkits and pass it to enable_toolkit. On an MCP client or the CLI, tell the user which integration to connect in Hyper.

Label Operations - Critical Distinctions

ADD LABEL (keeps email in current location + adds new label)

  • Use: gmail_labels_add
  • Use case: Adding labels WITHOUT moving the email from its current location
  • Example: Email stays in INBOX and also gets labeled "Important"

MOVE TO LABEL (removes from INBOX + adds to target label)

  • Use: gmail_messages_move_to_label
  • Use case: Moving email OUT of inbox and INTO a specific label/folder
  • Example: Email is removed from INBOX and moved to "Archive" or "Work"
  • This performs TWO operations: removes INBOX label + adds target label

REMOVE LABEL (removes specific label)

  • Use: gmail_labels_remove
  • Use case: Removing labels from an email
  • Can remove any label including INBOX

Getting Label IDs

CRITICAL: Most Gmail label operations require label IDs, NOT label names.

  • Always call gmail_labels_list first to get available labels and their IDs
  • Label IDs look like: "Label_123", "Label_456", or system labels: "INBOX", "SENT", "TRASH"
  • Never guess or make up label IDs

Common Workflows

Email Triage/Organization

  1. Call gmail_labels_list to see available labels
  2. Call gmail_messages_list to get emails
  3. Use gmail_messages_move_to_label to move emails from INBOX to appropriate labels

Adding Categories (keep in inbox)

  1. Call gmail_labels_list to get label IDs
  2. Use gmail_labels_add to categorize emails while keeping them in INBOX

Creating New Labels

  • Use gmail_labels_create if the desired label doesn't exist
  • Returns the new label's ID for immediate use

Searching and Listing Messages

gmail_messages_list supports full Gmail search query syntax:

  • query parameter accepts the same syntax as Gmail's search box
  • Examples: "is:unread", "from:user@example.com", "has:attachment subject:invoice"
  • Combine operators: "from:user@example.com is:unread has:attachment"
  • With no query, the tool adds -in:draft. When you pass a query, add -in:draft to it yourself
  • The label parameter takes the label NAME (or INBOX, SENT, SPAM, TRASH, CATEGORY_*), not a Label_… ID. An ID is ignored with no error

Drafts Workflow

Creating and sending draft emails

  1. gmail_drafts_create - Create initial draft
  2. gmail_drafts_update - Edit existing draft (optional)
  3. gmail_drafts_send - Send the draft as email

Managing drafts

  • gmail_drafts_list - List all draft emails
  • gmail_drafts_get - Get a specific draft by ID
  • gmail_drafts_delete - Delete a draft without sending

When to use drafts vs direct send

  • Use gmail_messages_send for immediate one-step sending
  • Use the draft workflow when a person must review or edit the email before it is sent
  • To send later, pass scheduled_at="<ISO datetime>" to gmail_messages_send; a draft does not schedule

Replies

  • gmail_messages_reply(message_id=..., body=..., reply_all=False) sends a reply at once
  • gmail_drafts_create(reply_to_message_id=..., mode="reply", body=...) drafts a reply; mode is also "reply_all", or "forward" with to

Email Actions - Important Distinctions

Archive vs Trash

  • gmail_messages_archive - Removes from INBOX but keeps in "All Mail" (recoverable, not deleted)
  • gmail_messages_trash - Moves to Trash folder (will be auto-deleted after 30 days)
  • Archive is the preferred way to "clean up" inbox while keeping emails

Attachments

  • gmail_attachments_get - Download attachments from received emails
  • To attach files, pass their workspace file IDs in file_ids, not /files/... paths (files_create returns the file_id). An unknown ID is skipped with no error, so check each ID before you send

Tool Selection Quick Reference

ActionTool
Add label Xgmail_labels_add
Move to label Xgmail_messages_move_to_label
Remove from inboxgmail_messages_move_to_label (move to target) OR gmail_labels_remove (just remove INBOX)
Archive emailgmail_messages_archive (preferred for cleanup)
Delete/trash emailgmail_messages_trash
Send email nowgmail_messages_send
Send email latergmail_messages_send with scheduled_at="<ISO datetime>"
Reply nowgmail_messages_reply
Draft a reply or forwardgmail_drafts_create with reply_to_message_id

Frequently asked questions

What does the Gmail AI skill do?

Manage Gmail end-to-end — send, reply, search, drafts, labels, attachments, and inbox organization. Use when the user wants to send or reply to email, clean up an inbox, build label systems, manage drafts, or pull attachments.

Why use Gmail on TypingMind?

Because you install it once and use it with any model. Gmail is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gmail in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hyperfx-ai/marketing-skills/tree/main/skills/gmail. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gmail?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gmail?

As many as you like. As long as a model supports skills, you can use Gmail with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gmail AI skill free?

Yes. It is published on GitHub by hyperfx-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇