gws-events

googleworkspace/cli · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/googleworkspace/cli --skill gws-events
0 commentsdiscussion
summary

Real-time event streaming and subscription management for Google Workspace.

  • Provides three core resource types: subscriptions (create, list, get, delete, patch, reactivate), operations (poll long-running tasks), and message/task streaming for real-time event delivery
  • Includes helper commands for subscribing to Workspace events as NDJSON streams and renewing suspended subscriptions
  • Requires Google Workspace authentication and the gws binary; use gws schema to inspect method parameters
skill.md

events (v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws events <resource> <method> [flags]

Helper Commands

Command Description
+subscribe Subscribe to Workspace events and stream them as NDJSON
+renew Renew/reactivate Workspace Events subscriptions

API Resources

message

  • stream — SendStreamingMessage is a streaming call that will return a stream of task update events until the Task is in an interrupted or terminal state.

operations

  • get — Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.

subscriptions

tasks

  • cancel — Cancel a task from the agent. If supported one should expect no more task updates for the task.
  • get — Get the current state of a task from the agent.
  • subscribe — TaskSubscription is a streaming call that will return a stream of task update events. This attaches the stream to an existing in process task. If the task is complete the stream will return the completed task (like GetTask) and close the stream.
  • pushNotificationConfigs — Operations on the 'pushNotificationConfigs' resource

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws events --help

# Inspect a method's required params, types, and defaults
gws schema events.<resource>.<method>

Use gws schema output to build your --params and --json flags.

how to use gws-events

How to use gws-events on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add gws-events
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/googleworkspace/cli --skill gws-events

The skills CLI fetches gws-events from GitHub repository googleworkspace/cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/gws-events

Reload or restart Cursor to activate gws-events. Access the skill through slash commands (e.g., /gws-events) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.434 reviews
  • Kiara Park· Dec 16, 2024

    Registry listing for gws-events matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Shikha Mishra· Dec 12, 2024

    gws-events has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Daniel Li· Dec 4, 2024

    Useful defaults in gws-events — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Daniel Srinivasan· Nov 23, 2024

    I recommend gws-events for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Gill· Nov 15, 2024

    gws-events has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Maya Chen· Nov 7, 2024

    Solid pick for teams standardizing on skills: gws-events is focused, and the summary matches what you get after install.

  • Kiara Malhotra· Oct 26, 2024

    We added gws-events from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Anaya Zhang· Oct 14, 2024

    gws-events reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mateo Rao· Oct 6, 2024

    Keeps context tight: gws-events is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Amelia Abebe· Sep 21, 2024

    Registry listing for gws-events matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 34

1 / 4