hermes - 💡(How to fix) Fix productivity/google-workspace: CLI wrapper missing attachment download

Summary

The bundled productivity/google-workspace skill exposes a clean CLI for search, list, get-message, and send via scripts/google_api.py, but does not surface attachment download. Reading an email with attachments via the agent leaves it stuck — it tries to download via the CLI, finds no verb, and either falls back to ad-hoc Python or loops on the missing capability.

Reproduction

1. Set up the skill normally (run setup.py, complete OAuth flow).
2. Ask the agent (via any gateway — Slack/Telegram) to read or summarize an email that has attachments.
3. Agent finds the message, identifies attachments in the payload, then has no skill-provided way to fetch them.

Where the gap is

The CLI wrapper at skills/productivity/google-workspace/scripts/google_api.py does not expose any verb for gmail.users().messages().attachments().get(...). Other operations (search, list, get-message, send, labels) are present.

The underlying google-api-python-client library fully supports attachment fetch — the gap is purely in the skill's CLI surface.

Suggested fix

Add a verb such as:

gmail attachment get <message_id> <attachment_id> <output_path>

Implementation outline:

msg = gmail.users().messages().get(userId='me', id=msg_id, format='full').execute()
# walk parts to map attachment_id → filename/mimeType for discoverability
att = gmail.users().messages().attachments().get(
    userId='me', messageId=msg_id, id=attachment_id
).execute()
data = base64.urlsafe_b64decode(att['data'])
Path(output_path).write_bytes(data)

A companion gmail attachment list <message_id> returning [{attachment_id, filename, mime_type, size_bytes}, ...] would help the agent discover attachment IDs without reading the full message payload twice.

Why this matters

The SKILL.md actively encourages searches like has:attachment filename:pdf newer_than:7d — but once the agent finds attachment-bearing emails, there's no skill-supported next step. Operationally this means the agent either fabricates a download path or asks the user to fetch manually from the Gmail UI.

Workarounds users have today

• Tell the agent in user-memory to skip attachments and summarize body only.
• Have the agent write ad-hoc Python using the library directly. Works but bypasses the skill's CLI contract and isn't reproducible across sessions.

Happy to send a PR if interested.