plugins/google-workspace-cli/skills/chat/SKILL.md
Use this skill when the user asks about Google Chat operations like sending messages, managing spaces, or listing conversations via the Google Workspace CLI.
npx skillsauth add nsheaps/ai-mktpl chatInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use gws chat to interact with Google Chat from the command line.
# List spaces
gws chat spaces list
# Get space details
gws chat spaces get <space-name>
# Create a space
gws chat spaces create --display-name "Project Alpha" --type "ROOM"
# List members of a space
gws chat spaces members list <space-name>
# List messages in a space
gws chat messages list <space-name>
# Send a message to a space
gws chat messages create <space-name> --text "Hello team!"
# Send a message with formatting
gws chat messages create <space-name> --text "*Bold* and _italic_ text"
# Reply to a thread
gws chat messages create <space-name> --text "Reply here" --thread <thread-name>
# Get a specific message
gws chat messages get <message-name>
# Update a message
gws chat messages update <message-name> --text "Updated message"
# Delete a message
gws chat messages delete <message-name>
# Add a reaction
gws chat messages reactions create <message-name> --emoji "thumbsup"
# List reactions
gws chat messages reactions list <message-name>
| Type | Description |
| ---------------- | ------------------------ |
| ROOM | Named space with threads |
| GROUP_CHAT | Group direct message |
| DIRECT_MESSAGE | 1:1 direct message |
spaces/<space-id>spaces/<space-id>/messages/<message-id>--format json for machine-readable outputtools
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
tools
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
tools
Manages spec files for requirements capture and validation
tools
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su