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 conveys the general purpose of meeting preparation within a Google ecosystem but lacks concrete action verbs, explicit trigger guidance, and sufficient keyword coverage. It would benefit from specifying exact actions performed and adding a 'Use when...' clause to help Claude distinguish this skill from other Google or meeting-related skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to prepare for a meeting, review upcoming calendar events, or gather meeting materials.'
Replace the noun list with concrete action verbs, e.g., 'Creates meeting agendas, lists attendees from Google Calendar, and links relevant Google Docs.'
Include more natural trigger terms and variations such as 'Google Calendar', 'meeting prep', 'upcoming meetings', 'participants', and 'schedule'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (meeting preparation) and some actions (agenda, attendees, linked docs), but these are more like nouns/features than concrete verbs describing specific actions. It doesn't detail what it actually does with these elements (e.g., 'creates agendas', 'looks up attendees', 'attaches documents'). | 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', which users might say. However, it misses common variations like 'calendar', 'schedule', 'Google Calendar', 'meeting prep', 'participants', or 'Google Docs'. The 'Google Workflow' prefix is somewhat technical/internal. | 2 / 3 |
Distinctiveness Conflict Risk | The meeting preparation focus provides some specificity, but 'Google Workflow' is broad and could overlap with other Google-related skills. The mention of agenda, attendees, and linked docs helps narrow it, but without clearer boundaries it could conflict with general calendar or document management skills. | 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 well-structured and concise with good cross-references, but it fundamentally under-delivers 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.
Suggestions
Add a multi-step workflow describing how Claude should prepare for a meeting: e.g., 1) fetch next event, 2) list attendees, 3) retrieve linked docs, 4) summarize agenda — even if each step is a single command.
Include an example output showing what the command returns (attendees list, agenda text, linked document URLs) so Claude knows what to expect and how to present results.
Clarify what Claude should do with the retrieved data — should it summarize, format a briefing, or just display raw output?
| 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 unnecessary inline detail. | 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
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.