Review who attended a Google Meet conference and for how long.
70
63%
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-review-meet-participants/SKILL.mdQuality
Discovery
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 identifies a clear, narrow use case (reviewing Google Meet attendance and duration) which gives it good distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from more trigger terms and additional concrete actions to improve discoverability and completeness.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Google Meet attendance, participant lists, meeting duration, or who joined a video call.'
Include more natural trigger terms such as 'participants', 'meeting attendance', 'call duration', 'video conference', and 'who was on the call'.
Expand the capability description with additional concrete actions, e.g., 'Review who attended a Google Meet conference, check individual join/leave times, and summarize participant duration.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Meet) and a specific action (review attendance and duration), but only describes one capability rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing it closer to 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Meet' and 'attended' as natural keywords, but misses common variations like 'meeting attendance', 'participants', 'call duration', 'video call', or 'conference call'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—Google Meet attendance and duration review—which is unlikely to conflict with other skills. | 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 clear, actionable CLI commands in a logical sequence. Its main weakness is the lack of any guidance on interpreting results or handling cases where expected data isn't found, though for a read-only query workflow this is a minor gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Meet is or how conferences work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides specific, copy-paste ready CLI commands with exact syntax, parameter formats, and placeholder values clearly indicated (CONFERENCE_ID, PARTICIPANT_ID). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered (list conferences → list participants → get sessions), but there's no validation or error handling guidance. For a read-only operation this is less critical, but guidance on what to do if no conferences are found or IDs are invalid would improve it. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout, brief description, and numbered steps. No need for external references given the scope. | 3 / 3 |
Total | 11 / 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.