Menú
Google Calendar: Create a new event.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Standalone Speedrift-native planning and Workgraph compilation. PlanForge V2 uses a model-mediated planner persona, validated schema, critic pass, and Speedrift module/model assignment to produce an executable Workgraph with tests, evals, drift gates, and fix loops. Use directly when you need discovery, decomposition, or an end-to-end Speedrift execution graph.
Use when agents need Google Workspace access across Drive, Docs, Sheets, Calendar, Slides, Tasks, People, or related GWS services; choose the correct gws-account profile before using gws CLI or domain-specific gws-* skills. Do not use Python gspread/googleapiclient or custom OAuth. Use msgvault for email search/reading.
gws CLI shared reference. Use before any gws-* skill to choose the correct gws-account profile, avoid raw gws config drift, and apply shared Drive flags, auth checks, output formatting, and security rules.
Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion
Workgraph-first drift-control autopilot (driftdriver + coredrift + optional specdrift/datadrift/depsdrift/uxdrift/therapydrift/yagnidrift/redrift) with optional Amplifier runtime integration. Use for start/resume, dependency-aware execution, and keeping code/spec/intent synced without hard blocks.
Use when managing projects, programs, initiatives, dependencies, schedules, Workboard/PAIA Program tasks, Linear/GitHub/Google/Folio work, cross-system planning, weekly operating reviews, stale work rescue, operational task decomposition, or research-backed planning for Braydon's work. Covers a model-mediated program panel, research/evidence discovery, model-authored records, HTML inspection packets, change plans, approval gates, and execution ledgers.
Basado en la clasificación ocupacional SOC
| name | gws-calendar-insert |
| description | Google Calendar: Create a new event. |
| metadata | {"version":"0.22.1","openclaw":{"category":"productivity","requires":{"bins":["gws"]},"cliHelp":"gws calendar +insert --help"}} |
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
create a new event
gws calendar +insert --summary <TEXT> --start <TIME> --end <TIME>
| 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 |
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 alice@example.com
gws calendar +insert --summary 'Meet' --start ... --end ... --meet
[!CAUTION] This is a write command — confirm with the user before executing. Autonomous agents must not run this through the agent-safe profile. The primary default profile permits Workspace artifact writes but must not include Calendar write scopes; only
primary-humanmay create events, and only after the user explicitly approves the live calendar mutation.