google-workspace/skills/gws-gmail-reply/SKILL.md
Gmail: Reply to a message via the gws CLI. Use when the user asks to "reply to email".
npx skillsauth add grailautomation/claude-plugins gws-gmail-replyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 |
| --cc | — | — | Additional CC email address(es), comma-separated |
| --bcc | — | — | BCC email address(es), comma-separated |
| --html | — | — | Send as HTML (quotes original with Gmail styling; treat --body as HTML) |
| --dry-run | — | — | Show the request that would be sent without executing it |
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 'Reply' --bcc [email protected]
gws gmail +reply --message-id 18f1a2b3c4d --body '<b>Bold reply</b>' --html
development
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.