Recurring focus time blocks on Google Calendar to protect deep work hours.
Works with
Creates weekly recurring focus blocks (Monday–Friday by default) that display as busy time, preventing calendar conflicts
Requires the gws-calendar skill and uses Google Calendar's recurrence rules for flexible scheduling
Includes verification step to confirm blocks appear correctly in calendar agenda view
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecipe-block-focus-timeExecute the skills CLI command in your project's root directory to begin installation:
Fetches recipe-block-focus-time from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate recipe-block-focus-time. Access via /recipe-block-focus-time in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<h1>Block Focus Time on Google Calendar</h1>\n<blockquote>\n<p><strong>PREREQUISITE:</strong> Load the following skills to execute this recipe: <code>gws-calendar</code></p>\n</blockquote>\n<p>Create recurring focus time blocks on Google Calendar to protect deep work hours.</p>\n<h2>Steps</h2>\n<ol>\n<li>Create recurring focus block: <code>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"}'</code></li>\n<li>Verify it shows as busy: <code>gws calendar +agenda</code></li>\n</ol>"}}]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: recipe-block-focus-time is focused, and the summary matches what you get after install.
We added recipe-block-focus-time from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: recipe-block-focus-time is the kind of skill you can hand to a new teammate without a long onboarding doc.
recipe-block-focus-time has been reliable in day-to-day use. Documentation quality is above average for community skills.
recipe-block-focus-time has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: recipe-block-focus-time is focused, and the summary matches what you get after install.
Keeps context tight: recipe-block-focus-time is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for recipe-block-focus-time matched our evaluation — installs cleanly and behaves as described in the markdown.
recipe-block-focus-time fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in recipe-block-focus-time — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 59