gmail-attachmentlisted

# gmail-attachment — Send Gmail with attachments via google-workspace MCP ## Why this skill exists The `google-workspace` MCP runs in its own filesystem sandbox (typically `/app/app/external/servers/`). The `attachments` parameter accepts two shapes: | Shape | Status | Why | |---|---|---| | `{path: "/Users/.../file.pdf"}` | ❌ Always fails | The MCP looks for the path inside its sandbox. Host paths don't exist there. The error message ("Path does not exist") is misleading because the path *does* exist — just not where the MCP can see it. Copying to `/tmp` doesn't help — `/tmp` isn't shared either. Project-relative paths fail too. | | `{content: "<base64>", filename: "..."}` | ✅ Works | Content is sent inline; the MCP doesn't need to read host disk. | Without this skill, the natural reflex is to pass `path` (it's the documented field). It always fails, and the failure mode is misleading. This skill enforces the working route and documents the practical size envelope so you don't paste 80 KB of base64 into a tool call and watch it get truncated. ## When to use Trigger on any request that involves emailing a file: - "email this PDF to X@example.com" - "envoie ce fichier par mail à Y" - "send the report as an attachment" - "draft an email with the doc attached" Use this skill **before** reaching for `mcp__google-workspace__send_gmail_message` or `mcp__google-workspace__draft_gmail_message` directly when an attachment is involved. Do NOT use for: emails without attachments,