recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
Profile →npx skills add googleworkspace/cli --skill recipe-block-focus-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.
# Block Focus Time on Google Calendar > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar` Create recurring focus time blocks on Google Calendar to protect deep work hours. ## Steps 1. Create recurring focus block: `gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Focus Time", "description": "Protected deep work block", "start": {"dateTime": "2025-01-20T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2025-01-20T11:00:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR"], "transparency": "opaque"}'` 2. Verify it shows as busy: `gws calendar +agenda`
- Steps
What does the recipe-block-focus-time skill do?
Create recurring focus time blocks on Google Calendar to protect deep work hours.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-block-focus-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.