gws-chat-send
Google Chat: Send a message to a space.
70
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
32%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 description is too minimal - it identifies the platform and a single action but lacks trigger guidance and comprehensive capability coverage. The absence of a 'Use when...' clause makes it difficult for Claude to know when to select this skill over others. Adding explicit triggers and more action verbs would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Google Chat', 'gchat', 'send chat message', 'notify space', 'post to Google Chat'
Expand capabilities beyond just sending messages - include actions like 'send messages, post notifications, share updates to Google Chat spaces'
Include file type or context triggers such as 'when user wants to communicate with team via Google Chat or mentions Chat spaces'
| 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 multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (send message to space) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Chat', 'message', and 'space' which are relevant keywords, but missing common variations like 'gchat', 'chat message', 'post to chat', or 'notify team'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Chat' and 'space' provide some distinctiveness from generic messaging skills, but could overlap with other chat/messaging integrations like Slack or Teams without clearer differentiation. | 2 / 3 |
Total | 7 / 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 a well-crafted, minimal skill that exemplifies good documentation practices. It provides exactly what's needed for the single task (sending a chat message) without over-explaining, includes proper safety warnings for the write operation, and appropriately delegates shared concerns to referenced files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Chat is or how messaging works. Every section serves a purpose with no padding. | 3 / 3 |
Actionability | Provides complete, copy-paste ready command with clear flag documentation. The example is executable and the tips provide practical guidance for finding space names. | 3 / 3 |
Workflow Clarity | For this simple single-command skill, the workflow is unambiguous. Includes appropriate validation checkpoint with the CAUTION note requiring user confirmation before executing the write operation. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear references to shared auth/flags in prerequisite, and well-signaled one-level-deep links to related skills. Content is appropriately scoped for this single command. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 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.