gog-groups

Google Groups operations through gog.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-groups/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.

The body is a lean, well-structured overview that delegates shared concerns to a sibling skill and gives concrete, runnable read-only commands with strong safety framing. Its main gap is the lack of concrete worked examples for the `list` and `members` commands.

Dimension	Reasoning	Score
Conciseness	The body is lean: short sections, a compact 3-command block, a 2-row table, and no padding or explanation of what Google Groups is. It assumes Claude's competence with every token earning its place, matching anchor 5. It is not 4 because there is nothing to trim.	5 / 5
Actionability	Concrete runnable commands and explicit flags (`--account`, `--readonly`, `--dry-run`, `--no-input`) are provided with a command table, matching anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps'). It is not 5 because `list`/`members` lack a concrete example invocation with flags and expected output, and the example uses a placeholder account.	4 / 5
Workflow Clarity	The 'Safe start' section gives a sequenced entry (auth check, schema, help) with a `--readonly` guard and a confirm-before-mutation checkpoint, matching anchor 4. It is not 5 because there is no explicit validate->fix->retry feedback loop, though the listed `list`/`members` commands are read-only so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	For a sub-50-line skill with no bundle files, the well-organized sections (Safe start, rules, Commands, discovery) and one-level-deep sibling reference ('Read `../gog/SKILL.md` first') with shared concerns delegated out match anchor 5. The `gog schema ... --json` contract is appropriately pulled live rather than inlined.	5 / 5
	Total	18 / 20 Passed

Description

48%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 correctly identifies the domain and tool in third person but is generic on actions and omits any 'Use when' trigger clause, capping completeness. It is distinctive enough to avoid most conflicts but would benefit from concrete capabilities and trigger phrases.

Suggestions

Add concrete actions, e.g. 'List groups you belong to and inspect group members' instead of the generic 'operations'.

Append a 'Use when' clause naming natural trigger terms, e.g. 'Use when managing Google Groups, listing group members, or working with mailing lists'.

Include synonyms/users' phrasings ('groups', 'mailing lists', 'members') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Google Groups operations through gog' names the domain and tool but uses the generic verb 'operations' without any concrete actions (no 'list members', 'manage groups'). It matches anchor 2 ('Names the domain but actions are minimal or generic') rather than 3 because no concrete action is named, and is above 1 because the specific domain/tool is identified.	2 / 5
Completeness	It gives a clear-ish 'what' ('Google Groups operations through gog') but no 'when/Use when' clause, which the guidelines cap at 3. It is not 2 because the 'what' is more specific than the anchor-2 'Use when working with documents' example, and not 4 because the 'when' is entirely missing.	3 / 5
Trigger Term Quality	'Google Groups' is a natural term a user would say, but synonyms/variations ('groups', 'mailing lists', 'members') are absent, matching anchor 3 ('Some relevant keywords but missing common variations or synonyms'). It is above 2 because the one keyword is strong and domain-specific rather than a generic filler.	3 / 5
Distinctiveness Conflict Risk	Google Groups plus the `gog` tool namespace is a fairly specific niche with low conflict risk against unrelated skills, matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). It is below 5 because sibling `gog` skills for other Google services create some overlap and 'operations' is broad.	4 / 5
	Total	12 / 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-groups/SKILL.md
Commit: eb85a99

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.