domains / agent-tooling / gmail-automation / gmail-automation

gmail-automation

combined

The two copies implement the same high-level Gmail automation task through fundamentally different mechanisms. The davepoon copy is a procedure for using the Rube MCP (Composio) toolkit, requiring an MCP server connection and using specific RUBE_* and GMAIL_* tool calls. The sickn33 copy is a standalone CLI-based skill that uses local Python scripts (auth.py, gmail.py) and standalone OAuth, explicitly stating 'No MCP server required.' Because they rely on different infrastructure, authentication flows, and command structures, crowning one as the authentic procedure would hide a valid, alternative implementation. The sickn33 copy also has a specific constraint (Google Workspace only) and missing supporting files that the davepoon copy does not share.

Repositories

Repository	Path
davepoon/buildwithclaude	`plugins/all-skills/skills/gmail-automation/SKILL.md`
sickn33/agentic-awesome-skills	`plugins/agentic-awesome-skills-claude/skills/gmail-automation/SKILL.md`

Other copies

Role	Repository	Path
peer	davepoon/buildwithclaude	`plugins/all-skills/skills/gmail-automation/SKILL.md`
peer	sickn33/agentic-awesome-skills	`plugins/agentic-awesome-skills-claude/skills/gmail-automation/SKILL.md`
adapter	sickn33/agentic-awesome-skills	`plugins/agentic-awesome-skills/skills/gmail-automation/SKILL.md`
adapter	sickn33/agentic-awesome-skills	`skills/gmail-automation/SKILL.md`

Combined skill

# Gmail Automation

This skill supports two distinct implementations for automating Gmail. Choose the appropriate path based on your environment.

## Path A: Rube MCP (Composio)
Use this path if you have access to the Rube MCP server.

1. **Prerequisites**: Ensure Rube MCP is connected and `RUBE_SEARCH_TOOLS` is available.
2. **Authentication**: Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gmail`. If not ACTIVE, follow the OAuth link.
3. **Search**: Use `GMAIL_FETCH_EMAILS` with Gmail query syntax (e.g., `from:user is:unread`).
4. **Send**: Use `GMAIL_SEND_EMAIL` with `recipient_email`, `subject`, and `body`.
5. **Labels**: Use `GMAIL_BATCH_MODIFY_MESSAGES` to add/remove labels (e.g., remove `UNREAD` to mark as read).

## Path B: Standalone CLI (OAuth)
Use this path if you prefer local scripts and do not have an MCP server. **Note: Requires Google Workspace account.**

1. **Prerequisites**: Ensure `scripts/auth.py` and `scripts/gmail.py` are available locally.
2. **Authentication**: Run `python scripts/auth.py login` to authenticate via browser.
3. **Search**: Run `python scripts/gmail.py search "query"` (e.g., `"from:user is:unread"`).
4. **Send**: Run `python scripts/gmail.py send --to "user" --subject "Subj" --body "Body"`.
5. **Labels**: Run `python scripts/gmail.py modify MESSAGE_ID --remove-label UNREAD` to mark as read.

## Common Gmail Query Syntax
- `from:user@example.com`: Emails from a sender.
- `is:unread`: Unread emails.
- `subject:keyword`: Emails with keyword in subject.
- `after:YYYY/MM/DD`: Emails after a date.
- `label:name`: Emails with a specific label.

## Conflicts
- **Repository**: sickn33/agentic-awesome-skills
  - **Conflicting Step**: Requires Google Workspace account; personal Gmail is not supported. The davepoon/buildwithclaude copy does not impose this restriction.
- **Repository**: sickn33/agentic-awesome-skills
  - **Conflicting Step**: Relies on local Python scripts (`scripts/auth.py`, `scripts/gmail.py`) which are not bundled in the catalog copy. The davepoon/buildwithclaude copy relies on remote MCP tools.