gws-workflow-meeting-prep
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-workflow-meeting-prep59
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
32%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 basic understanding of the skill's purpose (meeting preparation with Google tools) but lacks explicit trigger guidance and uses second person voice ('your next meeting'). The capabilities are listed as brief noun phrases rather than concrete actions, and there's no 'Use when...' clause to help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about upcoming meetings, needs meeting prep, or mentions Google Calendar, meeting agenda, or attendee lists'
Rewrite in third person with concrete action verbs: 'Retrieves meeting details, generates agendas, lists attendees, and surfaces linked documents from Google Calendar'
Include more natural trigger terms users would say: 'calendar', 'schedule', 'upcoming meetings', 'meeting prep', 'Google Calendar'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (meeting preparation) and lists some actions (agenda, attendees, linked docs), but these are brief noun phrases rather than concrete action verbs describing what the skill actually does. | 2 / 3 |
Completeness | Describes what it does (prepare for meetings) 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 relevant keywords like 'meeting', 'agenda', 'attendees', and 'docs', but missing common variations users might say like 'calendar', 'schedule', 'prep', 'upcoming meetings', or 'Google Calendar'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Google Workflow' prefix and meeting-specific focus provide some distinction, but 'prepare for your next meeting' could overlap with general calendar or productivity skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, following good patterns for CLI documentation. However, it lacks clarity on what the command actually outputs - the description promises 'agenda, attendees, and linked docs' but the body doesn't explain what format this takes or show example output. The disconnect between the description and the tips section ('Shows the next upcoming event') creates ambiguity.
Suggestions
Add an example output showing what the meeting prep information looks like (agenda format, attendee list, linked docs display)
Clarify the relationship between 'prepare for meeting' and 'shows the next upcoming event' - these seem inconsistent
Specify what 'linked docs' means and how they are displayed or extracted from the calendar event
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. Every section serves a purpose - usage, flags, examples, and tips are all minimal yet complete. | 3 / 3 |
Actionability | Provides concrete CLI commands and flag documentation, but lacks detail on what the output looks like or what 'prepare for meeting' actually produces. The workflow's actual behavior is vague - 'Shows the next upcoming event' is mentioned only in tips. | 2 / 3 |
Workflow Clarity | This is a simple single-command skill, but the actual workflow/output is unclear. What does 'prepare' mean? Does it display agenda, attendees, docs in a specific format? The description promises 'agenda, attendees, and linked docs' but the tips only mention 'next upcoming event with attendees and description'. | 2 / 3 |
Progressive Disclosure | Appropriate structure for a simple skill with clear references to related skills (gws-shared, gws-workflow). The prerequisite callout is well-placed and the See Also section provides good navigation. | 3 / 3 |
Total | 10 / 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.