Gmail: Reply to a message (handles threading automatically).
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)
gws gmail +reply --message-id <ID> --body <TEXT>
| 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 |
gws gmail +reply --message-id 18f1a2b3c4d --body 'Thanks, got it!'
gws gmail +reply --message-id 18f1a2b3c4d --body 'Looping in Carol' --cc carol@example.com
gws gmail +reply --message-id 18f1a2b3c4d --body 'Adding Dave' --to dave@example.com
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
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/gws-gmail-reply · pinned to the source commit
git clone https://github.com/googleworkspace/cli.git
cd cli
git checkout a3768d0e82ad83cca2da97724e46bea4ff0e6dbd
mkdir -p ".claude/skills/gws-gmail-reply"
cp -r "skills/gws-gmail-reply" ".claude/skills/gws-gmail-reply"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit a3768d0e82ad. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b