Calendly Automation
v0.1.1Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.
⭐ 1· 1.4k·0 current·0 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 (Calendly automation) match the SKILL.md instructions: all declared tools and procedures are Calendly operations (list events, invitees, scheduling links, org management) invoked via Rube MCP. There are no unexpected credentials, binaries, or unrelated capabilities requested.
Instruction Scope
Instructions stay within the Calendly domain and repeatedly require calling RUBE_SEARCH_TOOLS and the CALENDLY_* toolkit; they do instruct the agent to open OAuth auth links and to manage connections via RUBE_MANAGE_CONNECTIONS. The skill does not ask the agent to read local files or unrelated environment variables, but it does route operations through an external MCP server (rube.app) and an OAuth flow — which means data and auth exchanges occur off‑agent and require user consent.
Install Mechanism
No install spec and no code files — instruction‑only. This is low risk from an install perspective because nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The runtime assumes the user will authorize Calendly via the Rube MCP connection (OAuth), which is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-enabled, and it does not request persistent system modifications. Autonomous invocation is allowed by platform default but the skill does not escalate privileges or modify other skills.
Assessment
This skill is coherent for Calendly automation, but note it relies on a third‑party MCP endpoint (https://rube.app/mcp) and an OAuth connection to your Calendly account. Before installing: verify you trust rube.app (review its privacy/security posture), confirm any OAuth consent screens carefully (scope and account selection), and avoid granting unnecessary organization‑level admin rights unless you intend org management. The skill warns to confirm destructive actions (e.g., cancellations) — insist on explicit user confirmation before performing them. If you need higher assurance, ask the skill author for a privacy/data-flow description (where API calls and tokens are proxied/stored) or run these workflows using your own verified MCP instance.Like a lobster shell, security has layers — review code before you run it.
latestvk97d13q79kvas128h6cqm0x73980q8k5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
