gog-meet

Google Meet 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-meet/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 well-structured, token-efficient overview: concrete safe-start commands, a compact command reference table, and clear pointers to detailed contracts via --help and schema JSON, with explicit safety guidance for writes and deletes.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line intro, a compact safe-start block, a tight commands table, and a closing pointer to --help/schema, with no padding or explanation of concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	Provides concrete, executable commands (e.g. 'gog auth list --check --json --no-input', 'gog schema meet --json') and a commands table, but defers full per-command syntax to '--help'/'schema ... --json' rather than giving complete copy-paste invocations. Not a 5 because the common-case invocations are not fully spelled out.	4 / 5
Workflow Clarity	A clear safe-start sequence (auth list -> schema -> readonly help) with explicit validation/safety checkpoints ('Confirm the exact account, object, and mutation before any write or delete', '--dry-run', '--readonly') is present. Not a 5 because there is no explicit validate->fix->retry feedback loop for the destructive write/delete operations.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Safe start, Commands) and a clearly signaled one-level-deep reference ('Read ../gog/SKILL.md first'), with detailed command contracts deferred to '--help' and 'schema ... --json'. No bundle files exist to verify, but the structure itself is exemplary.	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 a specific niche (Google Meet via the gog tool) but is too terse: it uses the generic word 'operations' instead of naming concrete capabilities and omits any 'Use when...' trigger guidance, which caps completeness.

Suggestions

Replace the generic 'operations' with 2-3 concrete actions, e.g. 'Create and end Google Meet meetings, list call history and participants, and update space config via gog.'

Add an explicit trigger clause, e.g. 'Use when the user asks to create, join, end, or inspect Google Meet meetings or call history.'

Include natural synonyms such as 'video calls' or 'meetings' so the description triggers on varied user phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Meet') but the only action word is the generic 'operations', matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete actions (create, end, get, etc.) are listed.	2 / 5
Completeness	It states a clear 'what' ('Google Meet operations through gog') but provides no 'when' / 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 3. Not a 4 because the 'when' is entirely missing rather than weakly present.	3 / 5
Trigger Term Quality	'Google Meet' is a natural term users would say, but 'operations' is generic and 'gog' is tool jargon; common variations like 'meetings', 'video calls', or 'join meeting' are absent. Not a 4 because keyword coverage is thin rather than merely missing a few.	3 / 5
Distinctiveness Conflict Risk	'Google Meet' is a clear, narrow niche unlikely to trigger for unrelated skills, with only minor overlap risk against other gog-wrapped Google services. Not a 5 because the description is too terse to establish fully distinct trigger phrases.	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-meet/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.