gws-chat
Google Chat: Manage Chat spaces and messages.
53
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.
The description is too brief and lacks the explicit trigger guidance needed for Claude to reliably select this skill. While it identifies the platform (Google Chat), it fails to enumerate specific capabilities or provide 'Use when...' conditions. The vague 'manage' verb doesn't convey what concrete actions are available.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Google Chat, gchat, Chat spaces, or sending messages in Google Workspace'.
Replace 'Manage' with specific actions like 'Create and configure Chat spaces, send and read messages, list space members, search conversations'.
Include common user terms and variations: 'gchat', 'Google Workspace chat', 'team spaces', 'direct messages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Chat) and mentions two general actions (manage spaces and messages), but lacks specific concrete actions like 'create spaces', 'send messages', 'list members', or 'delete conversations'. | 2 / 3 |
Completeness | Provides a weak 'what' (manage spaces and messages) 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', 'spaces', and 'messages' which are relevant keywords, but misses common variations users might say like 'gchat', 'chat rooms', 'direct messages', 'DMs', or 'team chat'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Chat' is specific enough to distinguish from generic chat skills, but 'manage messages' could overlap with other messaging platform skills (Slack, Teams, etc.) without clearer differentiation. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference structure for the Google Chat API with good organization and clear navigation to related resources. However, it lacks concrete executable examples showing actual API calls with parameters, and the API descriptions contain significant repetition. The skill would benefit from at least one complete example demonstrating a common operation.
Suggestions
Add 1-2 concrete executable examples showing common operations (e.g., sending a message, listing spaces) with actual --params usage
Remove repetitive boilerplate from API descriptions (e.g., consolidate the custom emoji workspace requirements into a single note)
Add validation guidance for destructive operations like spaces.delete, noting the cascading behavior and suggesting verification steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes repetitive boilerplate text in API descriptions (e.g., the custom emoji workspace requirements are repeated 4 times verbatim). The structure is clean but could be tightened. | 2 / 3 |
Actionability | Provides command syntax and schema discovery commands, but lacks concrete executable examples showing actual usage with real parameters. The API resource list describes what methods do but doesn't show how to call them with specific flags/params. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic workflow for exploring the API, but there's no validation or error handling guidance. For operations like delete (cascading) or import, there are no checkpoints or verification steps mentioned. | 2 / 3 |
Progressive Disclosure | Well-structured with clear prerequisite reference to shared skill, helper command link, and organized API resource sections. Navigation is straightforward with one-level-deep references to related skills. | 3 / 3 |
Total | 9 / 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.