Gws Calendar Insert

Google Calendar: Create a new event.

Security Scan

The skill is a thin instruction wrapper that calls a local 'gws' CLI to create Google Calendar events and its declared requirements line up with that purpose, but you should inspect the referenced gws-shared auth instructions before running it.

Purpose & Capability

Name/description say 'create a calendar event' and the SKILL.md only invokes the 'gws' CLI's calendar +insert command. The declared required binary ('gws') is appropriate and proportional to the stated purpose.

Instruction Scope

Instructions are narrowly scoped to running 'gws calendar +insert' with event flags. However the file refers to ../gws-shared/SKILL.md for auth and security rules and suggests running 'gws generate-skills' if missing — that external doc or generator may request or create credentials/config, so you should read gws-shared before executing write operations.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes risk because nothing is fetched or written by the skill itself.

Credentials

This skill declares no environment variables, which is consistent because it delegates auth to gws-shared. That external file likely contains the actual auth requirements (OAuth tokens, service account keys, or environment vars). Verify gws-shared to confirm what credentials will be used and ensure they are limited in scope.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent or elevated platform privileges and does not modify other skills' configs. It performs a user-visible write action (creating calendar events), and SKILL.md explicitly cautions to confirm before executing.

Assessment

This skill itself is just an instruction wrapper that requires the local 'gws' CLI. Before installing or running it: (1) open the referenced ../gws-shared/SKILL.md to see how authentication is handled and which credentials or tokens will be used or created; (2) verify the provenance of the 'gws' binary (is it from a trusted vendor/repository?) because the skill delegates all actions to that tool; (3) be aware this is a write command — confirm with the user before creating events, and check whether the auth used grants broad access to your Google account; (4) avoid running 'gws generate-skills' until you review what files it will create and whether it requests credentials. If you want higher assurance, inspect gws-shared and the gws CLI source or documentation to see exactly what credentials, scopes, and network endpoints are involved.

calendar +insert

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

create a new event

Usage

gws calendar +insert --summary <TEXT> --start <TIME> --end <TIME>

Flags

Flag	Required	Default	Description
--calendar	—	primary	Calendar ID (default: primary)
--summary	✓	—	Event summary/title
--start	✓	—	Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z)
--end	✓	—	End time (ISO 8601)
--location	—	—	Event location
--description	—	—	Event description/body
--attendee	—	—	Attendee email (can be used multiple times)
--meet	—	—	Add a Google Meet video conference link

Examples

gws calendar +insert --summary 'Standup' --start '2026-06-17T09:00:00-07:00' --end '2026-06-17T09:30:00-07:00'
gws calendar +insert --summary 'Review' --start ... --end ... --attendee [e-mail]
gws calendar +insert --summary 'Meet' --start ... --end ... --meet

Tips

• Use RFC3339 format for times (e.g. 2026-06-17T09:00:00-07:00).
• The --meet flag automatically adds a Google Meet link to the event.

[!CAUTION] This is a write command — confirm with the user before executing.

See Also

• gws-shared — Global flags and auth
• gws-calendar — All manage calendars and events commands