recipe-find-free-time
Query Google Calendar free/busy status for multiple users to find a meeting slot.
Profile →npx skills add googleworkspace/cli --skill recipe-find-free-time --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Find Free Time Across Calendars > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar` Query Google Calendar free/busy status for multiple users to find a meeting slot. ## Steps 1. Query free/busy: `gws calendar freebusy query --json '{"timeMin": "2024-03-18T08:00:00Z", "timeMax": "2024-03-18T18:00:00Z", "items": [{"id": "user1@company.com"}, {"id": "user2@company.com"}]}'` 2. Review the output to find overlapping free slots 3. Create event in the free slot: `gws calendar +insert --summary 'Meeting' --attendee user1@company.com --attendee user2@company.com --start '2024-03-18T14:00:00' --end '2024-03-18T14:30:00'`
- Steps
What does the recipe-find-free-time skill do?
Query Google Calendar free/busy status for multiple users to find a meeting slot.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-find-free-time --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.