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
freebusy query format
Uses gws CLI
100%
100%
Uses calendar subcommand
100%
100%
Uses freebusy query subcommand
0%
100%
Uses --json flag
0%
100%
JSON has timeMin field
0%
100%
JSON has timeMax field
0%
100%
JSON has items array
0%
100%
Items use id field
0%
100%
id values are email addresses
0%
100%
Multiple users in items
0%
100%
Without context: $0.0937 · 23s · 9 turns · 14 in / 1,250 out tokens
With context: $0.1539 · 26s · 12 turns · 15 in / 1,427 out tokens
end-to-end scheduling workflow
Uses freebusy query
25%
100%
--json flag on query
0%
100%
timeMin in query JSON
0%
100%
timeMax in query JSON
0%
100%
Items use id field format
0%
100%
Uses +insert command
0%
100%
Uses --summary flag
0%
100%
Uses --attendees flag
50%
100%
Attendees comma-separated
70%
100%
Uses --start flag
53%
100%
Uses --duration flag
58%
100%
Without context: $0.2142 · 52s · 16 turns · 19 in / 2,800 out tokens
With context: $0.2027 · 36s · 13 turns · 16 in / 2,062 out tokens
calendar event creation flags
freebusy query command
100%
100%
--json flag present
0%
100%
timeMin in payload
0%
100%
timeMax in payload
0%
100%
items array with id field
40%
100%
+insert command used
0%
100%
--summary flag
50%
100%
--attendees flag
50%
100%
Comma-separated attendees
0%
100%
--start flag
50%
100%
--duration in minutes
0%
100%
Without context: $0.2161 · 58s · 13 turns · 61 in / 3,460 out tokens
With context: $0.2587 · 50s · 17 turns · 54 in / 2,863 out tokens
Table of Contents
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.