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 Google Calendar scheduling capability with good natural trigger terms. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. It could also benefit from listing additional related actions to improve specificity.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to schedule a meeting, check availability, or find open time slots across calendars.'
Expand the list of concrete actions, e.g., 'Query Google Calendar free/busy status for multiple users, find overlapping available time slots, and suggest meeting times.'
| 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—it's essentially one action described. | 2 / 3 |
Completeness | Clearly answers 'what does this do' (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' and 'free/busy' creates a clear, unique trigger. | 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.
This is a concise, actionable recipe with concrete CLI commands that Claude can execute directly. Its main weakness is the vague middle step—interpreting the freebusy response and handling the case where no overlapping slots exist could be more explicit. Overall it's a solid simple skill.
Suggestions
Add a brief example of the freebusy response format so Claude knows how to parse overlapping free slots in step 2.
Add guidance for the case where no overlapping free slots are found (e.g., suggest expanding the time range or querying the next day).
| 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 concrete, copy-paste ready CLI commands with realistic JSON payloads and flags. Both the query and event creation steps are executable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but step 2 ('Review the output to find overlapping free slots') is vague—no guidance on how to interpret the freebusy response or what the output structure looks like. There's no validation or error handling (e.g., what if no free slots exist). | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It clearly references a prerequisite skill (`gws-calendar`) and keeps content well-organized with a single focused section. | 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
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.