gmail-workflow
Skill1 starsChanged 46 days agoMITView on GitHub
Manage email workflows via Gmail MCP — draft outreach emails, triage inbox, manage newsletter lists, and search messages. Use when asked to 'check email', 'draft an email', 'triage inbox', 'find emails about X', or 'manage newsletter'. Do NOT use for non-Gmail email providers, calendar management, or Google Drive operations.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- workflownicojunk/claude-skillstheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- workflownicojunk/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- examples/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- skills/figma-handoff/AGENTS.mdAGENTS.md
- skills/github-pr-review/AGENTS.mdAGENTS.md
- skills/gmail-workflow/AGENTS.mdAGENTS.md
- skills/skill-compliance-checklist/AGENTS.mdAGENTS.md
- skills/skill-compliance-checklist/references/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- figma-handoffSkill
- github-pr-reviewSkill
- skill-compliance-checklistSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 6 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Use gmail_get_profile to identify the sender's address for context.
- Very specific: line 34
Use gmail_create_draft to save the email as a draft.
- Distinctive: line 36
Never send an email directly: Always save as draft and let the user send manually.
- Very specific: line 40
Use gmail_search_messages with is:unread (or a user-specified query) to fetch recent messages.
- Very specific: line 48
If the user wants to act on a message, use the appropriate tool (e.g., gmail_create_draft for a reply).
- Very specific: line 55
Use gmail_search_messages with the constructed query.
- Distinctive: line 56
If results are returned, summarise them in a table: Sender, Subject, Date, Snippet.
- Very specific: line 61
Use gmail_list_drafts to retrieve all existing drafts.
- Very specific: line 64
When updating, use gmail_create_draft with the revised content.
- Very specific: line 79
Search for recent messages from Sarah about the proposal using gmail_search_messages.
- Very specific: line 80
Read the relevant thread for context via gmail_read_thread.
- Very specific: line 86
Run gmail_search_messages with query is:unread subject:quarterly report.
- Distinctive: line 93
Read each message's content.
- Distinctive: line 95
Ask the user which messages to act on.
- Distinctive: line 99
Never send emails without explicit user confirmation: Always save as draft first.
- Distinctive: line 101
Respect privacy: Do not log, store, or summarise email content beyond the current session.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gmail Workflow Skill
Companion skill for the Gmail MCP server. Provides structured workflows for common email operations including drafting, triaging, searching, and draft management.
Available MCP Tools
This skill coordinates the following Gmail MCP tools:
gmail_search_messages— Search messages by query (supports Gmail search syntax)gmail_read_message— Read full message content by IDgmail_read_thread— Read an entire email thread by thread IDgmail_create_draft— Create a new draft emailgmail_list_labels— List all labels in the accountgmail_list_drafts— List existing draft emailsgmail_get_profile— Get the authenticated user's profile
Instructions
Drafting Emails
- Confirm the recipient, subject, and intent with the user before composing.
- Use
gmail_get_profileto identify the sender's address for context. - Compose the email body in a professional tone unless otherwise instructed.
- Use
gmail_create_draftto save the email as a draft. - Present the full draft to the user for review — include To, Subject, and Body.
- Never send an email directly. Always save as draft and let the user send manually.
Triaging Inbox
- Use
gmail_search_messageswithis:unread(or a user-specified query) to fetch recent messages. - For each message, use
gmail_read_messageto retrieve the subject, sender, and snippet. - Categorise messages into groups:
- Urgent — time-sensitive or from key contacts
- Action required — needs a reply or follow-up
- Informational — newsletters, notifications, FYI
- Low priority — marketing, promotions, automated
- Present the categorised summary to the user with recommended actions (reply, archive, label).
- If the user wants to act on a message, use the appropriate tool (e.g.,
gmail_create_draftfor a reply).
Searching Messages
- Clarify the search intent with the user — sender, subject, date range, keywords.
- Construct a Gmail search query using standard operators:
from:,to:,subject:,has:attachment,after:,before:,is:unread
- Use
gmail_search_messageswith the constructed query. - If results are returned, summarise them in a table: Sender, Subject, Date, Snippet.
- Offer to read full messages via
gmail_read_messageor threads viagmail_read_thread.
Managing Drafts
- Use
gmail_list_draftsto retrieve all existing drafts. - Present drafts with their subject, recipient, and snippet.
- Offer to update or discard drafts as needed.
- When updating, use
gmail_create_draftwith the revised content.
Error Handling
| Error | Response |
| MCP disconnected | Inform the user that the Gmail MCP server is not connected. Suggest reconnecting via the MCP configuration or restarting Claude Code. |
| Rate limits | If rate-limited by the Gmail API, wait briefly and retry. Inform the user if repeated attempts fail and suggest trying again in a few minutes. |
| No results found | Confirm the search query with the user. Suggest broadening the query (e.g., removing date filters, using partial keywords). Verify the correct account is connected via gmail_get_profile. |
| Authentication failure | Advise the user to re-authenticate the Gmail MCP server. Check that OAuth tokens are valid. |
Examples
"Draft a follow-up email to Sarah about the project proposal"
- Search for recent messages from Sarah about the proposal using
gmail_search_messages. - Read the relevant thread for context via
gmail_read_thread. - Compose a follow-up draft referencing the prior conversation.
- Save via
gmail_create_draftand present for review.
"Find all unread emails about the quarterly report"
- Run
gmail_search_messageswith queryis:unread subject:quarterly report. - Summarise results with sender, date, and snippet.
- Offer to read any specific message in full.
"Triage my inbox"
- Fetch unread messages via
gmail_search_messageswithis:unread. - Read each message's content.
- Categorise and present a prioritised summary.
- Ask the user which messages to act on.
Important
- Never send emails without explicit user confirmation. Always save as draft first.
- Always show the full draft (recipient, subject, body) before the user decides to send.
- Respect privacy. Do not log, store, or summarise email content beyond the current session.
- Do not modify or delete existing emails — this skill is for reading, searching, and drafting only.
- Verify the account via
gmail_get_profileat the start of a session to ensure the correct account is active.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

