g-calendar

name	g-calendar
description	Use when the user asks to view or change their Google Calendar. Do not use for daily planning.

Generated from blueprint.yaml. Do not edit this block by hand.

Catalog: personal-assistance; topics: planning, personal-organization, external-integrations; visibility: featured Activation: user-request, skill-workflow; persistent modifier: no

Skill Version: 2

Uses Interfaces:

• g-calendar.source.gateway -> connect-google.interface.default@1
• g-calendar.source.gateway -> g-calendar._rtx.interface.scripts-gcal@1

Setup Requires Setup Of:

• connect-google.interface.setup@1 Setup Order:

1. connect-google.interface.setup
2. g-calendar.interface.setup

Public Interfaces:

• g-calendar.interface.default
• g-calendar.interface.setup

Generated from blueprint.yaml. Do not edit this block by hand.

Instruction Interfaces:

These interfaces are documented prompt surfaces. They are not executed through dispatcher:

• g-calendar.interface.default — Primary LLM-facing skill instructions.
• g-calendar.interface.setup — Primary LLM-facing skill instructions.

Google Calendar

Use g-calendar._rtx.interface.scripts-gcal for calendar reads and writes. Invoke one interface call per operation, minimize network round trips, and issue independent calls in parallel. Use the public process contract for complete subcommand and option shapes; do not improvise invocation forms. Prefer the --all-calendars mode for schedule-wide agenda or search requests.

Reads may proceed directly. Create, update, and delete requests may proceed when the user supplied the necessary details for create, update, or delete. Confirm first when adding attendees because it sends invitations, and before deleting an event that has attendees or is far in the future. Treat move as authorized only when the user explicitly asked to move the identified event to the named destination calendar. Report each mutation's title, time, calendar, and link when available.

Routing calendar operations

Use calendars when the target calendar is unknown. Before create, match the event to the available calendar names. Use a clear match without asking; ask when multiple or no calendars plausibly fit. Do not silently use primary when another calendar is clearly more appropriate.

Agenda and search results are bounded to 50 events and do not paginate. Disclose that bound when the requested range may contain more results. Recurrence, attendees, and free-busy lack dedicated modes. For a genuine one-off unsupported API operation, use the declared token mode only when direct API access is explicitly in scope, keep the token secret, and apply the same confirmation rules. Prefer extending the public interface for repeated use.

Verify writes

Through g-calendar._rtx.interface.scripts-gcal, verify every create and delete and every nontrivial update. The only exception is a metadata-only update limited to summary, description, or location.

• After create, fetch the returned event ID and compare start, end, summary, location, and description with the request. On mismatch, delete the new event and report the intended and observed values.
• Before update, fetch and retain the fields being changed. Fetch again afterward. On mismatch, restore the retained values and report the discrepancy.
• After delete, fetch the event and require status cancelled; Google soft-deletes events rather than returning not-found. If it remains confirmed, report failure.

When completion is uncertain, inspect current event state before retrying; repeated creates can produce duplicates.

Google authorization

For setup or reauthorization, invoke connect-google.interface.default. Its deterministic coordinator creates a credential file, asks Calendar's owner to probe live access, and stores the path only after verification. Treat only complete: true as successful setup; report any incomplete Calendar result and retry through connect-google with the same file.

Existing legacy Calendar credentials remain runtime-readable until a verified credential-file binding replaces them. Do not offer legacy setup as a new route. Replacing the single active Calendar account requires explicit confirmation.