Back to Communication & Collaboration
google-spaces-updates
google chatgoogle spacesteam updateswebhookproject managementcommunicationautomationdeveloper tools
Install this skill
npx skills add jezweb/claude-skillsWorks across Claude Code, Cursor, Codex, Copilot & Antigravity
The google-spaces-updates skill automates communication between development tasks and Google Chat Spaces. By integrating with project-specific webhooks, the tool allows AI agents to push status reports, feature completions, bug fix summaries, and architectural queries directly into a team's messaging flow. It relies on a local configuration file to manage webhook endpoints and project metadata, ensuring team visibility without leaving the command line. The system automatically gathers relevant git history and file change context to construct informative, formatted updates. This reduces manual reporting overhead by converting development milestones into structured, readable notifications that include branch status, commit logs, and deployment links, keeping stakeholders informed of progress as work occurs.
When to Use This Skill
- •Notifying the team immediately after a successful production deployment
- •Sharing technical questions or blockages with team members tagged by name
- •Announcing completion of a high-priority feature for internal review
- •Logging resolved bug tickets directly in the team's collaboration channel
How to Invoke This Skill
Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:
- “Post deployment update to team
- “Tell the team about the new feature
- “Ask the team about the auth approach
- “Update the team on my recent bug fix
- “Notify the team that the feature is ready for testing
Pro Tips
- 💡**Configure granular webhooks**: If different projects or teams require distinct update streams, set up separate webhooks for each Google Space to ensure messages go to the right audience.
- 💡**Automate update triggers**: Integrate this skill with CI/CD pipelines or specific git hooks to automatically post status updates upon successful merges, deployments, or test suite completions.
- 💡**Tailor message content**: Guide the AI to craft concise, informative messages by providing clear prompts that specify the type of information needed (e.g., "Post a short summary of today's progress including completed tasks and next steps").
What this skill does
- •Posts structured status updates to Google Chat via webhooks
- •Auto-detects current branch and recent git history for context
- •Supports multiple update types including deployment, bug fixes, and feature releases
- •Manages project-specific configurations via .claude/settings.json
- •Generates human-readable formatting using Google Chat compatible syntax
When not to use it
- ✕Sharing minor, incremental code changes or experimental WIP commits
- ✕Communicating private or highly sensitive security credentials
- ✕Sending updates for projects that lack a configured Google Chat webhook
Example workflow
- Run /google-spaces-updates setup to link the Google Chat webhook
- Finish a coding task or feature development
- Request the skill to post a status update via natural language
- Review the gathered git context and proposed message content
- Confirm the post to send the payload to the configured Space
Prerequisites
- –Google Chat Space with webhook integration enabled
- –Webhook URL obtained from the Space's Apps & integrations menu
- –Project directory write access to create the .claude/ folder
Pitfalls & limitations
- !Formatting assumes Google Chat syntax, which differs from standard Markdown
- !Messages are limited to the information available in the local git environment
- !Requires manual setup of the .claude/settings.json file for every new repository
FAQ
How do I add a new project to this system?
Run the /google-spaces-updates setup command and provide the webhook URL for your specific Google Space.
Can I use standard bold markdown like **bold**?
No, Google Chat requires *bold* syntax for emphasis; the skill automatically handles these formatting rules.
What happens if I don't have a settings file?
The skill will detect the absence of .claude/settings.json and prompt you to walk through the initial configuration process.
Does this support posting to private direct messages?
This tool is intended for Google Chat Spaces where you can configure webhooks; it is not designed for direct messaging individual users.
How it compares
Unlike manual copy-pasting, this skill automatically extracts git context and current branch data, ensuring notifications are consistent and data-rich.
📄 Full skill instructions — original source: jezweb/claude-skills
# Google Spaces Updates
**Status**: Production Ready
**Last Updated**: 2026-01-09
Post updates to a team Google Chat Space via webhook.
---
## Quick Start
### 1. Setup (first time per project)
Run
### 2. Post an update
---
## How It Works
### Step 1: Check for project settings
Look for
If NOT_FOUND, ask the user:
> "This project doesn't have Google Spaces configured. Would you like me to set it up? I'll need the webhook URL for your team's Google Space."
Then create the file using the template in
### Step 2: Determine update type
Based on the command or context, determine the update type:
| Type | When to use |
|------|-------------|
|
|
|
|
|
### Step 3: Gather context
Collect relevant information to include:
Also use context from the conversation:
- What was just completed
- Any preview/production URLs
- Relevant file paths
- Who might need to know
### Step 4: Format the message
Use the appropriate template from
**Key formatting rules for Google Chat:**
- Use
- Use
- Newlines work as expected
- Keep messages concise but informative
- Include actionable links when relevant
### Step 5: Post to webhook
Replace:
-
-
### Step 6: Confirm to user
After posting, tell the user:
> "Posted update to team chat: [brief summary of what was posted]"
---
## Message Templates
### Deployment
### Bug Fix
### Feature Complete
### Question
### Custom
---
## Setup Command
When user runs
1. Ask for the Google Spaces webhook URL
2. Ask for project name (or detect from package.json/repo)
3. Ask for team members (optional)
4. Create
5. Add
6. Confirm setup is complete
---
## Proactive Suggestions
Suggest posting an update when:
- User says "done", "finished", "completed" after significant work
- After a
- User mentions team members by name
- User seems blocked and might benefit from team input
Ask: "Would you like me to post an update to the team about this?"
---
## When NOT to Use
- Minor refactors, typo fixes
- WIP commits that aren't ready for review
- Internal debugging/testing
- Anything that would just be noise
---
## Getting a Webhook URL
1. Open Google Chat
2. Navigate to your Space
3. Click Space name → **Apps & integrations** → **Webhooks**
4. Click **Add webhook**
5. Name it (e.g., "Claude Code Updates")
6. Copy the webhook URL
The URL format:
**Security**: Keep webhook URLs private. Add
**Status**: Production Ready
**Last Updated**: 2026-01-09
Post updates to a team Google Chat Space via webhook.
---
## Quick Start
### 1. Setup (first time per project)
Run
/google-spaces-updates setup or manually create .claude/settings.json:{
"project": {
"name": "my-project",
"repo": "github.com/org/my-project"
},
"team": {
"chat_webhook": "https://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=KEY&token=TOKEN",
"members": ["Deepinder", "Joshua", "Raquel"]
}
}### 2. Post an update
"Post deployment update to team"
"Tell the team about the new feature"
"Ask the team about the auth approach"---
## How It Works
### Step 1: Check for project settings
Look for
.claude/settings.json in the current project directory:cat .claude/settings.json 2>/dev/null || echo "NOT_FOUND"If NOT_FOUND, ask the user:
> "This project doesn't have Google Spaces configured. Would you like me to set it up? I'll need the webhook URL for your team's Google Space."
Then create the file using the template in
templates/settings-template.json.### Step 2: Determine update type
Based on the command or context, determine the update type:
| Type | When to use |
|------|-------------|
|
deployment | After pushing to production/staging, deploying to Vercel/etc ||
bugfix | After fixing a bug, especially one reported by team ||
feature | After completing a feature that's ready for review/use ||
question | When blocked or need team input on a decision ||
custom | For anything else |### Step 3: Gather context
Collect relevant information to include:
# Recent commits (for context)
git log --oneline -3 2>/dev/null
# Current branch
git branch --show-current 2>/dev/null
# Changed files (if recent changes)
git diff --name-only HEAD~1 2>/dev/null | head -10Also use context from the conversation:
- What was just completed
- Any preview/production URLs
- Relevant file paths
- Who might need to know
### Step 4: Format the message
Use the appropriate template from
templates/ directory.**Key formatting rules for Google Chat:**
- Use
*bold* for emphasis (not **markdown bold**)- Use
_italic_ for secondary text- Newlines work as expected
- Keep messages concise but informative
- Include actionable links when relevant
### Step 5: Post to webhook
curl -X POST "WEBHOOK_URL" \
-H "Content-Type: application/json" \
-d '{"text": "MESSAGE_HERE"}'Replace:
-
WEBHOOK_URL with value from .claude/settings.json → team.chat_webhook-
MESSAGE_HERE with the formatted message (escape quotes properly)### Step 6: Confirm to user
After posting, tell the user:
> "Posted update to team chat: [brief summary of what was posted]"
---
## Message Templates
### Deployment
🚀 *Deployed: [PROJECT_NAME]*
[WHAT_CHANGED - 1-2 sentences]
• Branch: [BRANCH]
• Commit: [COMMIT_HASH]
[• Preview: URL (if applicable)]
[• Production: URL (if applicable)]
_Posted by [USER] via Claude Code_### Bug Fix
🐛 *Bug Fixed: [PROJECT_NAME]*
*Problem:* [What was broken]
*Solution:* [How it was fixed]
*Files:* [Key files changed]
[• Commit: [COMMIT_HASH]]
_Please verify if you reported this issue._### Feature Complete
✨ *Feature Complete: [PROJECT_NAME]*
*[FEATURE_NAME]*
[DESCRIPTION - what it does, 1-2 sentences]
[• Demo: URL]
[• Files: key files]
_Ready for review/testing._### Question
❓ *Question: [PROJECT_NAME]*
[QUESTION - clear and specific]
*Context:*
[Relevant background - what you're working on, what you've tried]
*Options considered:*
1. [Option A]
2. [Option B]
_@[PERSON] - would appreciate your input_### Custom
📢 *Update: [PROJECT_NAME]*
[MESSAGE]
_Posted by [USER] via Claude Code_---
## Setup Command
When user runs
/google-spaces-updates setup:1. Ask for the Google Spaces webhook URL
2. Ask for project name (or detect from package.json/repo)
3. Ask for team members (optional)
4. Create
.claude/settings.json using the template5. Add
.claude/ to .gitignore if not already there6. Confirm setup is complete
---
## Proactive Suggestions
Suggest posting an update when:
- User says "done", "finished", "completed" after significant work
- After a
git push to main/master/production- User mentions team members by name
- User seems blocked and might benefit from team input
Ask: "Would you like me to post an update to the team about this?"
---
## When NOT to Use
- Minor refactors, typo fixes
- WIP commits that aren't ready for review
- Internal debugging/testing
- Anything that would just be noise
---
## Getting a Webhook URL
1. Open Google Chat
2. Navigate to your Space
3. Click Space name → **Apps & integrations** → **Webhooks**
4. Click **Add webhook**
5. Name it (e.g., "Claude Code Updates")
6. Copy the webhook URL
The URL format:
https://chat.googleapis.com/v1/spaces/SPACE_ID/messages?key=KEY&token=TOKEN**Security**: Keep webhook URLs private. Add
.claude/settings.json to .gitignore.By JezWeb
How to Use This Skill Unit
Option A: Project-Specific (Recommended)
- Click "Download" above
- In your project, create the directory:
.agent/skills/google-spaces-updates/ - Save the file as
SKILL.md - The agent will automatically discover the skill based on its description.
Option B: Global Installation (All Agents)
Save the file to these locations to make it available across all projects:
- Claude Code:
~/.claude/skills/jezweb/claude-skills/google-spaces-updates/SKILL.md - Cursor:
~/.cursor/skills/jezweb/claude-skills/google-spaces-updates/SKILL.md - Antigravity:
~/.gemini/antigravity/skills/jezweb/claude-skills/google-spaces-updates/SKILL.md
🚀 Install with CLI:npx skills add jezweb/claude-skills
Recommended Rules
View more rules →Python Automation & Scripting Expert
PythonAutomationScripting
You are an expert in Python automation and scripting. Key Principles: - Write robust, error-resistant scripts - Implement proper logging - Handle edg...
Python DevOps & Infrastructure Automation
PythonDevOpsInfrastructure
You are an expert in Python for DevOps, infrastructure automation, and CI/CD. Key Principles: - Automate repetitive tasks - Use infrastructure as cod...
Test Automation Frameworks
AutomationTestingArchitecture
You are an expert in designing and building Test Automation Frameworks. Key Principles: - Maintainability and Scalability - Reusability of code - Rep...
Recommended Workflows
View more workflows →Automatic commit message generator
GitAIAutomation
--- description: Automatic commit message generator and fast AI-powered commit for all current changes --- // turbo-all This workflow automatically ...
Setup Husky Git Hooks
GitAutomationQuality
--- description: Automate code quality checks with pre-commit and pre-push hooks --- 1. **Install Husky**: - Install husky and lint-staged. // ...
Setup Vercel Cron Jobs
VercelCronAutomation
--- description: Create and test scheduled tasks in Next.js --- 1. **Create Cron Config**: - Add `crons` to `vercel.json`. ```json { "c...
