recipe-reschedule-meeting
Move a Google Calendar event to a new time and automatically notify all attendees.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-reschedule-meeting72
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
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 clearly articulates a specific capability (moving calendar events and notifying attendees) with good distinctiveness for Google Calendar operations. However, it critically lacks explicit trigger guidance ('Use when...') and could benefit from additional natural trigger terms users might say when needing this functionality.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to reschedule a meeting, move a calendar event, or change the time of an appointment on Google Calendar'
Include common variations of trigger terms: 'reschedule', 'meeting', 'gcal', 'appointment', 'change time', 'move meeting'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Move a Google Calendar event', 'new time', and 'automatically notify all attendees'. These are clear, actionable capabilities. | 3 / 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 good terms like 'Google Calendar', 'event', 'notify', 'attendees', but missing common variations users might say like 'reschedule', 'meeting', 'gcal', or 'change time'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Google Calendar event rescheduling with attendee notification. Unlikely to conflict with other skills due to the specific platform and action combination. | 3 / 3 |
Total | 9 / 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 actionable, executable commands for rescheduling calendar events. The main weakness is the lack of a verification step after the update to confirm success or handle potential errors (wrong event ID, permission issues, etc.).
Suggestions
Add a verification step after the patch command, such as re-fetching the event to confirm the time was updated correctly
Consider adding a note about error handling if the event ID is not found or the user lacks permission to modify the event
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Google Calendar is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with complete parameter structures including JSON payloads. The commands are specific and concrete. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (find → get → update), but there's no validation checkpoint to confirm the update succeeded or handle errors if the event ID is wrong or the update fails. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. It clearly references the prerequisite skill and keeps content focused without unnecessary nesting. | 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.