gws-events-subscribe
Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.
pinned to #a3768d0updated 3 months ago
Ask your AI client: “install skills/gws-events-subscribe”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/gws-events-subscribemetahub onboarded this repo on the author's behalf.
If you own github.com/googleworkspace/cli on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
29,590
Last commit
3 months ago
Latest release
published
- #agent-skills
- #ai-agent
- #automation
- #cli
- #discovery-api
- #gemini-cli-extension
- #google-admin
- #google-api
- #google-calendar
- #google-chat
- #google-docs
- #google-drive
- #google-sheets
- #google-workspace
- #oauth2
- #rust
About this skill
Pulled from SKILL.md at publish time.
PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.a3768d0· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
12 words · 81 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
20,235 chars · 16 sections · 22 code blocks
Tags / topics declared
16 total — agent-skills, ai-agent, automation, cli, discovery-api, gemini-cli-extension (+10)
README has usage / example sections
found: Installation · Quick Start
Homepage / docs URL declared
https://developers.google.com/workspace
Release history
1- releasecurrenta3768d0warn3 months ago
Contents
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Subscribe to Workspace events and stream them as NDJSON
Usage
gws events +subscribe
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--target | — | — | Workspace resource URI (e.g., //chat.googleapis.com/spaces/SPACE_ID) |
--event-types | — | — | Comma-separated CloudEvents types to subscribe to |
--project | — | — | GCP project ID for Pub/Sub resources |
--subscription | — | — | Existing Pub/Sub subscription name (skip setup) |
--max-messages | — | 10 | Max messages per pull batch (default: 10) |
--poll-interval | — | 5 | Seconds between pulls (default: 5) |
--once | — | — | Pull once and exit |
--cleanup | — | — | Delete created Pub/Sub resources on exit |
--no-ack | — | — | Don't auto-acknowledge messages |
--output-dir | — | — | Write each event to a separate JSON file in this directory |
Examples
gws events +subscribe --target '//chat.googleapis.com/spaces/SPACE' --event-types 'google.workspace.chat.message.v1.created' --project my-project
gws events +subscribe --subscription projects/p/subscriptions/my-sub --once
gws events +subscribe ... --cleanup --output-dir ./events
Tips
- Without --cleanup, Pub/Sub resources persist for reconnection.
- Press Ctrl-C to stop gracefully.
[!CAUTION] This is a write command — confirm with the user before executing.
See Also
- gws-shared — Global flags and auth
- gws-events — All subscribe to google workspace events commands
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/gws-events-subscribe