Google Calendar API access for managing calendars, events, and sharing rules.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-calendarExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-calendar 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 gws-calendar. Access via /gws-calendar 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
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws calendar <resource> <method> [flags]
| Command | Description |
|---|---|
+insert |
create a new event |
+agenda |
Show upcoming events across all calendars |
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.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.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.stop — Stop watching resources through this channelget — Returns the color definitions for calendars and 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.query — Returns free/busy information for a set of calendars.get — Returns a single user setting.list — Returns all user settings for the authenticated user.watch — Watch for changes to Settings resources.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.
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: gws-calendar is focused, and the summary matches what you get after install.
Registry listing for gws-calendar matched our evaluation — installs cleanly and behaves as described in the markdown.
gws-calendar has been reliable in day-to-day use. Documentation quality is above average for community skills.
gws-calendar fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in gws-calendar — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend gws-calendar for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
gws-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: gws-calendar is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: gws-calendar is focused, and the summary matches what you get after install.
gws-calendar fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 73