Aerobase Calendar
PendingAudited by VirusTotal on May 11, 2026.
Overview
No VirusTotal analysis has been recorded yet. File reputation checks will appear here once the artifact hash has been scanned.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Connecting the skill may let Aerobase read or modify Google Calendar data according to the OAuth permissions granted.
The skill connects a Google Calendar account through OAuth. This is expected for calendar sync, but it grants account-level calendar access through the Aerobase service.
POST /api/calendar/connect — initiate OAuth (`{ provider: "google" }`)Review the Google OAuth consent scopes before connecting, and use the provided disconnect/revoke options if you no longer want the integration.
Incorrect or unintended flight changes could create confusing calendar entries or remove/update synced travel events.
The skill can create, update, and remove calendar events automatically when flight data changes. This is aligned with the sync purpose, but it affects a third-party account.
Auto-Sync - Flight added → calendar event created - Flight cancelled → calendar event updated/removed - Flight time changed → calendar event updated, conflicts rechecked
Check sync preferences and review calendar changes, especially when syncing an entire trip or after flight cancellations.
Meeting names, locations, and schedule details may be exposed to the Aerobase-backed agent workflow.
The agent retrieves event titles, times, and locations into its working context to calculate body-clock conflicts. This is purpose-aligned and scoped, but calendar details can be sensitive.
Returns calendar events for the next 7 days: ... "title": "Team Standup", "start": ..., "end": ..., "location": "Zoom"
Use the integration only with calendars you are comfortable sharing with Aerobase, and avoid connecting highly private calendars unless needed.