recipe-find-free-time
Query Google Calendar free/busy status for multiple users to find a meeting slot.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-find-free-time75
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
57%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 reasonably specific about its Google Calendar scheduling functionality and has low conflict risk due to its clear niche. However, it lacks an explicit 'Use when...' clause and could benefit from additional trigger terms that match how users naturally request meeting scheduling help.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'schedule a meeting', 'find availability', 'when is everyone free', or 'check calendars'
Include common user language variations such as 'find a time to meet', 'calendar availability', 'scheduling conflicts', or 'book a meeting'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Calendar) and a specific action (query free/busy status, find meeting slot), but doesn't list multiple concrete actions or capabilities beyond this single use case. | 2 / 3 |
Completeness | Clearly describes what it does (query free/busy status to find meeting slots), but lacks an explicit 'Use when...' clause to guide Claude on when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Google Calendar', 'free/busy', 'meeting slot', and 'multiple users', but misses common variations users might say like 'schedule a meeting', 'find availability', 'when are people free', or 'calendar availability'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Google Calendar free/busy queries for scheduling - unlikely to conflict with other skills due to the specific platform and function mentioned. | 3 / 3 |
Total | 9 / 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 actionable CLI commands for querying calendar availability. The main weakness is step 2, which leaves the interpretation of free/busy response data to inference rather than providing concrete guidance on parsing the output to identify available slots.
Suggestions
Add a brief example of the freebusy response format and how to identify free slots from the busy periods returned
Consider adding guidance for handling the case when no overlapping free slots are found
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands and steps without explaining what Google Calendar is or how free/busy queries work conceptually. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with complete JSON payloads and realistic example values. Commands are copy-paste ready with clear parameter examples. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced but step 2 ('Review the output to find overlapping free slots') is vague and lacks guidance on how to identify free slots from the response. No validation or error handling for edge cases like no available slots. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. The prerequisite skill reference is clearly signaled at the top, and the 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.