Cal Com Automation
v0.1.0Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.
⭐ 1· 1.6k·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description claim to automate Cal.com tasks; SKILL.md exclusively describes calling Rube MCP tool actions (CAL_* calls) to list/create bookings, check availability, manage webhooks, teams, and orgs. The requested capabilities align with the stated purpose.
Instruction Scope
Instructions are scoped to Rube MCP operations and Cal toolkit calls (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, CAL_*). They do not ask the agent to read arbitrary local files or unrelated environment variables. Important note: the runtime flow requires adding https://rube.app/mcp as an MCP server and completing an auth flow returned by RUBE_MANAGE_CONNECTIONS, which means credentials and Cal.com access will be brokered by that external endpoint — the SKILL.md tells the user to perform this, so the security depends on trusting rube.app.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required env vars or credentials. However, it instructs the user/agent to perform an external connection/authentication via Rube MCP (RUBE_MANAGE_CONNECTIONS) to obtain an ACTIVE Cal.com connection. This is reasonable for the stated purpose, but it centralizes authentication through the external MCP service rather than local API keys; users should verify the trustworthiness and scopes of that flow.
Persistence & Privilege
always is false, skill is user-invocable and not automatically forced into every agent run. There is no install that modifies other skills or system-wide config. The only persistence action the docs recommend is adding an MCP server endpoint to the client's configuration — that is a client-side change initiated by the user.
Assessment
This skill is coherent for automating Cal.com via a third-party broker (Rube MCP). Before installing or using it: 1) Confirm you trust the MCP endpoint (https://rube.app/mcp) because completing the described auth flow will grant that broker access to your Cal.com account and data; 2) Review the OAuth/auth link and scopes returned by RUBE_MANAGE_CONNECTIONS so you know what access will be granted; 3) Don't add unknown MCP endpoints in sensitive or production environments without an organizational review; 4) If you prefer, use native Cal.com API keys or your own trusted broker instead of a third-party MCP.Like a lobster shell, security has layers — review code before you run it.
latestvk975a9e81cszbnc58bygjgk72s80m679
License
MIT-0
Free to use, modify, and redistribute. No attribution required.