ワンクリックで
gws-chat
Google Chat: Manage Chat spaces and messages.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Google Chat: Manage Chat spaces and messages.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Deploy and verify the Bella Sláinte marketing site (BellaSlainteSite) on Vercel. Use when deploying bellaslainte.com, shipping site HTML changes, checking if the site is live, fixing blocked Vercel deploys, linking GitHub to Vercel for haberlah/david-6804, or running vercel CLI against project-iw363. Triggers: "deploy the website", "ship BellaSlainteSite", "push site to prod", "is bellaslainte.com live", "Vercel blocked", "redeploy marketing site", /vercel-bellaslainte-site.
This skill should be used whenever a task involves creating, changing, or granting access to any GCP resource — creating a project, adding or modifying an IAM binding or role grant, provisioning a secret, KMS key, or CMEK, enabling an API, changing an org policy, or touching networking, folders, or service accounts. It enforces that every such write happens through FAST (Fabric Automation and Scalability Toolkit / Cloud Foundation Fabric) YAML plus Terraform plus a reviewed PR against the foundations repo, never via ad-hoc `gcloud` commands or GCP Console clicks — including when the request is phrased as "quickly," "just for now," "as a one-off," or "to unblock." Also use this skill when asked to bring an already-existing (brownfield) GCP resource under Terraform management, or when reviewing whether a proposed GCP change is safe to apply directly. Read-only/diagnostic GCP requests (describing a project, listing IAM bindings, checking quota, viewing Console screens) do not need this skill.
Use whenever working on BellaAssist (Bella Assist) product, runtime, schema, API, AI skills, auth/RLS, CRM integration, ops, compliance registers, or architecture documentation — including phrases like "architecture pack", "arch-pack", "arch pack", "current-state docs", "how does X work in Bella", "endpoint inventory", "schema inventory", or "before coding BellaAssist". Routes agents to the BellaAssist architecture-pack for business logic maps, schemas, and generated inventories, and enforces the regenerate → validate → snapshot-sync loop. Also use when updating docs after a BellaAssist behaviour change, checking documentation drift, or deciding which regression tests to run.
Operate David's Jira Cloud (bellaslainte.atlassian.net) from the terminal with the official Atlassian CLI `acli`. Use whenever the task involves reading or writing a Jira board/project, creating/editing/transitioning/deleting work items, populating a Kanban board (e.g. from a Google Sheet), running JQL searches, or installing/authenticating acli. Captures the non-obvious gotchas: search defaults to 30 results, create-bulk caps at 50 and silently drops labels + ignores description in JSON, edit --labels appends, and the KAN board's columns are Idea/In Progress/Done.
How to authenticate and operate the AWS CLI for David's Bella Slainte AWS account (571573791861), and how to manage AWS API keys / IAM / IAM Identity Center. Use whenever the task involves running AWS CLI commands, logging in to AWS or refreshing AWS credentials, creating or rotating API keys / IAM access keys / Bedrock API keys, adding or auditing IAM Identity Center (SSO) users and permission sets, or any AWS console/CLI administration. Covers the SSO login gotchas (portal username is "David" not his email; the `aws configure sso` region prompt loops).
Review GitHub pull requests against a configurable AI review policy for Codex and Claude Code. Use before creating, triggering, checking, re-running, or summarizing PR reviews; when deciding between @codex review and @claude review once; when inspecting bot review results, GitHub checks, branch protection, CODEOWNERS, or merge readiness; and when verifying whether generic thumbs-up/no-findings review text actually means the review bot ran.
| name | gws-chat |
| description | Google Chat: Manage Chat spaces and messages. |
| metadata | {"version":"0.22.5","openclaw":{"category":"productivity","requires":{"bins":["gws"]},"cliHelp":"gws chat --help"}} |
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws chat <resource> <method> [flags]
| Command | Description |
|---|---|
+send | Send a message to a space |
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.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.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 in Import 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 a 404 NOT_FOUND error. 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.findGroupChats — Developer Preview: Returns all spaces with spaceType == GROUP_CHAT, whose human memberships contain exactly the calling user, and the users specified in FindGroupChatsRequest.users. Only members that have joined the conversation are supported. For an example, see Find group chats.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 the displayName field and receive the error message ALREADY_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, set use_admin_access to true. 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 appropriate membership.member.name. To add a human user, use users/{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' resourcesections — Operations on the 'sections' resourcespaces — Operations on the 'spaces' resourceBefore 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.