recipe-cancel-and-notify
Delete a Google Calendar event and send a cancellation email via Gmail.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-cancel-and-notify76
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/skillEvaluation — 96%
↑ 5.05xAgent success when using this skill
Validation 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 two-step workflow involving Google Calendar and Gmail integration. However, it lacks explicit trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. The trigger terms are decent but could include more natural user phrasings.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to cancel a calendar event and notify attendees' or 'when removing meetings that require cancellation notices'
Include natural trigger term variations users might say: 'cancel meeting', 'remove appointment', 'notify attendees about cancellation', 'delete event and send notice'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists two specific concrete actions: 'Delete a Google Calendar event' and 'send a cancellation email via Gmail'. Both are clear, actionable operations. | 3 / 3 |
Completeness | Clearly 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 keywords like 'Google Calendar', 'event', 'Gmail', 'cancellation email', but missing common variations users might say like 'cancel meeting', 'remove appointment', 'notify attendees'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Google Calendar deletion with Gmail cancellation notifications. Unlikely to conflict with general calendar or email skills due to the specific combined workflow. | 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 recipe skill that provides clear, actionable commands for canceling meetings. The main weakness is the lack of validation steps - particularly important since this involves destructive operations (deleting events) and external communication (sending emails to attendees).
Suggestions
Add a verification step after deletion to confirm the event was successfully removed before sending the follow-up email
Include error handling guidance for common failure cases (event not found, permission denied, attendee list retrieval)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanations. Every line serves a purpose - prerequisite, warning, and three clear steps with exact commands. | 3 / 3 |
Actionability | Provides fully executable commands with specific flags and parameters. The commands are copy-paste ready with clear placeholders (EVENT_ID, [Title]) for customization. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced but lacks validation checkpoints. No guidance on what to do if the event isn't found, if deletion fails, or how to verify the cancellation was successful before sending follow-up. | 2 / 3 |
Progressive Disclosure | Appropriate for a simple recipe skill. Clear prerequisite reference to dependent skills, well-organized with warning callout and numbered steps. No need for external file references given the scope. | 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.