Google Chat

**Judgment:** This skill is a solid, practical integration for sending messages into Google Chat, well-suited for CI/CD notifications, ops alerts, and scripted workflows. It focuses on outbound messaging (no event handling) but covers the core needs for posting messages into spaces and DMs. **Key strengths:** - Clear support for both **webhook-based** and **OAuth-based** messaging, with good examples for each. - Handles common needs like **threaded messages**, **space listing**, DM targeting (with existing space IDs), and **card-style rich messages**. - Uses official Google Chat API libraries and documented OAuth scopes. **Risks and limitations:** - **Secret handling risk:** Webhook URLs, OAuth credentials, and tokens are stored in local files; users must ensure they are managed securely (e.g., environment variables, secret managers, restricted file permissions) to avoid credential leakage. - **Workspace and API constraints:** Corporate Google Workspace policies or disabled Chat APIs can block OAuth flows or message delivery; DMs cannot be created by email and require pre-existing space IDs. - **Operational robustness:** The examples do not mention retries, backoff, or structured error handling, so reliability under transient network/API failures is left to the user’s surrounding tooling. **Recommended scenarios:** - Teams wanting a straightforward way to push **deployment or monitoring notifications** into Google Chat from scripts or CI/CD jobs. - Engineering orgs that need **dynamic routing** of notifications to different spaces at runtime using OAuth. - Workflows that occasionally need **targeted user pings** in Chat (via existing DM spaces) or **richer status messages** via cards, without building a full Chat app or bot infrastructure.