domains / families / agent-tooling / gmail-automation

gmail-automation

combined

Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas. Lightweight Gmail integration with standalone OAuth authentication. No MCP server required.

When to use

• You need to search, read, or send Gmail messages from the command line without an MCP server.
• You are automating inbox workflows for a Google Workspace account.
• You want a lightweight Gmail integration backed by standalone OAuth scripts.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

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.