
gws-gmail
✓ Official★ 29,400by Google · part of googleworkspace/cli
Gmail: Send, read, and manage email.
Gmail: Send, read, and manage email.
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by Google
Gmail: Send, read, and manage email.
npx skills add https://github.com/googleworkspace/cli --skill gws-gmail
Download ZIPGitHub29.4k
gmail (v1)
PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.
gws gmail [flags]
Helper Commands
Command Description
+send Send an email
+triage Show unread inbox summary (sender, subject, date)
+reply Reply to a message (handles threading automatically)
+reply-all Reply-all to a message (handles threading automatically)
+forward Forward a message to new recipients
+read Read a message and extract its body or headers
+watch Watch for new emails and stream them as NDJSON
API Resources
users
-
getProfile— Gets the current user's Gmail profile. -
stop— Stop receiving push notifications for the given user mailbox. -
watch— Set up or update a push notification watch on the given user mailbox. -
drafts— Operations on the 'drafts' resource -
history— Operations on the 'history' resource -
labels— Operations on the 'labels' resource -
messages— Operations on the 'messages' resource -
settings— Operations on the 'settings' resource -
threads— Operations on the 'threads' resource
Discovering Commands
Before calling any API method, inspect it:
# Browse resources and methods
gws gmail --help
# Inspect a method's required params, types, and defaults
gws schema gmail. .
Use gws schema output to build your --params and --json flags.
npx skills add https://github.com/googleworkspace/cli --skill gws-gmailRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.