Calendly

Inspect Calendly events, invitees, availability schedules, and webhook subscriptions, and perform available scheduling actions such as creating scheduling li...

Security Scan

The skill's requested capabilities, instructions, and lack of required credentials or install steps align with its stated Calendly scheduling purpose.

Purpose & Capability

The name/description match the instructions: inspecting events, invitees, schedules, webhooks and performing supported scheduling actions. The skill requests no unrelated binaries, env vars, or config paths that would be inconsistent with Calendly integration.

Instruction Scope

SKILL.md limits behavior to checking connection state, inspecting available tool actions before writes, asking clarifying questions, and refusing to request raw secrets or use unofficial login flows. It explicitly forbids reading unrelated local files or env vars.

Install Mechanism

No install spec and no code files — instruction-only skill. This is low-risk and consistent with a skill that delegates actual API calls to a connected Calendly integration/toolset.

Credentials

No required environment variables, credentials, or config paths are declared. The SKILL.md also instructs not to ask users to paste tokens or use harvested session flows, which is proportionate to the stated purpose.

Persistence & Privilege

always is false and the skill does not request persistent system-wide privileges. It is user-invocable and permits normal autonomous invocation, which is the platform default and appropriate here.

Assessment

This skill is internally consistent and instruction-only, but it depends on a separate Calendly connection/toolset to actually perform actions. Before using: (1) confirm your Calendly account is connected via the platform's official OAuth or integrations UI (do not paste tokens into chat), (2) review the permissions the connected account grants before allowing write actions (creating links, marking no-shows), and (3) ask the agent to show which actions are currently available and to summarize any write it will perform before proceeding.

Work with Calendly from chat to inspect events, invitees, schedules, and available booking actions when they are supported by the connected integration.

Overview

Use this skill for common Calendly work such as:

• viewing events and invitees
• checking availability schedules
• reviewing webhook subscriptions
• creating scheduling links when supported
• marking invitees as no-shows when explicitly requested and supported

Keep responses practical, concrete, and grounded in what is actually available.

How to work

Use this workflow:

1. Identify the Calendly task
2. Check whether Calendly is connected
3. Check which Calendly tools and actions are currently available
4. Prefer read and inspection actions before writes when they reduce ambiguity
5. If a write is requested, state clearly what will change before doing it
6. If multiple events, users, or invitees may match, ask the user to disambiguate
7. If the requested capability is not available, say so plainly

What this helps with

Examples:

• get a Calendly event
• list invitees for an event
• list upcoming or recent events
• check a user's availability schedules
• review webhook subscriptions
• create a scheduling link
• mark an invitee as a no-show when supported

Connection

Before doing Calendly work:

• verify whether Calendly is connected
• if it is not connected, guide the user through the available connection flow
• do not ask the user to paste raw access tokens, session cookies, passwords, or private credentials into chat
• do not use unofficial login or harvested browser-session flows

Treat the current connection state and live tool catalog as authoritative.

Safety

Operate with a narrow scope:

• use only the minimum inputs needed for the requested Calendly task
• do not access unrelated local files, secrets, environment variables, or configuration data
• do not perform unrelated outbound calls
• clearly disclose when an action will create links or modify event participation state
• prefer the least risky action that still solves the request

Behavioral rules

Follow these rules every time:

• use the live Calendly tool set as the source of truth
• do not claim full Calendly coverage
• do not fabricate unsupported event, invitee, schedule, or webhook actions
• do not imply write support just because read support exists
• ask clarifying questions when the intended event or invitee is ambiguous
• summarize risky or user-facing changes before performing them

Example requests

• Show this Calendly event
• List invitees for this Calendly event
• Show upcoming Calendly events
• Check this user's availability schedules
• List Calendly webhook subscriptions
• Create a Calendly scheduling link if supported
• Mark this invitee as a no-show if supported and explicitly requested

Limits

Actual capability depends on:

• whether the user's Calendly account is connected
• which Calendly actions are currently exposed by the connected tool set
• the permissions granted by the connected Calendly account

If an action is unavailable, say so plainly. Do not pretend the skill can do it anyway.

Response style

Be clear and operational:

• say what was found
• say what is supported
• say when Calendly must be connected first
• say when an action will write data
• say when a capability is unavailable

Keep answers useful, direct, and easy to audit.

Resources

• Calendly API Overview — https://developer.calendly.com/
• Calendly API Reference — https://developer.calendly.com/api-docs
• Calendly Developer Docs — https://developer.calendly.com/
• Discord Support — https://discord.gg/KjN3xcTvw4