Post team updates to Google Chat Spaces with git context and deployment notifications.
Works with
Reads webhook URL and team config from .claude/settings.json ; includes setup command to initialize per project
Supports five message types: deployment, bugfix, feature complete, question, and custom updates with appropriate templates
Automatically gathers git context (recent commits, branch, changed files) to enrich messages
Proactively suggests posting updates after significant work, pushes to
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongoogle-spaces-updatesExecute the skills CLI command in your project's root directory to begin installation:
Fetches google-spaces-updates from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate google-spaces-updates. Access via /google-spaces-updates in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Status: Production Ready Last Updated: 2026-01-09
Post updates to a team Google Chat Space via webhook.
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"]
}
}
"Post deployment update to team"
"Tell the team about the new feature"
"Ask the team about the auth approach"
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.
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 |
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 -10
Also use context from the conversation:
Use the appropriate template from templates/ directory.
Key formatting rules for Google Chat:
*bold* for emphasis (not markdown bold)_italic_ for secondary textcurl -X POST "WEBHOOK_URL" \
-H "Content-Type: application/json" \
-d '{"text": "MESSAGE_HERE"}'
Replace:
WEBHOOK_URL with value from .claude/settings.json → team.chat_webhookMESSAGE_HERE with the formatted message (escape quotes properly)After posting, tell the user:
"Posted update to team chat: [brief summary of what was posted]"
🚀 *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 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: [PROJECT_NAME]*
*[FEATURE_NAME]*
[DESCRIPTION - what it does, 1-2 sentences]
[• Demo: URL]
[• Files: key files]
_Ready for review/testing._
❓ *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_
📢 *Update: [PROJECT_NAME]*
[MESSAGE]
_Posted by [USER] via Claude Code_
When user runs /google-spaces-updates setup:
.claude/settings.json using the template.claude/ to .gitignore if not already thereSuggest posting an update when:
git push to main/master/productionAsk: "Would you like me to post an update to the team about this?"
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jezweb/claude-skills
jezweb/claude-skills
kostja94/marketing-skills
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
I recommend google-spaces-updates for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
google-spaces-updates reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in google-spaces-updates — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for google-spaces-updates matched our evaluation — installs cleanly and behaves as described in the markdown.
google-spaces-updates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for google-spaces-updates matched our evaluation — installs cleanly and behaves as described in the markdown.
google-spaces-updates is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
google-spaces-updates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in google-spaces-updates — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added google-spaces-updates from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 32