add-gmail
Skill0 starsChanged 6 months agoMITView on GitHub
Add Gmail as an inbox feeder to COS. Reads unread emails via Gmail MCP tools during sweep — no shell script, no credentials to manage.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- juancruzmunozalbelo/swarmclawtheir own version, first seen Oct 8, 2026
- Runchuan-BU/BioClawtheir own version, first seen Aug 2, 2026
- DingyangLyu/MatClawtheir own version, first seen Mar 17, 2026
- breakcafe/picoclawtheir own version, first seen Mar 6, 2026
- jaypyles/nanoclaw-discordtheir own version, first seen Feb 8, 2026
Used with
Projects with it also use add-voice-transcription and add-telegram-swarm.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 4 projects that use this
juancruzmunozalbeloSkilladd-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 4 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Runchuan-BU/BioClaw★ 405same name
- DingyangLyu/MatClaw★ 98same name
- jaypyles/nanoclaw-discord★ 2same name
- breakcafe/picoclaw★ 1same name
- juancruzmunozalbelo/swarmclaw★ 1same 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 repository3 other files it gives its agents.
- claude.mdCLAUDE.md
- add-draftsSkill
- add-telegramSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Look for Step 0.5c — Gmail fetch: in .claude/commands/sweep.md.
- Distinctive: line 25
Add Gmail MCP check after the Calendar MCP block in the Integration Check section
- Very specific: line 40
Run /sweep. The integration check should show ✓ Gmail — {email} connected.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Gmail Channel (COS)
COS is a pure Markdown vault with no app server. This skill adds Gmail support via MCP tool calls that Claude executes directly during sweep. No bot token, no shell script, no daemon — the Gmail MCP is already authenticated.
Phase 1: Pre-flight
Check if already applied
Look for Step 0.5c — Gmail fetch: in .claude/commands/sweep.md. If it exists, skip to Phase 3 (configuration).
Check Gmail MCP is available
The Gmail MCP must already be authenticated and available. Verify by calling gmail_get_profile — if it returns your email address, you're ready.
Phase 2: Apply
- Idempotency check — if
Step 0.5c — Gmail fetch:already exists in.claude/commands/sweep.md, skip to Phase 3. - Create state file — if
context/gmail-state.jsonis missing, create it with content:{"last_processed": null} - Patch sweep.md — using content from
modify/commands/sweep.md:- Add Gmail MCP check after the Calendar MCP block in the Integration Check section
- Insert Step 0.5c before Step 1
Phase 3: Verify
Check state file
cat context/gmail-state.jsonExpected: {"last_processed": null} (null on first run = fetch last 24h).
Run sweep
Run /sweep. The integration check should show ✓ Gmail — {email} connected. Step 0.5c should create inbox/gm-*.md files for any unread mail in scope.
Behavior
- First run: Fetches all unread mail from the last 24 hours (configurable via search filter).
- Subsequent runs: Fetches mail received after
last_processedtimestamp. - State file (
context/gmail-state.json) is updated tonowat the end of each Gmail fetch. - Email body is capped at ~2000 chars in the inbox file. Full thread available via
gmail_read_threadif needed. - Read-only: Emails are never marked as read, archived, or modified in any way.
Troubleshooting
Gmail MCP unavailable
The Gmail MCP must be configured and authenticated in your Claude environment. Check your MCP server settings if gmail_get_profile errors.
Step 0.5c not in sweep.md
Re-invoke /add-gmail. Phase 2 is idempotent — safe to run multiple times.
Duplicate files on repeated sweeps
The last_processed timestamp in context/gmail-state.json prevents this. If you suspect drift, check the file and adjust the timestamp manually.
Reset to fetch last 24h again
python3 -c "import json; f=open('context/gmail-state.json','r+'); d=json.load(f); d['last_processed']=None; f.seek(0); json.dump(d,f,indent=2); f.truncate()"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.

