CtrlK
BlogDocsLog inGet started
Tessl Logo

gws-meet

Manage Google Meet conferences.

56

Quality

47%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-meet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is far too terse and vague to be effective. It names the platform (Google Meet) but fails to specify any concrete actions and completely lacks trigger guidance for when Claude should select this skill. It would be easily overlooked or confused with other meeting-related skills.

Suggestions

Replace the vague verb 'Manage' with specific concrete actions such as 'Schedule, create links for, configure settings, and manage participants in Google Meet conferences'.

Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user mentions Google Meet, video calls, meeting links, video conferences, or screen sharing'.

Include common user-facing synonyms and file/URL patterns (e.g., 'meet.google.com links', 'video meeting', 'virtual meeting') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description says 'Manage Google Meet conferences' which is extremely vague. 'Manage' is an abstract verb that doesn't specify any concrete actions like scheduling, joining, recording, sharing links, or configuring settings.

1 / 3

Completeness

The 'what' is extremely vague ('manage') and there is no 'when' clause or explicit trigger guidance at all. Missing a 'Use when...' clause caps this at 2, and the weak 'what' brings it to 1.

1 / 3

Trigger Term Quality

'Google Meet' and 'conferences' are relevant keywords a user might say, but it's missing common variations like 'video call', 'meeting link', 'video conference', 'screen sharing', or 'Meet invite'.

2 / 3

Distinctiveness Conflict Risk

'Google Meet' provides some specificity that distinguishes it from generic meeting or calendar skills, but 'manage conferences' is broad enough to potentially overlap with calendar management or other video conferencing skills.

2 / 3

Total

6

/

12

Passed

Implementation

72%

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

This is a well-structured, concise reference skill that effectively catalogs the Google Meet API resources and provides a clear discovery workflow. Its main weakness is the lack of concrete, executable examples showing actual API calls with real parameters, which limits actionability. Adding 1-2 complete usage examples would significantly improve the skill.

Suggestions

Add 1-2 concrete executable examples showing common operations (e.g., `gws meet spaces create --params '...'` or `gws meet conferenceRecords list --params '...'`) with realistic parameter values.

Include at least one end-to-end workflow example, such as creating a space and then retrieving its details, to demonstrate a complete task sequence.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It lists resources and methods without explaining what Google Meet is or how conferences work. Every line serves a purpose—no padding or unnecessary context.

3 / 3

Actionability

Provides the CLI syntax pattern and a discovery workflow with concrete commands, but lacks executable examples of actual operations (e.g., creating a space, listing conference records with specific flags/params). The guidance is concrete but incomplete for real usage.

2 / 3

Workflow Clarity

The 'Discovering Commands' section provides a two-step discovery workflow (browse then inspect), which is helpful. However, there's no end-to-end workflow showing how to actually perform a task like creating a space or retrieving recordings, and no validation/verification steps.

2 / 3

Progressive Disclosure

Cleanly structured with a prerequisite reference to shared skills, a concise API resource listing, and a discovery section. The external links to Google's documentation and the reference to the shared SKILL.md are one level deep and clearly signaled.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
googleworkspace/cli
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.