ClawHub
Back to skill

Security audit

Gcalcli Calendar

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed Google Calendar helper that uses gcalcli, with the main risk being fast calendar edits and deletions when a request appears unambiguous.

Install only if you are comfortable letting an agent use your existing gcalcli Google Calendar session to read events and make calendar changes. If you want a safer workflow, edit SKILL.md to require confirmation before every delete or delete-and-recreate edit.

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill explicitly instructs immediate execution of destructive delete/edit actions without a user-facing confirmation step when a single match is found. In a calendar-management context, semantic matching and bounded agenda scans can still misidentify events, so this creates a realistic risk of unintended irreversible deletion from an agent acting too quickly.

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
### Safety guards in place

The skill does NOT blindly delete. All of these must hold before executing without confirmation:

1. **Explicit user request** — the user must have asked for the action in their message.
2. **Single unambiguous match** — exactly one event matches in a tight, bounded time window.
Confidence
87% confidence
Finding
The README explicitly endorses executing destructive calendar actions without an extra confirmation step when the agent believes the request is unambiguous. Even with guardrails, natural-language ambiguity, incorrect event matching, or prompt-manipulated user context can cause unintended deletion or modification of calendar data. In this context the impact is limited to calendar integrity rather than code execution, but autonomous destructive action still creates real risk.

Static analysis

No suspicious patterns detected.