CtrlK
BlogDocsLog inGet started
Tessl Logo

google-meet

Google Meet via gws: create spaces, fetch join links, list recordings.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-crafted skill body: concise, fully actionable with executable commands, clearly sequenced workflows with validation checkpoints, and cleanly organized. No significant weaknesses relative to the rubric.

DimensionReasoningScore

Conciseness

The body is lean and operational — it does not explain what Google Meet or recordings are, and nearly every line adds API-surface or selection guidance Claude would not already know, so every token earns its place.

3 / 3

Actionability

It provides fully executable, copy-paste-ready `gws meet ...` commands with concrete JSON/params payloads for each resource and method, matching the level-3 anchor.

3 / 3

Workflow Clarity

Multi-step flows are explicitly sequenced with checkpoints — the prerequisite onboarding flow (state, ask, read_skill), account-selection rules, and validation/fallback handling for 403/empty recording lists on destructive or batch-style operations.

3 / 3

Progressive Disclosure

A single, well-organized file with clear sections (Prerequisites, Selecting an account, When to Use, Quick Reference, Rules) and no broken or nested file references; appropriate for a CLI-wrapper skill with no bundle files.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 specific, well-scoped description that names concrete actions and natural trigger terms. Its main weakness is the absence of an explicit "when to use" clause, which limits completeness.

Suggestions

Append a trigger clause, e.g. "Use when the user wants a Meet join link not tied to a Calendar event, or to look up past meeting recordings, participants, or transcripts."

Consider dropping or contextualizing "spaces" since users more often say "room" or "link" than the API term "space".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "create spaces, fetch join links, list recordings" — rather than vague language, matching the level-3 anchor of enumerated specific actions.

3 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

"Google Meet", "join links", and "recordings" are natural terms a user would say when needing this skill; "spaces" is mildly technical but the overall keyword coverage is strong.

3 / 3

Distinctiveness Conflict Risk

"Google Meet via gws" with the listed Meet-specific actions carves out a clear niche with distinct triggers, making conflicts with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Open-Curiosity/gini-agent
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.