grailautomation/gws-gmail-reply-all
google-workspace/skills/gws-gmail-reply-all/SKILL.md
Gmail: Reply-all to a message via the gws CLI. Use when the user asks to "reply all".
tools
Updated Apr 5, 2026
$ install --global
skillsauthnpx skillsauth add grailautomation/claude-plugins gws-gmail-reply-allInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 3:34 PM85.1s1 file scanned
SKILL.md
- name:
- gws-gmail-reply-all
- description:
- >-
- Gmail:
- Reply-all to a message via the gws CLI. Use when the user asks to "reply
gmail +reply-all
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Reply-all to a message (handles threading automatically)
Usage
gws gmail +reply-all --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 |
| --cc | — | — | Additional CC email address(es), comma-separated |
| --bcc | — | — | BCC email address(es), comma-separated |
| --remove | — | — | Exclude recipients from the outgoing reply (comma-separated emails) |
| --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 |
Examples
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Sounds good to me!'
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Updated' --remove [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Adding Eve' --cc [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Adding Dave' --to [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Reply' --bcc [email protected]
gws gmail +reply-all --message-id 18f1a2b3c4d --body '<i>Noted</i>' --html
Tips
- Replies to the sender and all original To/CC recipients.
- Use --to to add extra recipients to the To field.
- Use --cc to add new CC recipients.
- Use --bcc for recipients who should not be visible to others.
- Use --remove to exclude recipients from the outgoing reply, including the sender or Reply-To target.
- The command fails if no To recipient remains after exclusions and --to additions.
See Also
- gws-shared — Global flags and auth
- gws-gmail — All send, read, and manage email commands
Related Skills
grailautomation/workato-recipe
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jul 5, 2026
grailautomation/staff-plan-review
databases
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jul 5, 2026
grailautomation/tasks
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jul 5, 2026
grailautomation/specify
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jul 5, 2026