gws-chat
Google Chat: Manage Chat spaces and messages.
- License 许可
- MIT
- 最近更新
- 2026-10-17
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- gws-chat
- metadata
- { "version": "0.22.5", "openclaw": { "cliHelp": "gws chat --help", "category": "productivity", "requires": { "bins": [ "gws" ] } } }
- description
- Google Chat: Manage Chat spaces and messages.
03 SKILL.md 正文
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.
04 同仓库更多 Skills
security-audit
Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).
malware-analysis-reversing
Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static/dynamic binary analysis, memory forensics, and YARA detection rule authoring.
application-security-pentesting
Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST/DAST pipeline integration, secure code review, threat modeling, and defensive security posture.
oauth2-oidc-security-flows
Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.
jwt-session-management-hardening
Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256/EdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.
soc2-compliance-automation
Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI/CD security gates.