Create a Google Meet meeting space and share the join link.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-meet-space74
Quality
63%
Does it follow best practices?
Impact
100%
1.96xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-create-meet-space/SKILL.mdDiscovery
40%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 clearly identifies its purpose around Google Meet but suffers from missing explicit trigger guidance ('Use when...') which is critical for skill selection. It has good distinctiveness due to the specific platform mention but could benefit from more natural trigger terms and comprehensive action coverage.
Suggestions
Add a 'Use when...' clause with trigger terms like 'video call', 'Google Meet', 'Meet link', 'schedule meeting', 'video conference'
Expand natural keyword coverage to include variations users might say: 'virtual meeting', 'video chat', 'Meet invite', 'conference call'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Meet) and two actions (create meeting space, share join link), but not comprehensive - doesn't mention scheduling, calendar integration, or other meeting management capabilities. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Meet' and 'meeting' which are natural terms, but missing common variations like 'video call', 'video conference', 'Meet link', 'schedule a call', or 'virtual meeting'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche with 'Google Meet' as a distinct product identifier - unlikely to conflict with other meeting or calendar skills due to the specific platform mention. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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-crafted, concise skill that provides actionable commands for a simple workflow. Its main weakness is the lack of explicit validation or error handling, and step 2 could be more specific about extracting the URI from the JSON response.
Suggestions
Clarify step 2 by showing how to extract the meeting URI from the JSON response (e.g., using jq or noting the specific field name)
Add a brief validation note for error cases (e.g., 'If space creation fails, check authentication status')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what Google Meet is, every line serves a purpose. | 3 / 3 |
Actionability | Provides exact, copy-paste ready commands with specific flags and JSON payloads. Clear what to do at each step. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced but lacks validation checkpoints. No error handling if space creation fails or email send fails. Step 2 'Copy the meeting URI' is vague about how to extract it from JSON response. | 2 / 3 |
Progressive Disclosure | Appropriate for a simple 3-step recipe. Prerequisites clearly stated at top, content is well-organized and doesn't need external references for this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
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.