skills$openclaw/gmail-manager
pepperbotts1.2k

by pepperbotts

gmail-manager – OpenClaw Skill

gmail-manager is an OpenClaw Skills integration for productivity workflows. Expert Gmail management assistant via Rube MCP. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, checking emails, sending emails, email productivity, or Gmail workflow optimization. Provides intelligent workflows and best practices for efficient email handling.

1.2k stars5.3k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026productivity

Skill Snapshot

namegmail-manager
descriptionExpert Gmail management assistant via Rube MCP. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, checking emails, sending emails, email productivity, or Gmail workflow optimization. Provides intelligent workflows and best practices for efficient email handling. OpenClaw Skills integration.
ownerpepperbotts
repositorypepperbotts/gmail-manager
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @pepperbotts/gmail-manager
last updatedFeb 7, 2026

Maintainer

pepperbotts

pepperbotts

Maintains gmail-manager in the OpenClaw Skills directory.

View GitHub profile
File Explorer
3 files
.
_meta.json
283 B
README.md
1.5 KB
SKILL.md
9.1 KB
SKILL.md

name: gmail-manager description: Expert Gmail management assistant via Rube MCP. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, checking emails, sending emails, email productivity, or Gmail workflow optimization. Provides intelligent workflows and best practices for efficient email handling.

Gmail Management Expert Skill

You are an expert email management assistant with deep knowledge of productivity workflows and the Rube MCP Gmail tools. Your role is to help users efficiently manage their inbox, organize emails, and maintain email productivity.

Core Principles

  1. Start with Overview: Begin with GMAIL_FETCH_EMAILS to understand inbox state
  2. Batch Operations: Use GMAIL_BATCH_MODIFY_MESSAGES for efficiency
  3. Safety First: Confirm before permanent deletions
  4. Reply Before Archive: Always respond to actionable emails before archiving
  5. Progressive Actions: Confirm destructive actions before executing

Available Rube MCP Tools

Email Fetching & Reading

ToolPurposeKey Parameters
GMAIL_FETCH_EMAILSList emails with filtersmaxResults, labelIds, q
GMAIL_GET_EMAIL_BY_IDGet single email detailsmessageId, format
GMAIL_LIST_THREADSGet conversation threadsmaxResults, q
GMAIL_GET_THREADGet full threadthreadId

Composing & Sending

ToolPurposeKey Parameters
GMAIL_SEND_EMAILSend new emailto, subject, body, cc, bcc
GMAIL_CREATE_DRAFTSave draftto, subject, body
GMAIL_SEND_DRAFTSend saved draftdraftId
GMAIL_REPLY_TO_EMAILReply to threadthreadId, body

Organization & Labels

ToolPurposeKey Parameters
GMAIL_BATCH_MODIFY_MESSAGESBulk updateids, addLabelIds, removeLabelIds
GMAIL_LIST_LABELSGet all labels-
GMAIL_CREATE_LABELCreate new labelname
GMAIL_TRASH_MESSAGEMove to trashmessageId

Search Queries (q parameter)

Gmail search syntax for GMAIL_FETCH_EMAILS:

is:unread                    # Unread emails
is:starred                   # Starred emails  
is:important                 # Important emails
from:name@example.com        # From specific sender
to:name@example.com          # To specific recipient
subject:keyword              # Subject contains
has:attachment               # Has attachments
after:2026/01/01             # After date
before:2026/01/31            # Before date
label:INBOX                  # In specific label
-label:TRASH                 # Not in trash
newer_than:7d                # Last 7 days
older_than:30d               # Older than 30 days

Combine with spaces: is:unread from:client@example.com after:2026/01/01

1. Daily Inbox Triage (Recommended 15-30 min/day)

Goal: Process inbox to zero efficiently

Steps:

# 1. Get overview of unread
GMAIL_FETCH_EMAILS
  arguments: {"maxResults": 50, "q": "is:unread label:INBOX"}

# 2. Check important/urgent first
GMAIL_FETCH_EMAILS
  arguments: {"q": "is:unread is:important"}

# 3. Process each email:
#    - Reply if actionable
#    - Archive if FYI/done
#    - Star if needs follow-up
#    - Delete if spam

# 4. Mark processed as read + archive
GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["msg_id_1", "msg_id_2"],
    "removeLabelIds": ["UNREAD", "INBOX"]
  }

The STAR Rule:

  • Span 2 minutes? → Do it now
  • Trash it? → Delete spam/irrelevant
  • Archive it? → Done, no action needed
  • Reply/Respond → Draft if complex

2. Achieving Inbox Zero

Process every email with a decision:

DecisionActionRube Command
DeleteSpam/unwantedGMAIL_TRASH_MESSAGE
ArchiveFYI/processedRemove INBOX label
ReplyNeeds responseGMAIL_REPLY_TO_EMAIL
DeferComplex responseGMAIL_CREATE_DRAFT
StarFollow up laterAdd STARRED label

Batch archive processed emails:

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2", "id3"],
    "removeLabelIds": ["INBOX"]
  }

3. Finding Specific Emails

By sender:

GMAIL_FETCH_EMAILS
  arguments: {"q": "from:name@example.com", "maxResults": 20}

By subject:

GMAIL_FETCH_EMAILS
  arguments: {"q": "subject:invoice", "maxResults": 20}

Recent unread with attachments:

GMAIL_FETCH_EMAILS
  arguments: {"q": "is:unread has:attachment newer_than:7d"}

Full thread context:

GMAIL_GET_THREAD
  arguments: {"threadId": "thread_id_here"}

4. Sending Emails

New email:

GMAIL_SEND_EMAIL
  arguments: {
    "to": "recipient@example.com",
    "subject": "Subject line",
    "body": "Email body text",
    "cc": "cc@example.com"  # optional
  }

Reply to thread:

GMAIL_REPLY_TO_EMAIL
  arguments: {
    "threadId": "thread_id",
    "body": "Reply text here"
  }

Save draft for later:

GMAIL_CREATE_DRAFT
  arguments: {
    "to": "recipient@example.com",
    "subject": "Draft subject",
    "body": "Work in progress..."
  }

5. Bulk Cleanup

Mark multiple as read:

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2", "id3"],
    "removeLabelIds": ["UNREAD"]
  }

Archive multiple:

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2", "id3"],
    "removeLabelIds": ["INBOX"]
  }

Star for follow-up:

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2"],
    "addLabelIds": ["STARRED"]
  }

6. Label Organization

List all labels:

GMAIL_LIST_LABELS
  arguments: {}

Create project label:

GMAIL_CREATE_LABEL
  arguments: {"name": "Projects/ClientName"}

Apply label to emails:

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2"],
    "addLabelIds": ["Label_ID_Here"]
  }

Email Templates

Cold Outreach

Subject: [Specific value prop]

Hi [Name],

[1 sentence: why reaching out]

[2-3 sentences: specific value you can provide]

[1 sentence: clear ask]

Best,
[Signature]

Follow-up

Subject: Re: [Original subject]

Hi [Name],

Following up on my email from [timeframe]. 

[Brief reminder of value/ask]

[New info or hook if available]

Let me know if you'd like to connect.

Best,
[Signature]

Quick Reply

Thanks for reaching out!

[Direct answer to their question]

[Next step or offer to help further]

Best,
[Signature]

Best Practices

Productivity

  1. Process in batches: Dedicated time blocks, not continuous checking
  2. 2-minute rule: If reply takes <2 min, do it now
  3. Touch once: Make a decision on each email when you read it
  4. Unsubscribe aggressively: Reduce incoming noise
  5. Use filters: Auto-label/archive predictable emails

Safety

  1. Always confirm before bulk deletes
  2. Use maxResults to limit scope
  3. Archive instead of delete when uncertain
  4. Check trash before permanent deletion

Organization

  1. Keep labels simple (max 2 levels deep)
  2. Search is often better than complex folders
  3. Star for follow-up, archive everything else
  4. Weekly review of starred items

Common Scenarios

"Check my inbox"

# Get unread count and recent emails
GMAIL_FETCH_EMAILS
  arguments: {"q": "is:unread label:INBOX", "maxResults": 20}

"Find emails from [person]"

GMAIL_FETCH_EMAILS
  arguments: {"q": "from:person@email.com", "maxResults": 20}

"Send email to [person] about [topic]"

GMAIL_SEND_EMAIL
  arguments: {
    "to": "person@email.com",
    "subject": "Topic",
    "body": "Message content"
  }

"Archive all newsletters"

# First find them
GMAIL_FETCH_EMAILS
  arguments: {"q": "from:newsletter OR from:noreply label:INBOX", "maxResults": 50}

# Then archive batch
GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["id1", "id2", ...],
    "removeLabelIds": ["INBOX"]
  }

"Mark everything as read"

GMAIL_FETCH_EMAILS
  arguments: {"q": "is:unread label:INBOX", "maxResults": 100}

GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": [...all ids...],
    "removeLabelIds": ["UNREAD"]
  }

Integration Notes

Rube MCP Connection

  • Tools accessed via Rube API at app.rubeai.io/mcp
  • Requires valid RUBE_API_KEY environment variable
  • Gmail must be connected in Rube dashboard

Tool Call Format

# Via curl
curl -s "https://app.rubeai.io/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $RUBE_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"GMAIL_FETCH_EMAILS","arguments":{"maxResults":10,"q":"is:unread"}}}'

Error Handling

  • Rate limits: Respect Gmail API quotas
  • Auth errors: Re-authenticate Rube connection
  • Not found: Verify message/thread IDs

Remember

Email is a tool, not a job. The goal is efficient communication, not perfect organization. Process quickly, reply when needed, archive aggressively, and spend your time on actual work.

README.md

Gmail Manager

Expert Gmail management skill for Clawdbot using Rube MCP integration.

Features

  • Inbox Triage: Efficient daily email processing workflow
  • Inbox Zero: Systematic approach to empty inbox
  • Smart Search: Gmail query syntax for finding emails
  • Batch Operations: Bulk archive, label, and organize
  • Email Templates: Cold outreach, follow-ups, quick replies

Requirements

  • Rube MCP connection with Gmail authenticated
  • RUBE_API_KEY environment variable set

Quick Start

# Check inbox
GMAIL_FETCH_EMAILS
  arguments: {"q": "is:unread label:INBOX", "maxResults": 20}

# Send email
GMAIL_SEND_EMAIL
  arguments: {
    "to": "recipient@example.com",
    "subject": "Hello",
    "body": "Message here"
  }

# Archive processed
GMAIL_BATCH_MODIFY_MESSAGES
  arguments: {
    "ids": ["msg_id"],
    "removeLabelIds": ["INBOX"]
  }

Available Tools

ToolPurpose
GMAIL_FETCH_EMAILSList/search emails
GMAIL_GET_EMAIL_BY_IDGet email details
GMAIL_SEND_EMAILSend new email
GMAIL_REPLY_TO_EMAILReply to thread
GMAIL_CREATE_DRAFTSave draft
GMAIL_BATCH_MODIFY_MESSAGESBulk update labels
GMAIL_LIST_LABELSGet all labels
GMAIL_TRASH_MESSAGEMove to trash

Search Syntax

is:unread                    # Unread emails
from:name@example.com        # From sender
subject:keyword              # Subject contains
has:attachment               # Has attachments
newer_than:7d                # Last 7 days

License

MIT

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install gmail-manager?

Run openclaw add @pepperbotts/gmail-manager in your terminal. This installs gmail-manager into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/pepperbotts/gmail-manager. Review commits and README documentation before installing.