Gws Calendar Insert

Google Calendar: Create a new event.

Security Scan

This instruction-only skill is internally consistent with its stated purpose (it calls the 'gws' CLI to create Google Calendar events), but you should review the referenced gws-shared auth instructions and trust the gws binary before use because this is a write operation.

Purpose & Capability

The skill name/description say 'create a Google Calendar event' and the only required binary is 'gws', which matches that purpose. There are no unrelated environment variables, install steps, or config paths declared.

Instruction Scope

SKILL.md limits runtime behavior to running the gws CLI command with specific flags for summary, start/end, attendees, and optional Meet link. It does, however, instruct the agent to read ../gws-shared/SKILL.md for auth, global flags, and security rules (or to run `gws generate-skills` if missing). Accessing that shared file or running the generator is expected for auth setup but is a notable external dependency that you should inspect.

Install Mechanism

No install specification and no code files are present (instruction-only). This minimizes install-time risk because nothing from the skill is written to disk or downloaded by the skill itself.

Credentials

The skill declares no required environment variables; authentication is delegated to the 'gws' CLI and the separate gws-shared instructions. That is proportionate for a CLI wrapper, but you should verify what auth the gws CLI expects (OAuth tokens, service account keys, etc.) and ensure it doesn't require unrelated secrets.

Persistence & Privilege

always is false and the skill does not request persistent or cross-skill configuration changes. It performs a write action (creates calendar events), which the SKILL.md itself flags with a CAUTION to confirm with the user before executing.

Assessment

This skill appears coherent for creating Google Calendar events via the 'gws' CLI. Before installing or using it: (1) Verify the 'gws' binary on your system is legitimate and comes from a trusted source; (2) open and review ../gws-shared/SKILL.md (or the output of `gws generate-skills`) to see exactly how authentication is handled and what credentials/tokens are used; (3) remember this is a write operation—confirm with the user/account owner before creating events; (4) if you are concerned about which Google account will be used, check the gws CLI config and OAuth scopes prior to execution.

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