Gws Calendar
v1.0.13Google Calendar: Manage calendars and events.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (Google Calendar management) align with requiring a 'gws' CLI, but the skill declares no environment credentials while its runtime instructions explicitly point to a ../gws-shared/SKILL.md for auth and security rules. Managing calendars typically requires OAuth/service credentials; those requirements are not declared here.
Instruction Scope
SKILL.md instructs the agent to read ../gws-shared/SKILL.md for authentication, global flags, and security rules. That is a reference to an external file/path outside the skill's own manifest and may contain additional credential access or behavior not represented in this skill's metadata. The instructions also enable destructive Google Calendar operations (e.g., calendars.clear) which require appropriate auth and scopes.
Install Mechanism
No install spec and no code files — instruction-only skill. This is low-risk from a code-install perspective, but it depends on the external 'gws' binary whose provenance is not provided.
Credentials
The skill lists no required env vars or primary credential despite needing authenticated access to Google Calendar. The SKILL.md explicitly refers to auth guidance (and warns about service accounts), implying credential needs that are not declared. This lack of declared credential requirements is disproportionate and opaque.
Persistence & Privilege
The skill does not request always: true and uses default autonomous invocation settings. It does not claim to modify other skills or global agent configuration in its own SKILL.md.
What to consider before installing
Before installing or enabling this skill: 1) Inspect the referenced ../gws-shared/SKILL.md to see exactly how authentication works and what credentials or files it will read or write. 2) Verify the provenance of the required 'gws' CLI (which exact binary/package is expected) — only install a trusted, official release. 3) Confirm what OAuth scopes or service-account credentials will be used; prefer least-privilege, per-account OAuth tokens rather than broad domain-wide delegation or long-lived service accounts. 4) Be cautious with destructive methods (calendars.clear, delete) — test in a sandbox account first. 5) Avoid running any 'gws generate-skills' or other setup commands without reviewing what they create and whether they store secrets on disk. If you cannot review the gws-shared auth instructions or the gws binary source, do not enable the skill.Like a lobster shell, security has layers — review code before you run it.
Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
CLI help (from plugin)
gws calendar --help
Runtime requirements
Binsgws
latest
calendar (v3)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto 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.
Comments
Loading comments...
