Google Calendar Update Time

Atomic node skill to exclusively update the start and end time of a Google Calendar event.

Security Scan

The skill's declared purpose (updating only an event's start/end via a CLI) matches its instructions and requirements, but it implicitly relies on a preinstalled, preauthenticated 'gog' CLI and does not document how authentication is handled.

Purpose & Capability

The name/description state a single responsibility (update start/end times). The SKILL.md contains a single, specific command (gog calendar update ...) that aligns with that purpose. Requiring the 'gog' binary is coherent for a native-CLI approach.

Instruction Scope

Instructions are narrow and limited to invoking 'gog calendar update' and validating the returned JSON (including retries). However, the skill assumes the 'gog' CLI is present and authenticated; it does not describe authentication, token storage, or which calendar/event permissions are required. That implicit reliance means the agent will use whatever credentials/config the 'gog' client already has.

Install Mechanism

No install spec and no code files — instruction-only — so nothing is written to disk by the skill itself. This is lower-risk from an installation perspective.

Credentials

The skill declares no environment variables or config paths, which is reasonable for a thin wrapper around a CLI. Nonetheless, it implicitly depends on the CLI's stored credentials (OAuth tokens or config files) and therefore will access Google Calendar data if the CLI is already authenticated. The skill does not request unrelated secrets or extra credentials.

Persistence & Privilege

The skill is not always-enabled, does not request unusual platform privileges, and does not modify other skills or system-wide settings. Autonomous invocation is allowed but is the platform default; nothing in the skill requests elevated persistent privileges.

Assessment

This skill is narrow and coherent, but before installing: verify the 'gog' CLI on the agent is from a trusted source and intentionally authenticated to the calendar you expect; confirm which account and scopes 'gog' has access to (tokens/config under your home directory or CLI config); consider testing on a non-production event/calendar first; and require explicit user consent before allowing the agent to run CLI commands that use existing credentials.

Lean Philosophy (Principles)

• Kaizen (改善): This skill is an atomic node, strictly limited to updating ONLY the start and end times of an event, preventing schema hallucination and ensuring single-responsibility.
• Standardized Work (Hyojun Sagyo): This node represents the most efficient, standardized path for this specific task before automation.
• Jidoka (自働化): This node includes autonomous defect detection. It relies on the CLI's self-healing loop and will report errors if the update fails. You MUST evaluate the output to ensure the time was updated correctly.

This skill allows the agent to update the start and end times of an existing event in Google Calendar using the native CLI. It does NOT update the title, location, or attendees.

Cognitive Directives

WHEN [The start or end time of an existing event needs to be modified or rescheduled] THEN [Execute the native terminal command gog calendar update <calendarId> <eventId> --from "..." --to "..."]

Schema Example

{
  "command": "gog calendar update primary event_id_123 --from \"2026-04-28T10:00:00Z\" --to \"2026-04-28T11:00:00Z\" --json"
}

Jidoka Validation Loop

1. Try: Execute the command.
2. Evaluate: Check the JSON response to confirm start and end times match the requested strings.
3. Correct/Fail: If it failed or hallucinated parameters, retry up to 3 times (max_retries=3) with the exact error.
4. Proceed: Return the final valid JSON.

Expected Output

A JSON object confirming the updated event details with the new start and end times.