recipe-find-free-time
Query Google Calendar free/busy status for multiple users to find a meeting slot.
83
80%
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-find-free-time/SKILL.mdQuality
Discovery
72%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 concise and clearly identifies a specific capability around Google Calendar availability checking. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are strong and naturally match what users would say.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to schedule a meeting, check availability, or find a time that works for multiple people on Google Calendar.'
Consider listing additional concrete actions if the skill supports them, such as 'check participant availability, suggest open time slots, compare schedules across time zones.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and a specific action (query free/busy status, find a meeting slot), but doesn't list multiple concrete actions beyond the single workflow of checking availability. | 2 / 3 |
Completeness | Clearly answers 'what' (query free/busy status to find meeting slots), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Google Calendar', 'free/busy', 'meeting slot', 'multiple users' — these are terms users would naturally use when looking for scheduling availability. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Google Calendar free/busy querying for scheduling is distinct and unlikely to conflict with other skills. The combination of 'Google Calendar' + 'free/busy' + 'meeting slot' creates a clear, unique identity. | 3 / 3 |
Total | 10 / 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.
A concise, actionable recipe with executable commands and good structure. The main weakness is step 2, which is vague about how to interpret the free/busy response and lacks a validation checkpoint before creating the event. Overall a solid simple skill that could benefit from slightly more guidance on interpreting the query output.
Suggestions
Add a brief example of the freebusy query response format so Claude knows how to interpret overlapping free slots in step 2.
Add a validation note before step 3, e.g., 'Confirm the selected time slot shows no busy entries for all attendees before creating the event.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Google Calendar is or how free/busy works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete JSON payloads and specific flags. The commands are copy-paste ready with realistic example data. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but step 2 ('Review the output to find overlapping free slots') is vague—it doesn't explain how to interpret the freebusy response or what to look for. There's no validation that the chosen slot is actually free before creating the event. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It references the prerequisite skill clearly and keeps content well-organized without needing external files. | 3 / 3 |
Total | 11 / 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.