Trip Calendar

Add trip itineraries, flights, hotel check-ins, and activities to Google Calendar using gog CLI. Handles "add to calendar" and boarding pass parsing.

Security Scan

The skill's requirements and instructions are coherent with its stated purpose (adding trip items to Google Calendar via the gog CLI); the only practical ambiguity is how boarding-pass images are parsed (OCR/vision details are not specified).

Purpose & Capability

Name/description match the declared requirement: the skill adds trip items to Google Calendar and explicitly requires the 'gog' CLI. Asking for the gog binary is proportional and expected for this purpose.

Instruction Scope

Most instructions stay within calendar-creation scope (show exact gog command format, event fields, confirmation rules). The boarding-pass parsing step asks the agent to 'Extract' fields from an image but does not specify how (no OCR tool, no external service, no fallback). Also the rule 'Always use IST (+05:30)' is a behavioral constraint users should be aware of.

Install Mechanism

Instruction-only skill with no install spec or downloaded artifacts; nothing is written to disk by the skill itself. Low installation risk.

Credentials

The skill requests no environment variables or credentials. It relies on the local gog CLI being present and (implicitly) authenticated to the user's Google account — reasonable and proportionate for calendar integration.

Persistence & Privilege

No elevated persistence requested (always is false). Agent invocation autonomy is default and not by itself a concern here.

Assessment

This skill appears to do what it says: it calls your local 'gog' CLI to create calendar events and will only add events after confirmation. Before installing/using it: (1) ensure you have the 'gog' CLI installed and authenticated to the Google account you want to modify — the skill does not request credentials itself; (2) be aware that boarding-pass parsing is underspecified: the agent may rely on built-in vision/OCR or ask you to provide extracted text — confirm how images are handled and whether they are sent to any external OCR service; (3) note the skill forces IST (+05:30) for created events — change may be needed if you want events in another timezone; (4) because boarding passes contain personal data, verify you are comfortable having the agent read those images and confirm calendar additions before proceeding.

When to activate

• User says "add to calendar", "put this on my calendar"
• User forwards a boarding pass screenshot
• After itinerary is finalized and user confirms

Adding itinerary to calendar

When user confirms "add to calendar":

1. Create events for key milestones using gog:

   • ✈️ Flights (with terminal, timing)
   • 🏨 Hotel check-in / check-out (with address)
   • 🥾 Major activities (treks, tours)
   • 🚕 Major transport

2. Command format: gog calendar create primary --summary "✈️ DEL→KLU 6E-2041" --from "2026-03-14T06:00:00+05:30" --to "2026-03-14T07:30:00+05:30" --location "DEL Terminal 1" --description "Reach airport by 4:30 AM"

3. Use emojis in titles: ✈️ flights, 🏨 hotels, 🥾 treks, 🚕 transport

4. Include location and useful details in description

Boarding pass parsing

When user sends boarding pass image:

1. Extract: flight number, date, time, origin, destination, gate/terminal
2. Confirm with user
3. On confirmation, create calendar event

Response

✓ Added 4 events to your Google Calendar: ✈️ DEL→KLU flight (Mar 14, 6 AM) 🏨 Check-in: Parvati Riverside (Mar 14, 1 PM) 🥾 Kheerganga Trek (Mar 15, full day) ✈️ KLU→DEL return (Mar 16, 3:30 PM)

Rules

• Never add without explicit user confirmation
• Always use IST timezone (+05:30)
• Don't create events for every small activity — key milestones only
• If gog is not available, tell user: "Calendar integration isn't set up yet. Here's your itinerary to add manually."