CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-meet

Google Meet through gog. Use for Google Meet spaces, configuration, call history, and participants.

Quality

83%

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.

An exemplary lean command-dispatcher skill: executable safe-start commands, explicit safety checkpoints around writes, and clean structure with one well-justified external reference. The only notable gap is the absence of a worked example of a real meet command and of any error-recovery guidance.

DimensionReasoningScore

Conciseness

The ~40-line body is lean throughout: three copy-paste safe-start commands, five one-line safety rules, a six-row command table, and a pointer to per-command help/schema. No concept explanations or padding; every token earns its place, matching the anchor-5 example's economy.

5 / 5

Actionability

Guidance is mostly executable: "gog auth list --check --json --no-input", "gog schema meet --json", and "gog --readonly --account user@example.com meet --help" are copy-paste ready, with the table giving each subcommand's purpose. It stops short of anchor 5 because no worked example of an actual meet operation (e.g. a full `gog meet create` or `gog meet history` invocation) is shown — syntax is delegated to --help/schema discovery.

4 / 5

Workflow Clarity

A clear validation-first sequence is present: read ../gog/SKILL.md first, run the auth check/schema/readonly help safe-start, then execute with "--dry-run before supported writes" and "Confirm the exact account, object, and mutation before any write or delete" as pre-write checkpoints. It misses anchor 5 because there is no error-recovery feedback loop (e.g. what to do when the auth check fails).

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and this under-50-line skill needs none: two well-organized sections plus a single clearly-signaled one-level-deep external pointer ("Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules") with its purpose stated, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

73%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.

A concise, well-scoped description with an explicit trigger clause and natural keywords. Its main weakness is the lack of concrete action verbs — capability is conveyed through a noun list rather than stated operations.

Suggestions

Add concrete action verbs to the first sentence, e.g. "Create and manage Google Meet spaces, review call history, and list participants through gog."

Include one or two extra natural trigger phrases such as "meeting spaces" or "past calls" so users phrasing the need differently still match.

DimensionReasoningScore

Specificity

"Google Meet through gog. Use for Google Meet spaces, configuration, call history, and participants." names the domain and enumerates four concrete capability areas, but states no action verbs (create, list, end, update), so it sits above the domain-only anchor 2 yet below the explicit-actions anchor 4.

3 / 5

Completeness

Both parts are present: the "what" is "Google Meet through gog" and an explicit "Use for ..." trigger clause covers the "when" with concrete topics. The "what" is terse and verb-less, keeping it below anchor 5's clearly explicit both-parts standard, but the explicit Use-for clause lifts it above anchor 3's weakly-implied-when case.

4 / 5

Trigger Term Quality

Terms like "Google Meet", "call history", and "participants" are exactly what users would say, giving good keyword coverage; common variations such as "join a meeting", "video call", or "meeting link" are missing, so it falls short of the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Google Meet through gog" carves out a clear niche with distinct triggers (Meet spaces, call history, participants); these terms are unlikely to fire for non-Meet or non-gog skills, matching the minimal-conflict anchor.

5 / 5

Total

16

/

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-meet/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.