Gws Gmail Send

v1.0.15

Gmail: Send an email.

0· 1.2k·18 current·20 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for googleworkspace-bot/gws-gmail-send.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Gws Gmail Send" (googleworkspace-bot/gws-gmail-send) from ClawHub.
Skill page: https://clawhub.ai/googleworkspace-bot/gws-gmail-send
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: gws
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install googleworkspace-bot/gws-gmail-send

ClawHub CLI

Package manager switcher

npx clawhub@latest install gws-gmail-send
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Gmail send) match the required binary ('gws') and the SKILL.md usage examples. Requiring the 'gws' CLI is appropriate for a CLI-based Gmail send helper.
Instruction Scope
The SKILL.md is narrowly scoped to building and running 'gws gmail +send' and documents flags, attachments, and dry-run. It does instruct the agent to read '../gws-shared/SKILL.md' for auth, global flags, and security rules — that external reference means the agent may attempt to read sibling skill files or run 'gws generate-skills' if missing. Reading that shared file is reasonable for auth guidance, but you should verify what the referenced file requires before granting access.
Install Mechanism
No install spec is present (instruction-only). Nothing is downloaded or written by the skill itself; it simply invokes an existing 'gws' binary on PATH.
Credentials
This skill declares no required environment variables, which is consistent with being a thin wrapper. However, authentication and global flags are delegated to gws-shared (external), which likely requires credentials or tokens; inspect gws-shared/SKILL.md or your gws configuration to confirm what secrets (OAuth tokens, account credentials) are used and where they are stored.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent system-wide privileges in its own metadata. The runtime will execute the 'gws' CLI as the agent; any persistence depends on that CLI, not this skill.
Assessment
This skill is a thin instruction-only wrapper around the 'gws' command-line tool for sending Gmail messages. Before installing or enabling it: (1) verify you trust the 'gws' binary on your system (check its source and how it stores credentials); (2) open the referenced ../gws-shared/SKILL.md to see what auth or tokens are required and where they are stored; (3) prefer --dry-run first to inspect the request the tool would make; (4) be cautious when allowing the agent to read files you might attach (attachments read from disk are expected behavior); and (5) confirm with users before any write/send action as the SKILL.md itself recommends.

Like a lobster shell, security has layers — review code before you run it.

Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
CLI help (from plugin)
gws gmail +send --help

Runtime requirements

Binsgws
latestvk9751k4c58z2eeanh8hmfcbh6183z0h3
1.2kdownloads
0stars
16versions
Updated 3w ago
v1.0.15
MIT-0

gmail +send

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

Send an email

Usage

gws gmail +send --to <EMAILS> --subject <SUBJECT> --body <TEXT>

Flags

FlagRequiredDefaultDescription
--toRecipient email address(es), comma-separated
--subjectEmail subject
--bodyEmail body (plain text, or HTML with --html)
--fromSender address (for send-as/alias; omit to use account default)
--attachAttach a file (can be specified multiple times)
--ccCC email address(es), comma-separated
--bccBCC email address(es), comma-separated
--htmlTreat --body as HTML content (default is plain text)
--dry-runShow the request that would be sent without executing it
--draftSave as draft instead of sending

Examples

gws gmail +send --to alice@example.com --subject 'Hello' --body 'Hi Alice!'
gws gmail +send --to alice@example.com --subject 'Hello' --body 'Hi!' --cc bob@example.com
gws gmail +send --to alice@example.com --subject 'Hello' --body '<b>Bold</b> text' --html
gws gmail +send --to alice@example.com --subject 'Hello' --body 'Hi!' --from alias@example.com
gws gmail +send --to alice@example.com --subject 'Report' --body 'See attached' -a report.pdf
gws gmail +send --to alice@example.com --subject 'Files' --body 'Two files' -a a.pdf -a b.csv
gws gmail +send --to alice@example.com --subject 'Hello' --body 'Hi!' --draft

Tips

  • Handles RFC 5322 formatting, MIME encoding, and base64 automatically.
  • Use --from to send from a configured send-as alias instead of your primary address.
  • Use -a/--attach to add file attachments. Can be specified multiple times. Total size limit: 25MB.
  • With --html, use fragment tags (<p>, <b>, <a>, <br>, etc.) — no <html>/<body> wrapper needed.
  • Use --draft to save the message as a draft instead of sending it immediately.

[!CAUTION] This is a write command — confirm with the user before executing.

See Also

Comments

Loading comments...