recipe-find-free-time

googleworkspace/cli · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/googleworkspace/cli --skill recipe-find-free-time
0 commentsdiscussion
summary

Find overlapping free time slots across multiple Google Calendars for scheduling meetings.

  • Queries free/busy status for multiple users within a specified time range to identify available meeting windows
  • Requires the gws-calendar skill as a dependency
  • Integrates with Google Workspace Calendar API to retrieve availability data and create events with attendees in confirmed free slots
skill.md

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>Find Free Time Across Calendars</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>Query Google Calendar free/busy status for multiple users to find a meeting slot.</p>\n<h2>Steps</h2>\n<ol>\n<li>Query free/busy: <code>gws calendar freebusy query --json '{"timeMin": "2024-03-18T08:00:00Z", "timeMax": "2024-03-18T18:00:00Z", "items": [{"id": "[email protected]"}, {"id": "[email protected]"}]}'</code></li>\n<li>Review the output to find overlapping free slots</li>\n<li>Create event in the free slot: <code>gws calendar +insert --summary 'Meeting' --attendee [email protected] --attendee [email protected] --start '2024-03-18T14:00:00' --end '2024-03-18T14:30:00'</code></li>\n</ol>"}}]

how to use recipe-find-free-time

How to use recipe-find-free-time on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add recipe-find-free-time
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/googleworkspace/cli --skill recipe-find-free-time

The skills CLI fetches recipe-find-free-time from GitHub repository googleworkspace/cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/recipe-find-free-time

Reload or restart Cursor to activate recipe-find-free-time. Access the skill through slash commands (e.g., /recipe-find-free-time) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.762 reviews
  • Advait Li· Dec 28, 2024

    Useful defaults in recipe-find-free-time — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Advait Singh· Dec 24, 2024

    Registry listing for recipe-find-free-time matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Carlos Chawla· Dec 12, 2024

    recipe-find-free-time reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mateo Anderson· Dec 8, 2024

    Registry listing for recipe-find-free-time matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chaitanya Patil· Dec 4, 2024

    Keeps context tight: recipe-find-free-time is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Smith· Nov 27, 2024

    Useful defaults in recipe-find-free-time — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Piyush G· Nov 23, 2024

    recipe-find-free-time has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hana Diallo· Nov 23, 2024

    recipe-find-free-time fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aanya Singh· Nov 19, 2024

    Registry listing for recipe-find-free-time matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dev Martinez· Nov 15, 2024

    Useful defaults in recipe-find-free-time — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 62

1 / 7