gws-chat-send
Google Chat: Send a message to a space.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-chat-send/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is concise and identifies a clear, specific platform (Google Chat) and action (send a message to a space), giving it good distinctiveness. However, it lacks a 'Use when...' clause, covers only a single action, and misses common keyword variations that would help Claude select it reliably.
Suggestions
Add a 'Use when...' clause with trigger terms like 'send a chat message', 'post to Google Chat', 'notify a Google Chat space', or 'Google Spaces'.
Expand the capability description to include additional actions if applicable, such as 'send messages, post cards, or notify team members in Google Chat spaces'.
Include common keyword variations users might say, such as 'Google Chat', 'chat space', 'Google Spaces', 'team message', or 'workspace chat'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Chat) and one specific action (send a message to a space), but only describes a single capability rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (send a message to a space) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Chat', 'message', and 'space' that users might say, but misses common variations like 'chat message', 'Google Spaces', 'Hangouts', or 'send notification'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Chat' and 'send a message to a space' is quite specific and unlikely to conflict with other skills; it clearly targets a distinct integration and action. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, concise skill that does exactly what it needs to. It provides clear, executable guidance for a single-purpose command with appropriate safety guardrails (user confirmation for write operations) and well-structured references to related skills. No improvements needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Google Chat is or how messaging works. The content is lean, with just the command, flags, an example, and essential tips. | 3 / 3 |
Actionability | Provides a fully copy-paste ready command with clear flag definitions, a concrete example, and actionable tips for discovering space names. Nothing is left vague. | 3 / 3 |
Workflow Clarity | This is a simple single-action skill (send a message), and the single action is unambiguous. It includes a caution to confirm with the user before executing a write command, which serves as a validation checkpoint for this destructive-adjacent operation. | 3 / 3 |
Progressive Disclosure | Clear prerequisite reference to shared auth skill, well-signaled 'See Also' links to related skills, and content is appropriately scoped to this single command without inlining unrelated material. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.