gog-chat

Google Chat operations through gog.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-chat/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

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

A tight, well-structured CLI skill body: executable safe-start commands, explicit safety gates for writes, and clean delegation of per-command syntax to --help and schema. The only gaps are the absence of a worked example of a real operation and of any error-recovery guidance when the auth check or a write fails.

Dimension	Reasoning	Score
Conciseness	The body is lean and purely operational — 'Use `gog` for Google Chat operations', the safe-start command block, safety bullets, and a four-row command table — with no padding or explanation of concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	The safe-start commands ('gog auth list --check --json --no-input', 'gog schema chat --json', 'gog --readonly --account user@example.com chat --help') are fully executable and copy-paste ready, and 'Do not guess command syntax' with the --help/schema delegation is concrete guidance. It stops short of anchor 5 because no concrete example of an actual operation (e.g., listing spaces or sending a message) is shown — the common cases are delegated to --help rather than covered by examples.	4 / 5
Workflow Clarity	The safe-start block is a clear ordered sequence with most checkpoints present: auth validation via '--check', '--dry-run before supported writes', and 'Confirm the exact account, object, and mutation before any write or delete' as a pre-write gate. It does not reach anchor 5 because there are no error-recovery feedback loops (e.g., what to do when the auth check fails).	4 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections, a single clearly signaled one-level-deep reference ('Read ../gog/SKILL.md first' for shared rules), and the bulk of per-command detail pushed to runtime discovery ('gog chat <command> --help', 'gog schema chat <command> --json'). No bundle files exist to inline or bury.	5 / 5
	Total	18 / 20 Passed

Description

40%Weight 40%Scale 1-5

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 identifies the domain and tool cleanly but does no triggering work beyond that: it names zero concrete operations and gives no guidance on when the skill should be used. Most of the descriptive burden is silently carried by the skill body.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to send or read Google Chat messages, list or manage Chat spaces, or work with chat threads/DMs.'

Replace the generic word 'operations' with 2-4 concrete capabilities drawn from the command table, e.g. 'Send and read Chat messages and DMs, list and manage spaces, and browse threads'.

Include natural trigger terms and synonyms users actually say — 'Google Chat', 'Chat space', 'chat message', 'DM' — rather than only the product and tool names.

Dimension	Reasoning	Score
Specificity	'Google Chat operations through gog' names the domain and tool but lists no concrete actions — nothing like sending messages, managing spaces, or reading threads. It is above anchor 1 (it is not pure abstraction) but does not reach anchor 3, which requires at least 1-2 concrete actions.	2 / 5
Completeness	The 'what' is vague ('operations' names no actual capability) and the 'when' is entirely missing — there is no 'Use when...' clause, which alone caps completeness at 3. It fits anchor 2 (vague what, no when) better than anchor 3, whose example states a clear, concrete what.	2 / 5
Trigger Term Quality	'Google Chat' is a relevant natural keyword a user would say, but the description omits common variations and synonyms (chat messages, spaces, threads, DMs). This matches anchor 3 — some relevant keywords, missing common variations — rather than 4, which requires good keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Google Chat' plus the 'gog' tool name defines a distinct niche with minimal conflict risk. It falls short of anchor 5 only because the generic 'X operations through gog' phrasing pattern would overlap with sibling gog skills (gmail, drive) and other chat-related skills.	4 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openclaw/gogcli
Path: .agents/skills/gog-chat/SKILL.md
Commit: 414e2ff

Reviewed: 3 days 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.