recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
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-plan-weekly-schedule/SKILL.mdQuality
Discovery
67%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 communicates specific actions around Google Calendar gap-filling, making it distinctive and actionable. However, it lacks an explicit 'Use when...' clause and could benefit from additional trigger terms that users would naturally say (e.g., 'schedule', 'free time', 'availability'). The use of second person 'your' is a minor voice issue but the description is otherwise concise and clear.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to review their weekly schedule, find open time slots, or fill gaps in their Google Calendar.'
Include additional natural trigger terms like 'schedule', 'availability', 'free time', 'meetings', 'open slots', or 'weekly planning'.
| 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 | Clearly answers 'what does this do' (review calendar, identify gaps, add events), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes 'Google Calendar' and 'events' which are natural terms, but misses common variations like 'schedule', 'meetings', 'availability', 'free time', 'booking', or 'calendar management'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Calendar', 'gaps', and 'add events' creates a clear niche that is unlikely to conflict with other skills. It's specifically about calendar gap-filling, not general calendar management. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that provides concrete CLI commands for weekly calendar planning. However, the hardcoded dates reduce real-world executability, and the workflow lacks guidance on how to analyze gaps and validate that new events don't create conflicts. The skill describes the mechanical steps but misses the analytical core of 'identify gaps and fill them.'
Suggestions
Replace hardcoded dates with dynamic placeholders or instructions to compute the current week's date range (e.g., 'Replace timeMin/timeMax with the current week's Monday and Friday').
Add explicit guidance between steps 2 and 3 on how to interpret freebusy output to identify gaps and decide what events to schedule.
Add a validation step after inserting an event to confirm it was created successfully and doesn't overlap with existing events.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Google Calendar is or how scheduling works. Every line serves a purpose. | 3 / 3 |
Actionability | Commands are concrete and copy-paste ready, but the hardcoded dates (2025-01-20, 2026-01-21) make them not directly executable for the user's actual week. The skill also doesn't explain how to identify gaps—it just shows freebusy output without guidance on interpreting it or deciding what events to add. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no validation or feedback loop—no check that the inserted event doesn't conflict, no error handling if insertion fails, and the gap between step 2 (identify gaps) and step 3 (add event) lacks explicit reasoning/decision guidance. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It references the prerequisite gws-calendar skill clearly and keeps content at one level with no unnecessary nesting. | 3 / 3 |
Total | 10 / 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
a3768d0
- 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.