gws-chat

Google Chat: Manage Chat spaces and messages.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-chat/SKILL.md

Quality

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 terse and vague. While it correctly identifies the platform (Google Chat), it fails to enumerate specific capabilities and entirely omits trigger guidance for when Claude should select this skill. The word 'manage' is a catch-all that doesn't convey concrete actions.

Suggestions

Add a 'Use when...' clause with explicit trigger terms like 'Use when the user asks about Google Chat, sending chat messages, creating or listing Chat spaces, or managing Google Workspace conversations.'

Replace the vague 'Manage' with specific actions such as 'Send messages, create and list spaces, add members, read conversation history in Google Chat.'

Include natural keyword variations users might say, such as 'Google Workspace chat', 'chat rooms', 'DMs', or 'group conversations'.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Chat) and two actions (manage spaces and messages), but 'manage' is vague and doesn't list specific concrete actions like creating spaces, sending messages, listing members, etc.	2 / 3
Completeness	Provides a brief 'what' (manage spaces and messages) but completely lacks a 'when should Claude use it' clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'Google Chat', 'spaces', and 'messages' which are relevant keywords, but misses common variations like 'chat rooms', 'direct messages', 'DMs', 'send message', or 'Google Workspace chat'.	2 / 3
Distinctiveness Conflict Risk	'Google Chat' is fairly specific and distinguishes it from generic messaging skills, but 'messages' and 'spaces' are generic enough terms that could overlap with Slack or other messaging platform skills.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a verbose API reference listing that duplicates information discoverable through the tool's own help system. The repetitive descriptions (especially for customEmojis) waste significant token budget. The skill would benefit greatly from trimming the API listing to just resource/method names and adding 2-3 concrete usage examples.

Suggestions

Remove or drastically shorten the API method descriptions since they repeat boilerplate and are discoverable via `gws chat --help` and `gws schema` — list only resource.method names in a compact table.

Add 2-3 concrete, executable examples for common tasks (e.g., list spaces, create a space, find a direct message) with actual `gws chat` commands and sample `--params` flags.

Eliminate the repeated 'Custom emojis are only available for Google Workspace accounts' text that appears four times verbatim.

Add a brief workflow example showing a multi-step task like 'create space → add members → send first message' with validation checkpoints.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with repetitive boilerplate descriptions for each API method. The customEmojis section repeats nearly identical text about Google Workspace requirements four times. The spaces section includes lengthy descriptions that are essentially API documentation Claude could discover via `gws schema`.	1 / 3
Actionability	Provides the basic command pattern and discovery commands (`gws schema`, `--help`), but lacks concrete executable examples for common operations like creating a space, sending a message, or listing members. The helper command reference to `+send` is useful but the main content is descriptive rather than instructive.	2 / 3
Workflow Clarity	The 'Discovering Commands' section provides a reasonable two-step workflow (browse then inspect), but there are no validation steps or error handling guidance. For a reference-style skill this is acceptable, but the lack of any concrete workflow example (e.g., create space → add members → send message) limits clarity.	2 / 3
Progressive Disclosure	References the shared skill file and the helper command correctly, which is good progressive disclosure. However, the massive inline API reference listing should be significantly trimmed since users can discover methods via `gws chat --help` and `gws schema`. The content that is inline would be better served by the discovery commands already mentioned.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: c7c6646

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.