gws-calendar

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 gws-calendar
0 commentsdiscussion
summary

Google Calendar API access for managing calendars, events, and sharing rules.

  • Covers 10+ API resources including events, calendars, ACL rules, calendar lists, free/busy queries, and user settings
  • Supports event operations: create, read, update, delete, import, move between calendars, and query recurring instances
  • Includes calendar management: create secondary calendars, update metadata, clear primary calendars, and manage sharing access
  • Provides helper commands for quick event cre
skill.md

calendar (v3)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws calendar <resource> <method> [flags]

Helper Commands

Command Description
+insert create a new event
+agenda Show upcoming events across all calendars

API Resources

acl

  • delete — Deletes an access control rule.
  • get — Returns an access control rule.
  • insert — Creates an access control rule.
  • list — Returns the rules in the access control list for the calendar.
  • patch — Updates an access control rule. This method supports patch semantics.
  • update — Updates an access control rule.
  • watch — Watch for changes to ACL resources.

calendarList

  • delete — Removes a calendar from the user's calendar list.
  • get — Returns a calendar from the user's calendar list.
  • insert — Inserts an existing calendar into the user's calendar list.
  • list — Returns the calendars on the user's calendar list.
  • patch — Updates an existing calendar on the user's calendar list. This method supports patch semantics.
  • update — Updates an existing calendar on the user's calendar list.
  • watch — Watch for changes to CalendarList resources.

calendars

  • clear — Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.
  • delete — Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars.
  • get — Returns metadata for a calendar.
  • insert — Creates a secondary calendar. The authenticated user for the request is made the data owner of the new calendar.

Note: We recommend to authenticate as the intended data owner of the calendar. You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user. Don't use a service account for authentication. If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior.

  • patch — Updates metadata for a calendar. This method supports patch semantics.
  • update — Updates metadata for a calendar.

channels

  • stop — Stop watching resources through this channel

colors

  • get — Returns the color definitions for calendars and events.

events

  • delete — Deletes an event.
  • get — Returns an event based on its Google Calendar ID. To retrieve an event using its iCalendar ID, call the events.list method using the iCalUID parameter.
  • import — Imports an event. This operation is used to add a private copy of an existing event to a calendar. Only events with an eventType of default may be imported. Deprecated behavior: If a non-default event is imported, its type will be changed to default and any event-type-specific properties it may have will be dropped.
  • insert — Creates an event.
  • instances — Returns instances of the specified recurring event.
  • list — Returns events on the specified calendar.
  • move — Moves an event to another calendar, i.e. changes an event's organizer. Note that only default events can be moved; birthday, focusTime, fromGmail, outOfOffice and workingLocation events cannot be moved.
  • patch — Updates an event. This method supports patch semantics.
  • quickAdd — Creates an event based on a simple text string.
  • update — Updates an event.
  • watch — Watch for changes to Events resources.

freebusy

  • query — Returns free/busy information for a set of calendars.

settings

  • get — Returns a single user setting.
  • list — Returns all user settings for the authenticated user.
  • watch — Watch for changes to Settings resources.

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws calendar --help

# Inspect a method's required params, types, and defaults
gws schema calendar.<resource>.<method>

Use gws schema output to build your --params and --json flags.

how to use gws-calendar

How to use gws-calendar 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 gws-calendar
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 gws-calendar

The skills CLI fetches gws-calendar 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/gws-calendar

Reload or restart Cursor to activate gws-calendar. Access the skill through slash commands (e.g., /gws-calendar) 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.673 reviews
  • Sakura Reddy· Dec 24, 2024

    Solid pick for teams standardizing on skills: gws-calendar is focused, and the summary matches what you get after install.

  • Hana Perez· Dec 16, 2024

    Registry listing for gws-calendar matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Hana Chawla· Dec 12, 2024

    gws-calendar has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Noah Ghosh· Dec 12, 2024

    gws-calendar fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hana Bhatia· Dec 8, 2024

    Useful defaults in gws-calendar — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Hana Sanchez· Dec 4, 2024

    I recommend gws-calendar for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Maya Yang· Nov 27, 2024

    gws-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Benjamin Bansal· Nov 23, 2024

    Keeps context tight: gws-calendar is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hana Gonzalez· Nov 19, 2024

    Solid pick for teams standardizing on skills: gws-calendar is focused, and the summary matches what you get after install.

  • Kiara Gonzalez· Nov 7, 2024

    gws-calendar fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 73

1 / 8