recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-plan-weekly-schedule69
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
42%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 what the skill does with specific actions (review, identify gaps, add events), but fails to provide explicit trigger guidance for when Claude should use it. The use of second person ('your') violates the third-person voice requirement, and the lack of a 'Use when...' clause significantly limits its effectiveness for skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'schedule gaps', 'fill my calendar', 'find free time', 'calendar availability'
Rewrite in third person voice: 'Reviews Google Calendar week, identifies gaps, and adds events to fill them'
Include additional natural trigger terms users might say: 'schedule', 'free time', 'availability', 'book time blocks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Review your Google Calendar week', 'identify gaps', and 'add events to fill them'. 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 'Google Calendar' and 'events' which are natural terms, but misses common variations like 'schedule', 'calendar gaps', 'free time', 'availability', or 'book time'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Calendar' provides some specificity, but 'add events' could overlap with general calendar management skills. The gap-filling focus is somewhat distinctive but not explicitly called out as a trigger. | 2 / 3 |
Total | 8 / 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 immediately actionable commands for calendar management. The main weakness is the lack of validation or error handling guidance—what happens if an event conflicts with existing busy time, or if the insert fails? For a non-destructive operation like calendar management, this is acceptable but could be improved.
Suggestions
Add a brief note on handling conflicts detected in the freebusy query before inserting events
Consider adding guidance on what to do if the insert command fails or returns an error
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what calendars and scheduling are. Every line serves a purpose with concrete commands. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands for each step. Specific examples with actual parameters (dates, durations, summary text) make this immediately actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (check → identify gaps → add → verify), but lacks validation checkpoints. No guidance on what to do if freebusy shows conflicts, or how to handle errors when inserting events. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite reference to the gws-calendar skill, and content is well-organized without needing external files. | 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.