gws-chat▌
googleworkspace/cli · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Manage Google Chat spaces, messages, custom emojis, and media through API commands.
- ›Access 10+ API resources including spaces, messages, members, custom emojis, and media with create, read, update, delete, and search operations
- ›Create and manage spaces with initial members, find or list direct messages, and handle space imports and deletion
- ›Upload and download media attachments, and manage custom emojis (Google Workspace only, requires admin enablement)
- ›Requires gws binary and aut
chat (v1)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws chat <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+send |
Send a message to a space |
API Resources
customEmojis
create— Creates a custom emoji. Custom emojis are only available for Google Workspace accounts, and the administrator must turn custom emojis on for the organization. For more information, see Learn about custom emojis in Google Chat and Manage custom emoji permissions.delete— Deletes a custom emoji. By default, users can only delete custom emoji they created. Emoji managers assigned by the administrator can delete any custom emoji in the organization. See Learn about custom emojis in Google Chat. Custom emojis are only available for Google Workspace accounts, and the administrator must turn custom emojis on for the organization.get— Returns details about a custom emoji. Custom emojis are only available for Google Workspace accounts, and the administrator must turn custom emojis on for the organization. For more information, see Learn about custom emojis in Google Chat and Manage custom emoji permissions.list— Lists custom emojis visible to the authenticated user. Custom emojis are only available for Google Workspace accounts, and the administrator must turn custom emojis on for the organization. For more information, see Learn about custom emojis in Google Chat and Manage custom emoji permissions.
media
download— Downloads media. Download is supported on the URI/v1/media/{+name}?alt=media.upload— Uploads an attachment. For an example, see Upload media as a file attachment.
spaces
completeImport— Completes the import process for the specified space and makes it visible to users.create— Creates a space. Can be used to create a named space, or a group chat inImport mode. For an example, see Create a space.delete— Deletes a named space. Always performs a cascading delete, which means that the space's child resources—like messages posted in the space and memberships in the space—are also deleted. For an example, see Delete a space.findDirectMessage— Returns the existing direct message with the specified user. If no direct message space is found, returns a404 NOT_FOUNDerror. For an example, see Find a direct message. With app authentication, returns the direct message space between the specified user and the calling Chat app.get— Returns details about a space. For an example, see Get details about a space.list— Lists spaces the caller is a member of. Group chats and DMs aren't listed until the first message is sent. For an example, see List spaces.patch— Updates a space. For an example, see Update a space. If you're updating thedisplayNamefield and receive the error messageALREADY_EXISTS, try a different display name.. An existing space within the Google Workspace organization might already use this display name.search— Returns a list of spaces in a Google Workspace organization based on an administrator's search. In the request, setuse_admin_accesstotrue. For an example, see Search for and manage spaces.setup— Creates a space and adds specified users to it. The calling user is automatically added to the space, and shouldn't be specified as a membership in the request. For an example, see Set up a space with initial members. To specify the human members to add, add memberships with the appropriatemembership.member.name. To add a human user, useusers/{user}, where{user}can be the email address for the user.members— Operations on the 'members' resourcemessages— Operations on the 'messages' resourcespaceEvents— Operations on the 'spaceEvents' resource
users
sections— Operations on the 'sections' resourcespaces— Operations on the 'spaces' resource
Discovering Commands
Before calling any API method, inspect it:
# Browse resources and methods
gws chat --help
# Inspect a method's required params, types, and defaults
gws schema chat.<resource>.<method>
Use gws schema output to build your --params and --json flags.
How to use gws-chat on Cursor
AI-first code editor with Composer
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-chat
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gws-chat from GitHub repository googleworkspace/cli and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gws-chat. Access the skill through slash commands (e.g., /gws-chat) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★60 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
gws-chat is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Olivia Ghosh· Dec 16, 2024
We added gws-chat from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Malhotra· Dec 12, 2024
gws-chat reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mei Sethi· Dec 8, 2024
gws-chat reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Isabella Desai· Nov 27, 2024
Registry listing for gws-chat matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Nov 19, 2024
Keeps context tight: gws-chat is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Nia Martin· Nov 3, 2024
Registry listing for gws-chat matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Anaya Haddad· Oct 22, 2024
gws-chat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Harper Desai· Oct 18, 2024
gws-chat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Chaitanya Patil· Oct 10, 2024
gws-chat has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 60