WadeWarrenWadeWarren/gws-claude-plugin/skills/gws-gmail-reply-all/SKILL.md

gws-gmail-reply-all

Skill38 starsChanged 8 months agoApache-2.0View on GitHub

Gmail: Reply-all to a message (handles threading automatically).

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use --to to add extra recipients to the To field.
line 53
Very specific:
Use --cc to add new CC recipients.
line 54
Very specific:
Use --bcc for recipients who should not be visible to others.
line 55
Very specific:
Use --remove to exclude recipients from the outgoing reply, including the sender or Reply-To target.
line 56

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

gmail +reply-all

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to 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 bob@example.com
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Adding Eve' --cc eve@example.com
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Adding Dave' --to dave@example.com
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Reply' --bcc secret@example.com
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.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free