Google Calendar Update Summary

Atomic node skill to exclusively update the summary (title) of a Google Calendar event.

Security Scan

The skill is narrowly scoped to run a Google-Calendar CLI command to update an event title, but it omits provenance and credential details for the required 'gog' binary and implicitly relies on local CLI auth, which is a potential mismatch you should understand before installing.

Purpose & Capability

The skill's name, description, and instructions all claim a single, narrow purpose (update only an event summary) and the required 'gog' binary aligns with that purpose — executing a native CLI is reasonable for this task. However, the skill does not document where 'gog' comes from (official Google tool vs third-party), which matters for trust.

Instruction Scope

SKILL.md instructs a single CLI invocation (gog calendar update <calendarId> <eventId> --summary "...") and to validate the returned JSON; it does not instruct reading arbitrary files or exfiltrating data. The validation/retry loop is narrow and limited to the task.

Install Mechanism

There is no install spec (instruction-only), so nothing is written to disk by the skill itself. That reduces risk, but the runtime requires an external binary ('gog') already present on the system.

Credentials

The skill declares no environment variables or config paths, yet using a Google CLI typically requires authenticated credentials/config stored locally (OAuth tokens, config files). This implicit reliance on existing CLI authentication is not documented. The 'gog' binary may also access the filesystem or network when executed — that privilege isn't represented in the metadata.

Persistence & Privilege

always:false (no forced permanent inclusion) and autonomous invocation is allowed (platform default). The skill does not request elevated persistent privileges or modify other skills' configs.

What to consider before installing

Before installing: verify what 'gog' is (official Google tool or third-party) and only use a vetted binary from an official source. Ensure the CLI is configured with the minimum OAuth scopes needed to edit event summaries and that you understand which local credentials/config files it will read. Test the command manually in a safe account or isolated environment to confirm behavior. If you need a stricter security posture, require the skill documentation to declare credential/config path expectations or avoid installing and run the update manually through a controlled process.

Lean Philosophy (Principles)

• Kaizen (改善): This skill is an atomic node, strictly limited to updating ONLY the summary (title) 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 summary was updated.

This skill allows the agent to update the summary (title) of an existing event in Google Calendar using the native CLI. It does NOT update times, locations, or attendees.

Cognitive Directives

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

Schema Example

{
  "command": "gog calendar update primary event_id_123 --summary \"Updated Sync Meeting\" --json"
}

Jidoka Validation Loop

1. Try: Execute the command.
2. Evaluate: Check the JSON response to confirm summary matches the requested string.
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 summary.