Gmail: Read a message and extract its body or headers.
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Read a message and extract its body or headers
gws gmail +read --id <ID>
| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| --id | ✓ | — | The Gmail message ID to read |
| --headers | — | — | Include headers (From, To, Subject, Date) in the output |
| --format | — | text | Output format (text, json) |
| --html | — | — | Return HTML body instead of plain text |
| --dry-run | — | — | Show the request that would be sent without executing it |
gws gmail +read --id 18f1a2b3c4d
gws gmail +read --id 18f1a2b3c4d --headers
gws gmail +read --id 18f1a2b3c4d --format json | jq '.body'
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/gws-gmail-read · pinned to the source commit
git clone https://github.com/googleworkspace/cli.git
cd cli
git checkout a3768d0e82ad83cca2da97724e46bea4ff0e6dbd
mkdir -p ".claude/skills/gws-gmail-read"
cp -r "skills/gws-gmail-read" ".claude/skills/gws-gmail-read"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit a3768d0e82ad. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b