composio-gmail

Files (7)

• SKILL.md
• label-actions.md · references/
• pasted-link-workflow.md · references/
• reply-workflow.md · references/
• search-workflow.md · references/
• self-delivery.md · references/
• tool-map.md · references/

SKILL.md (first lines)

# Gmail via Composio

## Overview

Turn noisy email into clear summaries, action lists, and ready-to-send drafts using Composio Gmail tools through the Hermes meta-runtime (`composio_*` tools).

Load this skill for Gmail work. For pure inbox ranking requests, also load `composio:composio-gmail-inbox-triage`.

## Preferred Deliverables

- Thread briefs: latest status, decisions, open questions, next actions
- Reply/forward drafts ready to paste or send
- Inbox triage buckets (urgent / needs reply / waiting / FYI)

## Workflow Skills

| Workflow | Skill |
| --- | --- |
| Inbox triage, urgency ranking, follow-up detection | [../composio-gmail-inbox-triage/SKILL.md](../composio-gmail-inbox-triage/SKILL.md) |

## Reference Notes

| Task | Reference |
| --- | --- |
| Tool slug map + discover pattern | [references/tool-map.md](./references/tool-map.md) |
| Search planning and body-fetch strategy | [references/search-workflow.md](./references/search-workflow.md) |
| Pasted Gmail URL handling | [references/pasted-link-workflow.md](./references/pasted-link-workflow.md) |
| Reply drafting and reply-all | [references/reply-workflow.md](./references/reply-workflow.md) |
| Labels | [references/label-actions.md](./references/label-actions.md) |
| Self-delivery ("email this to me") | [references/self-delivery.md](./references/self-delivery.md) |

## Mailbox Analysis Pattern

1. `composio_status` if Gmail connection is uncertain.
2. Discover the right slug with `composio_search` ("search gmail unread inbox") rather than inventing names.
3. Prefer Gmail-native query syntax in arguments when the tool supports it (from:, newer_than:, is:unread, label:, has:attachment, in:anywhere).
4. Shortlist from message summaries before fetching full bodies.
5. Expand to thread reads only when conversation context changes the answer.
6. Summarize before mutating. Keep analysis separate from send/archive/trash/label unless explicitly requested.

## Write Safety

- Preserve recipients, subjects, quoted facts, dates, and links unless asked to change them.
- Draft by default when the user asks to reply but not explicitly to send.
- Send/archive/trash/label/move require clear user intent and `confirmed=true` on execute (unless yolo).
- Identify the intended thread before acting when multiple conversations match.

## Output Conventions

- Lead with latest status, then decisions, open questions, actions.
- State search scope and coverage ("from the most recent 15 inbox hits").
- Avoid absolute claims like "the only urgent email" unless the scan was comprehensive.
- Drafts should be concise and ready to paste.

## Example Requests

- "Summarize the latest thread with Acme and what I still owe them."
- "Draft a reply that confirms Tuesday and asks for the agenda."
- "Triage my unread inbox into urgent, waiting, and FYI."

## Light Fallback

If Gmail is disconnected or scoped to the wrong mailbox, say so and run/connect via `composio_connect` / `/composio connect gmail`.

From kamellperry/hermes-composio, MIT.

More from kamellperry/hermes-composio