Calcom Cli
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill fits its Cal.com calendar-management purpose, but it relies on an external CLI install, local token storage, and commands that can change calendar data.
Before installing, verify the external CLI source, consider pinning or reviewing the package, use a scoped Cal.com token if possible, and require explicit confirmation before the agent cancels, deletes, or reschedules anything.
Findings (3)
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.
Installing the skill’s recommended tooling may run third-party code before it handles your Cal.com account token.
The setup path installs external, unpinned tooling and may execute remote installer code. This is purpose-aligned for a CLI skill, but users should verify the source before running it.
npx api2cli install Melvynx/calcom-cli ... bun --version || curl -fsSL https://bun.sh/install | bash
Install only from sources you trust, prefer pinned versions where possible, and review the GitHub/api2cli package before providing credentials.
Anyone or any process that can access the stored token may be able to act on the connected Cal.com account within the token’s permissions.
The skill uses a Cal.com API token and stores it persistently on disk. That is expected for this integration, but it is sensitive account authority.
calcom-cli auth set "your-token" ... Auth commands: `auth set <token>`, `auth show`, `auth remove`, `auth test` ... Token is stored in `~/.config/tokens/calcom-cli.txt`.
Use the least-privileged token available, avoid exposing `auth show` output, secure the local token file, and run `auth remove` when finished.
Mistaken commands could cancel or reschedule meetings or remove calendar configuration.
The documented CLI commands can change or delete Cal.com resources. These actions match the skill purpose, but they can affect meetings, availability, and attendees.
Bookings: ... `cancel <uid>` ... `reschedule <uid>` ... `confirm <uid>` ... Schedules: ... `delete <id>` ... Event Types: ... `delete <id>`
Ask the agent to show the target booking/schedule/event type first and require confirmation before canceling, deleting, or rescheduling.
