gws-gmail-reply
Gmail: Reply to a message (handles threading automatically).
pinned to #a3768d0updated 3 months ago
Ask your AI client: “install skills/gws-gmail-reply”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/gws-gmail-replymetahub onboarded this repo on the author's behalf.
If you own github.com/googleworkspace/cli on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
29,590
Last commit
3 months ago
Latest release
published
- #agent-skills
- #ai-agent
- #automation
- #cli
- #discovery-api
- #gemini-cli-extension
- #google-admin
- #google-api
- #google-calendar
- #google-chat
- #google-docs
- #google-drive
- #google-sheets
- #google-workspace
- #oauth2
- #rust
About this skill
Pulled from SKILL.md at publish time.
PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.a3768d0· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
8 words · 60 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
20,235 chars · 16 sections · 22 code blocks
Tags / topics declared
16 total — agent-skills, ai-agent, automation, cli, discovery-api, gemini-cli-extension (+10)
README has usage / example sections
found: Installation · Quick Start
Homepage / docs URL declared
https://developers.google.com/workspace
Release history
1- releasecurrenta3768d0warn3 months ago
Contents
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Reply to a message (handles threading automatically)
Usage
gws gmail +reply --message-id <ID> --body <TEXT>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--message-id | ✓ | — | Gmail message ID to reply to |
--body | ✓ | — | Reply body (plain text, or HTML with --html) |
--from | — | — | Sender address (for send-as/alias; omit to use account default) |
--to | — | — | Additional To email address(es), comma-separated |
--attach | — | — | Attach a file (can be specified multiple times) |
--cc | — | — | CC email address(es), comma-separated |
--bcc | — | — | BCC email address(es), comma-separated |
--html | — | — | Treat --body as HTML content (default is plain text) |
--dry-run | — | — | Show the request that would be sent without executing it |
--draft | — | — | Save as draft instead of sending |
Examples
gws gmail +reply --message-id 18f1a2b3c4d --body 'Thanks, got it!'
gws gmail +reply --message-id 18f1a2b3c4d --body 'Looping in Carol' --cc [email protected]
gws gmail +reply --message-id 18f1a2b3c4d --body 'Adding Dave' --to [email protected]
gws gmail +reply --message-id 18f1a2b3c4d --body '<b>Bold reply</b>' --html
gws gmail +reply --message-id 18f1a2b3c4d --body 'Updated version' -a updated.docx
gws gmail +reply --message-id 18f1a2b3c4d --body 'Draft reply' --draft
Tips
- Automatically sets In-Reply-To, References, and threadId headers.
- Quotes the original message in the reply body.
- --to adds extra recipients to the To field.
- Use -a/--attach to add file attachments. Can be specified multiple times.
- With --html, the quoted block uses Gmail's gmail_quote CSS classes and preserves HTML formatting. Use fragment tags (, <b>, <a>, etc.) — no <html>/<body> wrapper needed.
- With --html, inline images in the quoted message are preserved via cid: references.
- Use --draft to save the reply as a draft instead of sending it immediately.
- For reply-all, use +reply-all instead.
See Also
- gws-shared — Global flags and auth
- gws-gmail — All send, read, and manage email commands
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/gws-gmail-reply