google-spaces-updates
Post team updates to Google Chat Spaces via webhook. Deployment notifications, bug fixes, feature announcements, questions. Reads config from .claude/settings.json, includes git context. Use when: "post to team", "notify team", after deployments, completing features, fixing bugs, asking team questions.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill google-spaces-updates87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, natural trigger terms users would actually say, explicit 'Use when' guidance, and a clear niche that distinguishes it from other notification or communication skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Post team updates', 'Deployment notifications, bug fixes, feature announcements, questions', 'Reads config from .claude/settings.json, includes git context' - these are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (post updates to Google Chat Spaces via webhook, various notification types) AND when (explicit 'Use when:' clause with specific triggers like 'after deployments', 'completing features', 'fixing bugs'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'post to team', 'notify team', 'deployments', 'features', 'bugs', 'team questions'. These are phrases users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: specifically targets Google Chat Spaces via webhook, with clear triggers around team notifications. The combination of 'Google Chat', 'webhook', and team-specific actions makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with clear workflows and executable examples. The main weakness is length - message templates and setup instructions could be moved to referenced files to improve token efficiency. The content is practical and provides good context-gathering commands.
Suggestions
Move message templates to a separate `templates/messages.md` file and reference it, reducing the main skill file by ~50 lines
Remove the 'When NOT to Use' section - Claude can infer appropriate usage from the positive guidance
Condense the 'Getting a Webhook URL' section to 2-3 lines since this is standard Google Chat documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'Status' and 'Last Updated' metadata, the 'When NOT to Use' section (Claude can infer this), and verbose explanations of webhook setup that could be condensed. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete JSON templates, specific curl syntax, and copy-paste ready message templates. The step-by-step workflow includes concrete commands for every action. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit checkpoints: check settings → determine type → gather context → format → post → confirm. Includes error handling for missing config and clear decision tables for update types. | 3 / 3 |
Progressive Disclosure | References templates directory but includes all message templates inline rather than in separate files. The content is well-organized with clear sections, but the 200+ line document could benefit from splitting templates and setup instructions into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.