gws-workflow-meeting-prep
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
63
55%
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-workflow-meeting-prep/SKILL.mdQuality
Discovery
50%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 provides a reasonable sense of the skill's purpose—meeting preparation involving agendas, attendees, and linked documents—but reads more like a marketing tagline than a functional skill description. It lacks explicit trigger guidance ('Use when...'), concrete action verbs, and sufficient keyword coverage to reliably distinguish it from other meeting or Google-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'meeting prep', 'upcoming meeting', 'Google Calendar', 'meeting agenda', 'attendee list'.
Replace the tagline format with concrete action verbs, e.g., 'Creates meeting agendas, retrieves attendee lists from Google Calendar, and links relevant Google Docs for upcoming meetings.'
Include common keyword variations such as 'calendar', 'Google Calendar', 'meeting notes', 'participants', and 'schedule' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (meeting preparation) and lists some specific elements (agenda, attendees, linked docs), but doesn't describe concrete actions like 'create agenda', 'fetch attendee list', or 'link relevant documents'. The colon-separated format reads more like a tagline than a capability list. | 2 / 3 |
Completeness | The 'what' is partially addressed (prepare for meetings with agenda, attendees, linked docs), but there is no explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords like 'meeting', 'agenda', 'attendees', and 'docs' that users might say. However, it misses common variations like 'calendar', 'Google Calendar', 'meeting prep', 'meeting notes', 'participants', or 'Google Docs'. The phrase 'Google Workflow' is not something a user would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Google Workflow' and meeting-specific elements (agenda, attendees, linked docs) provides some distinctiveness, but 'meeting preparation' could overlap with general calendar skills, note-taking skills, or other Google-related skills. The scope is not sharply delineated. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured with good cross-references, but it significantly underdelivers on its stated purpose. A 'meeting prep' workflow should describe a multi-step process (fetch next event, extract attendees, retrieve linked documents, summarize agenda), but instead it only documents a single CLI command with no workflow steps or example output. The actionability suffers from the lack of expected output format and the workflow clarity is poor for what should be a multi-step preparation process.
Suggestions
Add a step-by-step workflow describing the full meeting prep process: fetch event → extract attendees → retrieve linked docs → produce summary.
Include an example of expected output (e.g., a sample meeting prep summary with agenda items, attendee list, and document links) so Claude knows what to produce.
Clarify what Claude should do after running the command — should it summarize the meeting details, create a prep document, or just display raw data?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what meetings or calendars are. Every section serves a purpose — flags, examples, tips, and cross-references are all tightly written. | 3 / 3 |
Actionability | Provides concrete CLI commands and a flags table, but lacks detail on what the actual output looks like (no example output shown) and doesn't describe what Claude should do with the retrieved information. The skill describes invocation but not the full workflow of preparing for a meeting. | 2 / 3 |
Workflow Clarity | For a skill titled 'meeting prep,' there is no workflow sequence at all — no steps for gathering agenda, checking attendees, finding linked docs, or synthesizing a prep summary. It's essentially just a single command invocation with no multi-step process described despite the task implying one. | 1 / 3 |
Progressive Disclosure | Clear prerequisite reference to shared skill, well-signaled 'See Also' links to related skills, and content is appropriately scoped for this file without deep nesting. | 3 / 3 |
Total | 9 / 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
a3768d0
- 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.