Extract message body and headers from Gmail using message IDs.
Works with
Reads individual Gmail messages by ID and returns body content in plain text or HTML format
Optionally includes message headers (From, To, Subject, Date) in output
Supports multiple output formats (text, json) and automatically converts HTML-only messages to plain text
Handles multipart messages and base64 decoding; includes dry-run mode for testing requests
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'
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-gmail-readExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-gmail-read from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gws-gmail-read. Access via /gws-gmail-read in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
sickn33/antigravity-awesome-skills
myzy-ai/dokie-ai-ppt
sickn33/antigravity-awesome-skills
I recommend gws-gmail-read for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gws-gmail-read — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gws-gmail-read has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: gws-gmail-read is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: gws-gmail-read is focused, and the summary matches what you get after install.
gws-gmail-read has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in gws-gmail-read — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for gws-gmail-read matched our evaluation — installs cleanly and behaves as described in the markdown.
gws-gmail-read reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: gws-gmail-read is focused, and the summary matches what you get after install.
showing 1-10 of 61