Subscribe to Google Workspace events and stream them as NDJSON output.
Works with
Connects to Workspace resources (Chat spaces, Drive, Calendar, etc.) via CloudEvents types and streams events in real-time or batch mode
Supports Pub/Sub-backed subscriptions with configurable polling intervals, batch sizes, and optional auto-acknowledgment
Offers flexible output modes: stream to stdout, write individual events to files, or reuse existing subscriptions for reconnection
Includes cleanup options
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-events-subscribeExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-events-subscribe 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-events-subscribe. Access via /gws-events-subscribe 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
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
gws events +subscribe
| 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 |
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
[!CAUTION] This is a write command — confirm with the user before executing.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in gws-events-subscribe — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend gws-events-subscribe for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
gws-events-subscribe reduced setup friction for our internal harness; good balance of opinion and flexibility.
gws-events-subscribe fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
gws-events-subscribe has been reliable in day-to-day use. Documentation quality is above average for community skills.
gws-events-subscribe is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: gws-events-subscribe is focused, and the summary matches what you get after install.
We added gws-events-subscribe from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: gws-events-subscribe is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for gws-events-subscribe matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 44