recipe-schedule-recurring-event
Create a recurring Google Calendar event with attendees.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-schedule-recurring-event70
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 identifies a specific platform (Google Calendar) and a concrete action but is too narrow in scope and lacks explicit trigger guidance. It fails to tell Claude when to select this skill and doesn't cover the full range of calendar-related user requests it might handle.
Suggestions
Add a 'Use when...' clause with trigger terms like 'schedule meeting', 'create calendar invite', 'set up recurring meeting', 'add attendees'
Expand the capability list to include related actions if applicable (e.g., 'Create, modify, or manage Google Calendar events including recurring meetings and attendee invitations')
Include common user phrasings and variations like 'weekly meeting', 'monthly sync', 'invite people', 'schedule a call'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and one specific action (create recurring event with attendees), but doesn't list multiple concrete actions or capabilities beyond this single use case. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric, missing 'Use when' caps completeness at 2, but this also has a weak 'what' (single action only). | 1 / 3 |
Trigger Term Quality | Includes some natural keywords ('Google Calendar', 'recurring', 'event', 'attendees') but missing common variations like 'meeting', 'schedule', 'invite', 'repeat', 'weekly', 'monthly'. | 2 / 3 |
Distinctiveness Conflict Risk | Specific to Google Calendar which helps distinguish it, but could overlap with other calendar or scheduling skills. The narrow focus on 'recurring events with attendees' provides some distinctiveness but lacks explicit boundary conditions. | 2 / 3 |
Total | 7 / 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 an excellent, well-crafted skill that exemplifies token efficiency and actionability. It provides complete, executable commands without any unnecessary explanation, and includes a verification step. The prerequisite is clearly stated, making dependencies explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations about what calendars or recurring events are. Every line serves a purpose - prerequisite, description, and two actionable steps. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with complete JSON payloads. The example includes all necessary parameters (summary, start/end times, timezone, recurrence rule, attendees). | 3 / 3 |
Workflow Clarity | For this simple two-step task, the workflow is crystal clear: create the event, then verify it was created. The verification step serves as an appropriate validation checkpoint for a non-destructive operation. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single task, the structure is appropriate. Clear prerequisite callout, brief description, and well-organized steps section. No need for external references given the scope. | 3 / 3 |
Total | 12 / 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.