Gws Chat Send
Post plain-text updates from your coding agent into a Google Chat space using the gws CLI after auth is set up.
Overview
gws-chat-send is an agent skill for the Build phase that sends plain-text messages to a Google Chat space through the gws `chat +send` CLI.
Install
npx skills add https://github.com/googleworkspace/cli --skill gws-chat-sendWhat is this skill?
- Sends plain-text messages with `gws chat +send --space <NAME> --text <TEXT>`
- Documents 2 required flags (`--space`, `--text`) plus a copy-paste bash example
- Write command: agent must confirm with the user before executing
- Use `gws chat spaces list` to resolve space resource names (e.g. spaces/AAAA…)
- Depends on gws-shared for auth, global flags, and security rules (metadata version 0.22.5)
- 2 required CLI flags: --space and --text
- Documented as a write command requiring user confirmation
Adoption & trust: 16.2k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need your agent to notify a Google Chat space but do not want to hand-roll OAuth and Chat API calls for a simple text post.
Who is it for?
Solo builders who already use gws for Google Workspace and want one-line agent notifications into a known Chat space.
Skip if: Rich cards, threaded replies, or unattended bulk sends without user approval—use the raw Chat API or extend beyond this command.
When should I use this skill?
User or agent needs to send plain-text to a Google Chat space via `gws chat +send` with space name and text.
What do I get? / Deliverables
After you confirm the write, the agent runs `gws chat +send` with the correct space resource name and message text, delivering a plain-text Chat message.
- Plain-text message delivered to the specified Google Chat space
Recommended Skills
Journey fit
The skill is a thin Google Chat API integration invoked during development and agent workflows, so Build is the canonical shelf for wiring workspace messaging into your stack. Integrations is where third-party CLIs and APIs—here Google Workspace Chat via gws—are documented for agent-driven automation.
How it compares
Use instead of ad-hoc Google Chat REST scripts when you standardize workspace automation on the gws CLI.
Common Questions / FAQ
Who is gws-chat-send for?
It is for solo and indie builders using coding agents with the gws CLI who need to push short text updates into Google Chat during build, ship, or ops workflows.
When should I use gws-chat-send?
Use it when you have a space resource name and plain text to post—e.g. integration smoke tests in Build, release notes at Launch, or on-call pings in Operate—after reading gws-shared for auth and confirming the write with the user.
Is gws-chat-send safe to install?
It automates a write to Google Chat and requires network access and workspace credentials via gws; review the Security Audits panel on this Prism page and only confirm sends you intend.
Workflow Chain
Requires first: gws shared
Then invoke: gws chat
SKILL.md
READMESKILL.md - Gws Chat Send
# chat +send > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Send a message to a space ## Usage ```bash gws chat +send --space <NAME> --text <TEXT> ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--space` | ✓ | — | Space name (e.g. spaces/AAAA...) | | `--text` | ✓ | — | Message text (plain text) | ## Examples ```bash gws chat +send --space spaces/AAAAxxxx --text 'Hello team!' ``` ## Tips - Use 'gws chat spaces list' to find space names. - For cards or threaded replies, use the raw API instead. > [!CAUTION] > This is a **write** command — confirm with the user before executing. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-chat](../gws-chat/SKILL.md) — All manage chat spaces and messages commands