Post team updates to Google Chat Spaces with git context and deployment notifications.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add jezweb/claude-skills --skill google-spaces-updatesCompatible with
Supported agents
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:
epx add jezweb/claude-skills --skill google-spaces-updatesFetches 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:
.cursor/skills/google-spaces-updates
Restart Cursor to activate google-spaces-updates. Access via /google-spaces-updatesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
google-apps-script
jezweb/claude-skills · Backend · same repo
vitest
jezweb/claude-skills · Testing · same repo
google-image-search
glebis/claude-skills · Backend · tag: google
colab-session-operator
googlecolab/google-colab-cli · productivity · tag: google
typescript-best-practices
jwynia/agent-skills · Backend · same category
fastapi-python
mindrally/skills · Backend · same category
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