recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
77
72%
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/recipe-create-meet-space/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that provides specific CLI commands for creating a Google Meet space and sharing the link. Its main weaknesses are the gap between extracting the meeting URI from the response and using it in the email command, and the lack of any validation before sending the email.
Suggestions
Show how to extract the meeting URI from the JSON response of step 1 (e.g., a jq command or note about which field contains it) to make the workflow fully executable.
Add a validation checkpoint between creating the space and sending the email, such as verifying the meeting URI was returned successfully before proceeding to send.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Meet is or how email works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete commands but uses a placeholder 'MEETING_URI' without showing how to programmatically extract it from the response. The commands are specific but the glue between steps 1 and 3 is incomplete. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced but there's no validation—no check that the meeting space was successfully created before emailing, and no error handling if the space creation fails. For a multi-step process involving sending emails (a somewhat irreversible action), a validation checkpoint is warranted. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It references prerequisite skills clearly and the content is well-organized with a clear prerequisite note and numbered steps. | 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 | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.