Manage Google Meet conferences.
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-meet/SKILL.mdQuality
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 too terse and vague to be effective for skill selection. It names the product (Google Meet) but fails to specify concrete actions and entirely lacks a 'Use when...' clause. Without explicit triggers or detailed capabilities, Claude would struggle to reliably select this skill over similar ones.
Suggestions
List specific concrete actions such as 'Schedule Google Meet calls, generate meeting links, add participants, configure meeting settings'.
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to schedule a video call, create a Google Meet link, manage meeting participants, or set up a virtual meeting'.
Include common keyword variations users might say: 'video call', 'meeting link', 'Google Meet', 'virtual meeting', 'conference call'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says only 'Manage Google Meet conferences' which is vague — 'manage' is abstract and does not list any concrete actions like scheduling, joining, recording, sharing links, or adjusting settings. | 1 / 3 |
Completeness | The 'what' is extremely vague ('manage') and there is no 'when' clause or explicit trigger guidance at all, which per the rubric should cap completeness at 2 — but since the 'what' is also weak, this scores a 1. | 1 / 3 |
Trigger Term Quality | 'Google Meet' and 'conferences' are relevant natural keywords a user might say, but it's missing common variations like 'video call', 'meeting link', 'schedule a call', 'virtual meeting', or 'Google Meet link'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Meet' is a specific product which helps distinguish it from generic meeting or calendar skills, but 'manage conferences' is broad enough that it could 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 methods available through the `gws` CLI. Its main weakness is the lack of concrete, executable examples showing actual usage with `--params` or `--json` flags, which limits actionability. Adding one or two complete command examples would significantly improve the skill.
Suggestions
Add at least one concrete, executable example (e.g., `gws meet spaces create --params '{...}'`) showing a complete command with realistic parameters.
Include a brief end-to-end workflow example for a common task like creating a meeting space and then retrieving its details, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
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 helpful discovery workflow (`gws schema`), but lacks concrete executable examples of actual Meet operations (e.g., creating a space, listing conference records with specific flags/params). The guidance is more of a reference catalog than copy-paste-ready instructions. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a two-step discovery workflow (browse then inspect), which is useful. However, there's no end-to-end workflow example showing a complete task (e.g., create space → get details → end conference), and no validation or error-handling checkpoints. | 2 / 3 |
Progressive Disclosure | Cleanly structured with a prerequisite reference to shared skills, organized resource sections, and a discovery section. The external links to Google's documentation are appropriate one-level-deep references. Content is appropriately scoped for a SKILL.md overview. | 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
c7c6646
Table of Contents
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.