Security audit
Security checks for vulnerabilities and agentic risk
The skill is not deceptive, but it can autonomously create Google Calendar availability events based on vague focus signals, so users should review it carefully before installing.
Install only if you are comfortable with the skill using your configured gog/Google Workspace access to create calendar busy events automatically. Prefer adding explicit consent, a defined event duration, cooldowns, logging, and an easy way to delete events it creates.
The manifest promises a skill that monitors focus and mutes interruptions, but the implementation performs Google Calendar modifications in Google Workspace. This scope mismatch is dangerous because users or orchestrators may grant or trigger the skill under narrower assumptions, while it actually changes external account data and availability signaling.
The skill performs Google Workspace/Calendar operations that go beyond the narrowly described function of monitoring focus and muting interruptions. This creates a permission and expectation gap: a user may approve a passive monitoring skill without realizing it can write to external systems, enabling unintended modifications to calendars and status.
The skill autonomously modifies external workspace data without an explicit warning that it will create Google Calendar events and affect visible availability/state. This is dangerous because it can alter a user's professional signaling and scheduling records without informed consent, potentially affecting coworkers, automated scheduling tools, and audit trails.
The activation condition, 'telemetry from local sensors indicates deep focus,' is vague and broad, leaving substantial room for misclassification and autonomous triggering. In this context, that ambiguity is more dangerous because it directly drives external calendar/status changes, so normal activity could be incorrectly interpreted as 'Deep Work' and cause unintended blocking behavior.
No suspicious patterns detected.
