google-spaces-updates▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Post team updates to Google Chat Spaces with git context and deployment notifications.
- ›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
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 /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 -10
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 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_URLwith value from.claude/settings.json→team.chat_webhookMESSAGE_HEREwith 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:
- Ask for the Google Spaces webhook URL
- Ask for project name (or detect from package.json/repo)
- Ask for team members (optional)
- Create
.claude/settings.jsonusing the template - Add
.claude/to.gitignoreif not already there - Confirm setup is complete
Proactive Suggestions
Suggest posting an update when:
- User says "done", "finished", "completed" after significant work
- After a
git pushto 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
- Open Google Chat
- Navigate to your Space
- Click Space name → Apps & integrations → Webhooks
- Click Add webhook
- Name it (e.g., "Claude Code Updates")
- 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.
How to use google-spaces-updates on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add google-spaces-updates
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches google-spaces-updates from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate google-spaces-updates. Access the skill through slash commands (e.g., /google-spaces-updates) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ 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.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★32 reviews- ★★★★★Pratham Ware· Dec 24, 2024
I recommend google-spaces-updates for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kabir Li· Dec 16, 2024
google-spaces-updates reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yash Thakker· Nov 15, 2024
Useful defaults in google-spaces-updates — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Meera Jain· Nov 11, 2024
Registry listing for google-spaces-updates matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kiara Torres· Nov 7, 2024
google-spaces-updates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kabir Thomas· Oct 26, 2024
Registry listing for google-spaces-updates matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dhruvi Jain· Oct 6, 2024
google-spaces-updates is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kaira Malhotra· Oct 2, 2024
google-spaces-updates fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Zaid Farah· Sep 9, 2024
Useful defaults in google-spaces-updates — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Valentina Zhang· Sep 5, 2024
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