recipe-schedule-recurring-event
Create a recurring Google Calendar event with attendees.
75
70%
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/recipe-schedule-recurring-event/SKILL.mdQuality
Discovery
40%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 is narrowly focused on a single specific task (creating recurring Google Calendar events with attendees), which gives it good distinctiveness but limits its usefulness as a comprehensive skill description. It lacks a 'Use when...' clause and could benefit from broader trigger terms and additional capability details.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to schedule a recurring meeting, set up a repeating calendar event, or invite attendees to a Google Calendar event.'
Expand trigger terms to include natural variations like 'schedule', 'repeating meeting', 'weekly event', 'calendar invite', 'invite people'.
Consider broadening the capability description if the skill handles more than just recurring events with attendees, e.g., 'Create, modify, and manage Google Calendar events including recurring schedules and attendee invitations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and a specific action (create a recurring event with attendees), but only describes a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is narrow enough that this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Calendar', 'recurring', 'event', and 'attendees' that users would say, but misses common variations like 'repeating meeting', 'schedule', 'invite', 'weekly/daily event', or 'calendar invite'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Calendar', 'recurring event', and 'attendees' creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%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 a complete, executable example for creating a recurring Google Calendar event. It includes all necessary details (recurrence rule, attendees, time zones) in a copy-paste-ready command and includes a verification step. The prerequisite is clearly called out.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean — no unnecessary explanations. Every line serves a purpose: prerequisite, description, and two concrete steps. | 3 / 3 |
Actionability | Provides a fully copy-paste-ready CLI command with complete JSON payload including recurrence rules, attendees, time zones, and a verification command. | 3 / 3 |
Workflow Clarity | For this simple two-step task, the sequence is clear: create the event, then verify. The verification step serves as an explicit validation checkpoint, which is appropriate for a non-destructive creation operation. | 3 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with a single task, the content is well-organized with a clear prerequisite callout, description, and numbered steps. No external references are needed. | 3 / 3 |
Total | 12 / 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.