CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-chat

Google Chat through gog. Use for Google Chat spaces, messages, threads, and members.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

The body is an exemplar of lean, generated-skill authoring: executable safe-start commands, concrete safety flags, a tight command table, and one-level delegation of shared rules to the parent gog skill and of syntax to --help/schema. The only gap is the absence of even one concrete operational example beyond discovery commands.

DimensionReasoningScore

Conciseness

Every line instructs — "Use `gog` for Google Chat operations. Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules" — with zero explanation of concepts Claude already knows and no padding. This matches anchor 5's 'every token earns its place'; there is nothing to trim, so it exceeds anchor 4.

5 / 5

Actionability

The "Safe start" block gives copy-paste-ready commands (`gog auth list --check --json --no-input`, `gog schema chat --json`), the bullets name specific flags (`--account`, `--readonly`, `--dry-run`, `--json --wrap-untrusted`), and the command table lists dm/messages/spaces/threads. It falls short of anchor 5 only because no worked example of an actual operation (e.g., sending a message or listing a space's members) is shown — syntax is delegated to `--help` and `gog schema chat <command> --json`.

4 / 5

Workflow Clarity

A verification-first sequence is present (auth check → schema → per-command help), and destructive-write checkpoints are explicit: "Confirm the exact account, object, and mutation before any write or delete" and "Use `--no-input` in automation and `--dry-run` before supported writes". Because validation for risky writes IS present, the destructive-operation cap at 3 does not apply; it stays below anchor 5 since the sequence is implied by section order rather than explicit steps and there is no error-recovery loop.

4 / 5

Progressive Disclosure

The body is under 50 lines with clean sections (Safe start, Commands) and a single clearly-signaled one-level-deep reference: "Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules". Flag and schema details are delegated to `--help` and `gog schema chat <command> --json` instead of being inlined, matching the simple-skill exception for a top score; nothing is misplaced, so it exceeds anchor 4.

5 / 5

Total

18

/

20

Passed

Description

68%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 is concise, in third person, distinctly scoped, and has an explicit trigger clause, but it lists objects rather than capabilities — no verbs tell the reader what operations are available. Adding concrete actions (e.g., send/read messages, list or manage spaces and members) and a few natural synonyms would lift specificity and completeness.

Suggestions

State concrete operations in the description, e.g., 'Send and read Google Chat messages, list and manage spaces, threads, and members through gog', so the 'what' covers actions rather than only objects.

Add natural trigger variations users would say, such as 'DMs', 'direct messages', or 'chat rooms', to broaden trigger-term coverage.

Make the 'when' clause situation-oriented (e.g., 'Use when the user wants to post, search, or manage content in Google Chat') rather than only enumerating object types.

DimensionReasoningScore

Specificity

The description names the domain and objects ("Google Chat spaces, messages, threads, and members") but contains no concrete actions or verbs — it never says what can be done with them. This matches 'names the domain but actions are minimal or generic'; it falls short of anchor 3, which requires 1-2 concrete actions, and is well above anchor 1's pure abstraction.

2 / 5

Completeness

Both parts are present: 'what' is stated ("Google Chat through gog") and 'when' is explicit ("Use for Google Chat spaces, messages, threads, and members"). The 'what' is thin on operations and the 'when' enumerates objects rather than trigger situations, so it does not reach anchor 5's concrete trigger phrases; the explicit "Use for" clause keeps it above anchor 3.

4 / 5

Trigger Term Quality

"Google Chat", "spaces", "messages", "threads", and "members" are terms users would naturally say when needing this skill. A few natural variants are missing (e.g., "DMs" or "direct messages", which the skill body's `dm` command covers), keeping it below anchor 5's comprehensive synonym coverage but clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"Google Chat through gog" carves out a clear product-and-tool niche, and the trigger terms are Google Chat-specific, so conflict with other skills is minimal. It is not anchor 4, which reserves for skills with minor overlap risk with closely related siblings.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-chat/SKILL.md

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.