Gws Calendar

Google Calendar: Manage calendars and events.

Security Scan

The skill is an instruction-only wrapper for a Google Calendar CLI (gws) and its declared requirements and instructions are consistent with that purpose, but some runtime behavior depends on external shared SKILL.md files you should inspect first.

Purpose & Capability

Name and description map directly to the declared required binary 'gws' and the SKILL.md lists Calendar API resources and methods — these are appropriate for a Google Calendar CLI wrapper.

Instruction Scope

The instructions are limited to running the 'gws calendar' CLI and inspecting schemas; they do not themselves ask to read unrelated system files or exfiltrate data. However the SKILL.md explicitly directs the operator to read ../gws-shared/SKILL.md for auth, global flags, and security rules — that external file is not included here and may contain credential handling or additional behavior that changes the risk profile.

Install Mechanism

There is no install spec (instruction-only). That is low-risk; nothing will be written or executed by the skill itself. The skill does require the external 'gws' binary to be present, but how that binary is installed/where it comes from is outside this package.

Credentials

This skill declares no required environment variables and does not itself request credentials. That fits its purpose. Caveat: authentication details are delegated to the referenced ../gws-shared/SKILL.md, which likely introduces OAuth tokens or API credentials — inspect that file before granting secrets.

Persistence & Privilege

The skill is not always-enabled and uses the default model-invocation behavior. It does not request system-wide configuration changes in the provided content.

Assessment

This skill is an instruction-only wrapper that runs the 'gws' Google Workspace CLI to manage calendars. Before installing or using it: 1) Verify the 'gws' binary on your system comes from a trusted source (official project/repo). 2) Inspect the referenced ../gws-shared/SKILL.md and any helper SKILLs (gws-calendar-insert, gws-calendar-agenda) — those files will define how authentication is handled and may request OAuth tokens or other credentials. 3) Only provide calendar credentials (OAuth client ID/secret, tokens) that are appropriate for the account scope you intend to manage; avoid giving broad organization-level credentials unless necessary. 4) Because this skill has no install and no included code, its behavior is entirely determined by the external gws binary and the shared SKILL.md — review those before granting access.

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.