agentleFS
elzinkoelzinko/google-mcp-multi-account/.claude/skills/gws-gmail-reply-all/SKILL.md

gws-gmail-reply-all

Skill0 starsChanged 3 months agoMITView on GitHub

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

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --to to add extra recipients to the To field.

    line 56
  2. Very specific:

    Use --cc to add new CC recipients.

    line 57
  3. Very specific:

    Use --bcc for recipients who should not be visible to others.

    line 58
  4. Very specific:

    Use --remove to exclude recipients from the outgoing reply, including the sender or Reply-To target.

    line 59
  5. Distinctive:

    Use -a/--attach to add file attachments.

    line 61
  6. Very specific:

    Use --draft to save the reply as a draft instead of sending it immediately.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

FlagRequiredDefaultDescription
--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
--remove——Exclude recipients from the outgoing reply (comma-separated emails)

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 '<i>Noted</i>' --html
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Notes attached' -a notes.pdf
gws gmail +reply-all --message-id 18f1a2b3c4d --body 'Draft reply' --draft

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.
  • 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 (<p>, <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.

See Also

  • gws-shared — Global flags and auth
  • gws-gmail — All send, read, and manage email commands

Download now (ZIP)

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.