Agent skill

Gmail Manager

Expert Gmail management assistant via Rube MCP. An agent skill from CraftOS-dev/CraftBot.

MITAuto-check passedProductivity & Automation

Install Gmail Manager

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gmail-manager .claude/skills/gmail-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .claude/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gmail-manager .agents/skills/gmail-manager && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .agents/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gmail-manager .cursor/skills/gmail-manager && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .cursor/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/CraftOS-dev/CraftBot.git --path skills/gmail-manager

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gmail-manager .gemini/skills/gmail-manager && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .gemini/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gmail-manager .github/skills/gmail-manager && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .github/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot gmail-manager --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gmail-manager .opencode/skills/gmail-manager && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gmail-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/gmail-manager into .opencode/skills/gmail-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gmail-manager", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gmail-manager
GitHub stars: 392
Token cost: ~2.3k tokens
SKILL.md length: 536 words
Files: 3
Skills in repo: 89
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Expert Gmail management assistant via Rube MCP. An agent skill from CraftOS-dev/CraftBot.

Works in 6 steps: Daily Inbox Triage (Recommended 15-30… → Achieving Inbox Zero → Finding Specific Emails → …
Mentions inbox management
SKILL.md covers Core Principles, Available Rube MCP Tools, Common Workflows and Email Templates, plus 3 more sections
Needs RUBE_API_KEY

What it does

Gmail Manager is an agent skill from CraftOS-dev/CraftBot. 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.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `_meta.json`).

It sits in Productivity & Automation, covering Email management. It works with Gmail. The repository describes itself as: One agent. Every kind of work. The licence is MIT.

When your agent uses it

Mentions inbox management
Email organization
Organizing emails
Checking emails

Example prompts

“/gmail-manager”

Requirements

Python 3
A credential in RUBE_API_KEY

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Daily Inbox Triage (Recommended 15-30 min/day)
Achieving Inbox Zero
Finding Specific Emails
Sending Emails
Bulk Cleanup
Label Organization

What it can do on your machine

Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- RUBE_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gmail Manager loads about 2.3k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 536 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~85
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 536 words, ~2,336 tokens.

Download SKILL.mdSave it as .claude/skills/gmail-manager/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

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

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

Available Rube MCP Tools

Email Fetching & Reading

Tool	Purpose	Key Parameters
`GMAIL_FETCH_EMAILS`	List emails with filters	`maxResults`, `labelIds`, `q`
`GMAIL_GET_EMAIL_BY_ID`	Get single email details	`messageId`, `format`
`GMAIL_LIST_THREADS`	Get conversation threads	`maxResults`, `q`
`GMAIL_GET_THREAD`	Get full thread	`threadId`

Composing & Sending

Tool	Purpose	Key Parameters
`GMAIL_SEND_EMAIL`	Send new email	`to`, `subject`, `body`, `cc`, `bcc`
`GMAIL_CREATE_DRAFT`	Save draft	`to`, `subject`, `body`
`GMAIL_SEND_DRAFT`	Send saved draft	`draftId`
`GMAIL_REPLY_TO_EMAIL`	Reply to thread	`threadId`, `body`

Organization & Labels

Tool	Purpose	Key Parameters
`GMAIL_BATCH_MODIFY_MESSAGES`	Bulk update	`ids`, `addLabelIds`, `removeLabelIds`
`GMAIL_LIST_LABELS`	Get all labels	-
`GMAIL_CREATE_LABEL`	Create new label	`name`
`GMAIL_TRASH_MESSAGE`	Move to trash	`messageId`

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

Common Workflows

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

Goal: Process inbox to zero efficiently

Steps:

python

# 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:

Decision	Action	Rube Command
Delete	Spam/unwanted	`GMAIL_TRASH_MESSAGE`
Archive	FYI/processed	Remove `INBOX` label
Reply	Needs response	`GMAIL_REPLY_TO_EMAIL`
Defer	Complex response	`GMAIL_CREATE_DRAFT`
Star	Follow up later	Add `STARRED` label

Batch archive processed emails:

python

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

3. Finding Specific Emails

By sender:

python

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

By subject:

python

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

Recent unread with attachments:

python

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

Full thread context:

python

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

4. Sending Emails

New email:

python

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

Reply to thread:

python

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

Save draft for later:

python

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

5. Bulk Cleanup

Mark multiple as read:

python

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

Archive multiple:

python

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

Star for follow-up:

python

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

6. Label Organization

List all labels:

python

GMAIL_LIST_LABELS
  arguments: {}

Create project label:

python

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

Apply label to emails:

python

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

Show full SKILL.md (209 more words)Show less

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

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

Safety

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

Organization

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

Common Scenarios

"Check my inbox"

python

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

"Find emails from [person]"

python

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

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

python

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

"Archive all newsletters"

python

# 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"

python

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

python

# 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.

Files

SKILL.md and 2 other files in skills/gmail-manager of CraftOS-dev/CraftBot.

SKILL.md
README.md
_meta.json

Open the folder on GitHubat commit b50970c

Compare with similar skills

Gmail Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gmail Manager compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gmail Manager this skillCraftOS-dev/CraftBot	392	—	~2.3k	Automated safety check: Pass	MIT	today
Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops	74k	—	~233	Automated safety check: Notes	MIT	yesterday
Gmailteam-attention/plugins-for-claude-natives	825	—	~967	Automated safety check: Pass	MIT	5 mo ago
Connect Apps with ComposioComposioHQ/awesome-claude-skills	77k	3 repos	~557	Automated safety check: Pass	None	19 days ago
Gmail Emailopen-gitagent/gitagent	710	—	~235	Automated safety check: Notes	MIT	1 mo ago
Zeleremorses/zele	299	—	~1.3k	Automated safety check: Pass	None	6 days ago

Similar skills

Career-Ops Gmail Lead Plugin
career-ops-hq/career-ops
Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.
74k GitHub stars~233 tokensUpdated yesterday
Productivity & AutomationAuto-check: notes
Gmail
team-attention/plugins-for-claude-natives
This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail.
825 GitHub stars~967 tokensUpdated 5 mo ago
Productivity & AutomationAuto-check passed
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
77k GitHub starsUsed in 3 repos~557 tokens
Productivity & AutomationAuto-check passed
Gmail Email
open-gitagent/gitagent
Send emails via Gmail SMTP using App Password authentication.
710 GitHub stars~235 tokensUpdated 1 mo ago
Productivity & AutomationAuto-check: notes
Zele
remorses/zele
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar.
299 GitHub stars~1.3k tokensUpdated 6 days ago
Productivity & AutomationAuto-check passed
Google Workspace
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
15k GitHub stars~1.8k tokensUpdated yesterday
Productivity & AutomationAuto-check passed

Questions about Gmail Manager

What does Gmail Manager do?

Expert Gmail management assistant via Rube MCP. An agent skill from CraftOS-dev/CraftBot. Gmail Manager is an agent skill from CraftOS-dev/CraftBot. Expert Gmail management assistant via Rube MCP.

When should I use Gmail Manager?

Gmail Manager fits situations like: mentions inbox management; email organization; organizing emails; checking emails.

How do I install Gmail Manager in Claude Code?

Run `npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a claude-code`. Or copy the skill folder (skills/gmail-manager in CraftOS-dev/CraftBot) into .claude/skills/gmail-manager in your project. Claude Code loads it when a task matches its description.

How do I install Gmail Manager in Codex?

Run `npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a codex`. Or copy the skill folder (skills/gmail-manager in CraftOS-dev/CraftBot) into .agents/skills/gmail-manager in your project. Codex loads it when a task matches its description.

Can I use Gmail Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CraftOS-dev/CraftBot --skill gmail-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gmail-manager, .gemini/skills/gmail-manager, .github/skills/gmail-manager and .opencode/skills/gmail-manager in your project.

What does Gmail Manager need to run?

Going by SKILL.md and its folder, Gmail Manager needs credentials named RUBE_API_KEY. Our summary lists: Python 3; A credential in RUBE_API_KEY.

Does Gmail Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gmail Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gmail Manager use?

Gmail Manager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gmail Manager use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gmail Manager?

Skills that share tags, products or a category with Gmail Manager: Career-Ops Gmail Lead Plugin (career-ops-hq/career-ops, 74k stars), Gmail (team-attention/plugins-for-claude-natives, 825 stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars) and Gmail Email (open-gitagent/gitagent, 710 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gmail Manager?

CraftOS-dev (a GitHub user) maintains it in CraftOS-dev/CraftBot, which has 392 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 7, 2026.

Source: CraftOS-dev/CraftBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gmail Manager

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Gmail Management Expert Skill

Core Principles

Available Rube MCP Tools

Email Fetching & Reading

Composing & Sending

Organization & Labels

Search Queries (q parameter)

Common Workflows

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

2. Achieving Inbox Zero

3. Finding Specific Emails

4. Sending Emails

5. Bulk Cleanup

6. Label Organization

Email Templates

Cold Outreach

Follow-up

Quick Reply

Best Practices

Productivity

Safety

Organization

Common Scenarios

"Check my inbox"

"Find emails from [person]"

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

"Archive all newsletters"

"Mark everything as read"

Integration Notes

Rube MCP Connection

Tool Call Format

Error Handling

Remember

Files

Compare with similar skills

Similar skills

More from CraftOS-dev/CraftBot

Related

Questions about Gmail Manager