recipe-review-meet-participants
Review who attended a Google Meet conference and for how long.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-review-meet-participants68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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, specific niche (Google Meet attendance review) which makes it distinctive, but it lacks completeness by not providing explicit trigger guidance. The trigger terms are adequate but could include more natural variations users might say when needing this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'meeting attendance', 'who joined the call', 'participant list', 'meeting duration'
Include additional natural keywords users might say: 'video call participants', 'who was on the meeting', 'attendance report', 'call log'
Expand capabilities if applicable, such as 'export attendance data' or 'generate attendance reports'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Meet) and a specific action (review attendance and duration), but only describes one capability rather than multiple concrete actions. | 2 / 3 |
Completeness | Describes what the skill 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 'attended/conference' which are relevant, but misses common variations like 'meeting attendance', 'participants', 'call duration', 'video call', or 'who was on the call'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focusing on Google Meet attendance tracking; unlikely to conflict with other skills due to the specific platform and use case combination. | 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, executable commands for reviewing Google Meet attendance. The workflow is logical and the commands are copy-paste ready with clear placeholders. Minor improvement could be made by adding guidance on identifying the correct conference from the initial list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Meet is or how conferences work. Every line serves a purpose with concrete commands. | 3 / 3 |
Actionability | Provides fully executable CLI commands with exact syntax, parameter formats, and placeholder values. Copy-paste ready with clear substitution points (CONFERENCE_ID, PARTICIPANT_ID). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (list conferences → list participants → get sessions), but this is a read-only workflow that could benefit from noting how to identify the correct conference from the list before proceeding to step 2. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite callout, concise overview, and well-organized numbered steps. No need for external references. | 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 | |
- 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.