Best use case
gws-gmail is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Gmail: Send, read, and manage email.
Teams using gws-gmail should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gws-gmail/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gws-gmail Compares
| Feature / Agent | gws-gmail | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Gmail: Send, read, and manage email.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# gmail (v1) > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. ```bash gws gmail <resource> <method> [flags] ``` ## Helper Commands | Command | Description | |---------|-------------| | [`+send`](../gws-gmail-send/SKILL.md) | Send an email | | [`+triage`](../gws-gmail-triage/SKILL.md) | Show unread inbox summary (sender, subject, date) | | [`+reply`](../gws-gmail-reply/SKILL.md) | Reply to a message (handles threading automatically) | | [`+reply-all`](../gws-gmail-reply-all/SKILL.md) | Reply-all to a message (handles threading automatically) | | [`+forward`](../gws-gmail-forward/SKILL.md) | Forward a message to new recipients | | [`+read`](../gws-gmail-read/SKILL.md) | Read a message and extract its body or headers | | [`+watch`](../gws-gmail-watch/SKILL.md) | Watch for new emails and stream them as NDJSON | ## API Resources ### users - `getProfile` — Gets the current user's Gmail profile. - `stop` — Stop receiving push notifications for the given user mailbox. - `watch` — Set up or update a push notification watch on the given user mailbox. - `drafts` — Operations on the 'drafts' resource - `history` — Operations on the 'history' resource - `labels` — Operations on the 'labels' resource - `messages` — Operations on the 'messages' resource - `settings` — Operations on the 'settings' resource - `threads` — Operations on the 'threads' resource ## Discovering Commands Before calling any API method, inspect it: ```bash # Browse resources and methods gws gmail --help # Inspect a method's required params, types, and defaults gws schema gmail.<resource>.<method> ``` Use `gws schema` output to build your `--params` and `--json` flags.
Related Skills
recipe-create-gmail-filter
Create a Gmail filter to automatically label, star, or categorize incoming messages.
gws-gmail-watch
Gmail: Watch for new emails and stream them as NDJSON.
gws-gmail-triage
Gmail: Show unread inbox summary (sender, subject, date).
gws-gmail-send
Gmail: Send an email.
gws-gmail-reply
Gmail: Reply to a message (handles threading automatically).
gws-gmail-reply-all
Gmail: Reply-all to a message (handles threading automatically).
gws-gmail-read
Gmail: Read a message and extract its body or headers.
gws-gmail-forward
Gmail: Forward a message to new recipients.
gmail-automation
Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.
gmail-tools
Reading and managing Gmail emails - Sending emails with attachments - Replying to emails while maintaining thread continuity
bigmailer-automation
Automate Bigmailer tasks via Rube MCP (Composio). Always search tools first for current schemas.
Daily Logs
Record the user's daily activities, progress, decisions, and learnings in a structured, chronological format.