Prismer Google Workspace
Prismer-AI/PrismerCloud
Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.
Replies to a Gmail message from the gws CLI with automatic threading, plus CC, BCC, extra recipients, attachments, HTML bodies and draft or dry-run modes.
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install googleworkspace/cli gws-gmail-reply --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gws-gmail-reply .claude/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .claude/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-replyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install googleworkspace/cli gws-gmail-reply --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gws-gmail-reply .agents/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .agents/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install googleworkspace/cli gws-gmail-reply --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gws-gmail-reply .cursor/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .cursor/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/googleworkspace/cli.git --path skills/gws-gmail-reply--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install googleworkspace/cli gws-gmail-reply --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gws-gmail-reply .gemini/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .gemini/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install googleworkspace/cli gws-gmail-replyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gws-gmail-reply .github/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .github/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add googleworkspace/cli --skill gws-gmail-reply -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install googleworkspace/cli gws-gmail-reply --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/googleworkspace/cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gws-gmail-reply .opencode/skills/gws-gmail-reply && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gws-gmail-reply" agent skill from https://github.com/googleworkspace/cli/tree/main/skills/gws-gmail-reply into .opencode/skills/gws-gmail-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gws-gmail-reply", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gws-gmail-replyReplies to a Gmail message from the gws CLI with automatic threading, plus CC, BCC, extra recipients, attachments, HTML bodies and draft or dry-run modes.
The skill wraps the gws gmail +reply command, which takes a message ID and a body. It sets the In-Reply-To, References and threadId headers by itself and quotes the original message in the reply. Optional flags change the sender alias, add To, CC and BCC recipients, attach files, which can be repeated, and treat the body as HTML, in which case the quoted block keeps Gmail's own CSS classes and inline images stay attached through cid references.
Two flags make it safer to try: --dry-run shows the request without sending it, and --draft saves the reply as a draft instead of sending, since otherwise the reply goes out immediately. Before use the agent must read the gws-shared skill for authentication, global flags and security rules, and run gws generate-skills if it is missing. Reply-all has its own +reply-all command, and the gws-gmail skill covers other mail commands.
Read from SKILL.md and the folder at commit a3768d0. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Gmail Reply via gws loads about 655 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 220 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from googleworkspace/cli at commit a3768d0, republished under its Apache-2.0 licence (© googleworkspace). 220 words, ~655 tokens.
.claude/skills/gws-gmail-reply/SKILL.md (or your agent's skills folder).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<p>, <b>, <a>, etc.) — no <html>/<body> wrapper needed.© googleworkspace, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/gws-gmail-reply of googleworkspace/cli.
Open the folder on GitHubat commit a3768d0
Gmail Reply via gws next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gmail Reply via gws this skillgoogleworkspace/cli | 31k | — | ~655 | Automated safety check: Pass | Apache-2.0 | |
| Prismer Google WorkspacePrismer-AI/PrismerCloud | 1.6k | 3 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Google Workspaceyc-software/qm | 15k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Google Workspace CLIlaude-institute/headlong | 1.2k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Email Draftingmgonto/executive-assistant-skills | 118 | — | ~2.8k | Automated safety check: Pass | None | |
| Gmail Query Syntaxprovos/ironcurtain | 613 | — | ~971 | Automated safety check: Pass | Apache-2.0 |
Prismer-AI/PrismerCloud
Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
laude-institute/headlong
Drives Google Drive, Gmail, Calendar, Sheets, Docs and Chat from the shell with the gws CLI, including its sign-in, flags, helper commands and safety rules.
mgonto/executive-assistant-skills
Draft email replies for Gonto's Gmail accounts (m@gon.to, gonto@hypergrowthpartners.com).
provos/ironcurtain
Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose.
trpc-group/trpc-agent-go
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
googleworkspace/cli
Streams new Gmail messages as NDJSON from the gws command line tool using Google Pub/Sub, with label filters, batch settings and optional per-message files.
googleworkspace/cli
Subscribes to Google Workspace events with the gws CLI and streams them as NDJSON, with flags for the target resource, event types, Pub/Sub project and output directory.
googleworkspace/cli
Forwards an existing Gmail message to new recipients from the command line with the gws CLI, with options for notes, attachments, CC, BCC and drafts.
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
googleworkspace/cli
Replies to everyone on a Gmail message through the gws CLI, with threading handled automatically, options to add or drop recipients, and a draft mode.
googleworkspace/cli
Google Drive: Upload a file with automatic metadata. An agent skill from googleworkspace/cli.
Works with
Categories
Replies to a Gmail message from the gws CLI with automatic threading, plus CC, BCC, extra recipients, attachments, HTML bodies and draft or dry-run modes. The skill wraps the gws gmail +reply command, which takes a message ID and a body. It sets the In-Reply-To, References and threadId headers by itself and quotes the original message in the reply.
Gmail Reply via gws fits situations like: replying to a specific Gmail message while keeping the thread intact; saving a reply as a draft for review before sending; replying with extra recipients or file attachments; previewing the request a reply would send with a dry run.
Run `npx skills add googleworkspace/cli --skill gws-gmail-reply -a claude-code`. Or copy the skill folder (skills/gws-gmail-reply in googleworkspace/cli) into .claude/skills/gws-gmail-reply in your project. Claude Code loads it when a task matches its description.
Run `npx skills add googleworkspace/cli --skill gws-gmail-reply -a codex`. Or copy the skill folder (skills/gws-gmail-reply in googleworkspace/cli) into .agents/skills/gws-gmail-reply in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add googleworkspace/cli --skill gws-gmail-reply -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gws-gmail-reply, .gemini/skills/gws-gmail-reply, .github/skills/gws-gmail-reply and .opencode/skills/gws-gmail-reply in your project.
SKILL.md names no scripts, command-line tools or credentials: Gmail Reply via gws is instructions for the agent only. Our summary lists: The `gws` Google Workspace CLI, authenticated for Gmail.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Gmail Reply via gws is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 655 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Gmail Reply via gws: Prismer Google Workspace (Prismer-AI/PrismerCloud, 1.6k stars), Google Workspace (yc-software/qm, 15k stars), Google Workspace CLI (laude-institute/headlong, 1.2k stars) and Email Drafting (mgonto/executive-assistant-skills, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
googleworkspace (a GitHub organization) maintains it in googleworkspace/cli, which has 31,265 GitHub stars. The repository holds 77 skills in this directory. The repository was last updated on October 6, 2026.
Source: googleworkspace/cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.