📦 Calendly

Calendly

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

Overview

Use this 技能 for common Calendly work such as:

viewing 事件 and invitees 检查ing avAIlability schedules reviewing 网页hook subscriptions creating scheduling links when supported marking invitees as no-shows when explicitly 请求ed and supported

Keep 响应s practical, concrete, and grounded in what is actually avAIlable.

How to work

Use this 工作流:

Identify the Calendly task 检查 whether Calendly is connected 检查 which Calendly 工具s and actions are currently avAIlable Prefer read and inspection actions before writes when they reduce ambi图形界面ty If a write is 请求ed, 状态 clearly what will change before doing it If multiple 事件, users, or invitees may match, ask the user to disambiguate If the 请求ed capability is not avAIlable, say so plAInly What this helps with

Examples:

获取 a Calendly event 列出 invitees for an event 列出 upcoming or recent 事件 检查 a user's avAIlability schedules review 网页hook subscriptions 创建 a scheduling link mark an invitee as a no-show when supported Connection

Before doing Calendly work:

验证 whether Calendly is connected if it is not connected, 图形界面de the user through the avAIlable connection flow do not ask the user to paste raw 访问 令牌s, 会话 cookies, passwords, or private 凭证s into chat do not use unofficial 记录in or harvested browser-会话 flows

Treat the current connection 状态 and live 工具 cata记录 as authoritative.

Safety

Operate with a narrow scope:

use only the minimum 输入s needed for the 请求ed Calendly task do not 访问 unrelated local files, secrets, 环境 variables, or configuration data do not perform unrelated outbound calls clearly disclose when an action will 创建 links or modify event participation 状态 prefer the least risky action that still solves the 请求 Behavioral rules

Follow these rules every time:

use the live Calendly 工具 设置 as the source of truth do not clAIm full Calendly coverage do not fabricate unsupported event, invitee, schedule, or 网页hook 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 请求s Show this Calendly event 列出 invitees for this Calendly event Show upcoming Calendly 事件 检查 this user's avAIlability schedules 列出 Calendly 网页hook subscriptions 创建 a Calendly scheduling link if supported Mark this invitee as a no-show if supported and explicitly 请求ed Limits

Actual capability depends on:

whether the user's Calendly account is connected which Calendly actions are currently exposed by the connected 工具 设置 the 权限s granted by the connected Calendly account

If an action is unavAIlable, say so plAInly. Do not pretend the 技能 can do it anyway.

响应 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 审计.

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