[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M715KGSV1JS1PB10GW4986Z5":3,"skill-same:01M715KGSV1JS1PB10GW4986Z5":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M715KGSV1JS1PB10GW4986Z5","calendly-automation",null,"Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fcalendly-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"calendly","automation","calendly automation","search tools","via","first","administration","scheduling","event","for","availability","automate","Tools","composio","2026","organization","unknown","MCP","search","community","2026-11-10 10:12:30",false,"---\nname: calendly-automation\ndescription: \"Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Calendly Automation via Rube MCP\n\nAutomate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Calendly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n- Many operations require the user's Calendly URI, obtained via `CALENDLY_GET_CURRENT_USER`\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`\n3. If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and View Scheduled Events\n\n**When to use**: User wants to see their upcoming, past, or filtered Calendly events\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get authenticated user URI and organization URI [Prerequisite]\n2. `CALENDLY_LIST_EVENTS` - List events scoped by user, organization, or group [Required]\n3. `CALENDLY_GET_EVENT` - Get detailed info for a specific event by UUID [Optional]\n\n**Key parameters**:\n- `user`: Full Calendly API URI (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`) - NOT `\"me\"`\n- `organization`: Full organization URI for org-scoped queries\n- `status`: `\"active\"` or `\"canceled\"`\n- `min_start_time` \u002F `max_start_time`: UTC timestamps (e.g., `2024-01-01T00:00:00.000000Z`)\n- `invitee_email`: Filter events by invitee email (filter only, not a scope)\n- `sort`: `\"start_time:asc\"` or `\"start_time:desc\"`\n- `count`: Results per page (default 20)\n- `page_token`: Pagination token from previous response\n\n**Pitfalls**:\n- Exactly ONE of `user`, `organization`, or `group` must be provided - omitting or combining scopes fails\n- The `user` parameter requires the full API URI, not `\"me\"` - use `CALENDLY_GET_CURRENT_USER` first\n- `invitee_email` is a filter, not a scope; you still need one of user\u002Forganization\u002Fgroup\n- Pagination uses `count` + `page_token`; loop until `page_token` is absent for complete results\n- Admin rights may be needed for organization or group scope queries\n\n### 2. Manage Event Invitees\n\n**When to use**: User wants to see who is booked for events or get invitee details\n\n**Tool sequence**:\n1. `CALENDLY_LIST_EVENTS` - Find the target event(s) [Prerequisite]\n2. `CALENDLY_LIST_EVENT_INVITEES` - List all invitees for a specific event [Required]\n3. `CALENDLY_GET_EVENT_INVITEE` - Get detailed info for a single invitee [Optional]\n\n**Key parameters**:\n- `uuid`: Event UUID (for `LIST_EVENT_INVITEES`)\n- `event_uuid` + `invitee_uuid`: Both required for `GET_EVENT_INVITEE`\n- `email`: Filter invitees by email address\n- `status`: `\"active\"` or `\"canceled\"`\n- `sort`: `\"created_at:asc\"` or `\"created_at:desc\"`\n- `count`: Results per page (default 20)\n\n**Pitfalls**:\n- The `uuid` parameter for `CALENDLY_LIST_EVENT_INVITEES` is the event UUID, not the invitee UUID\n- Paginate using `page_token` until absent for complete invitee lists\n- Canceled invitees are excluded by default; use `status: \"canceled\"` to see them\n\n### 3. Create Scheduling Links and Check Availability\n\n**When to use**: User wants to generate a booking link or check available time slots\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get user URI [Prerequisite]\n2. `CALENDLY_LIST_USER_S_EVENT_TYPES` - List available event types [Required]\n3. `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` - Check available slots for an event type [Optional]\n4. `CALENDLY_CREATE_SCHEDULING_LINK` - Generate a single-use scheduling link [Required]\n5. `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` - View user's availability schedules [Optional]\n\n**Key parameters**:\n- `owner`: Event type URI (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fevent_types\u002F{uuid}`)\n- `owner_type`: `\"EventType\"` (default)\n- `max_event_count`: Must be exactly `1` for single-use links\n- `start_time` \u002F `end_time`: UTC timestamps for availability queries (max 7-day range)\n- `active`: Boolean to filter active\u002Finactive event types\n- `user`: User URI for event type listing\n\n**Pitfalls**:\n- `CALENDLY_CREATE_SCHEDULING_LINK` can return 403 if token lacks rights or owner URI is invalid\n- `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` requires UTC timestamps and max 7-day range; split longer searches\n- Available times results are NOT paginated - all results returned in one response\n- Event type URIs must be full API URIs (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fevent_types\u002F...`)\n\n### 4. Cancel Events\n\n**When to use**: User wants to cancel a scheduled Calendly event\n\n**Tool sequence**:\n1. `CALENDLY_LIST_EVENTS` - Find the event to cancel [Prerequisite]\n2. `CALENDLY_GET_EVENT` - Confirm event details before cancellation [Prerequisite]\n3. `CALENDLY_LIST_EVENT_INVITEES` - Check who will be affected [Optional]\n4. `CALENDLY_CANCEL_EVENT` - Cancel the event [Required]\n\n**Key parameters**:\n- `uuid`: Event UUID to cancel\n- `reason`: Optional cancellation reason (may be included in notification to invitees)\n\n**Pitfalls**:\n- Cancellation is IRREVERSIBLE - always confirm with the user before calling\n- Cancellation may trigger notifications to invitees\n- Only active events can be canceled; already-canceled events return errors\n- Get explicit user confirmation before executing `CALENDLY_CANCEL_EVENT`\n\n### 5. Manage Organization and Invitations\n\n**When to use**: User wants to invite members, manage organization, or handle org invitations\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get user and organization context [Prerequisite]\n2. `CALENDLY_GET_ORGANIZATION` - Get organization details [Optional]\n3. `CALENDLY_LIST_ORGANIZATION_INVITATIONS` - Check existing invitations [Optional]\n4. `CALENDLY_CREATE_ORGANIZATION_INVITATION` - Send an org invitation [Required]\n5. `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` - Revoke a pending invitation [Optional]\n6. `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` - Remove a member [Optional]\n\n**Key parameters**:\n- `uuid`: Organization UUID\n- `email`: Email address of user to invite\n- `status`: Filter invitations by `\"pending\"`, `\"accepted\"`, or `\"declined\"`\n\n**Pitfalls**:\n- Only org owners\u002Fadmins can manage invitations and removals; others get authorization errors\n- Duplicate active invitations for the same email are rejected - check existing invitations first\n- Organization owners cannot be removed via `CALENDLY_REMOVE_USER_FROM_ORGANIZATION`\n- Invitation statuses include pending, accepted, declined, and revoked - handle each appropriately\n\n## Common Patterns\n\n### ID Resolution\nCalendly uses full API URIs as identifiers, not simple IDs:\n- **Current user URI**: `CALENDLY_GET_CURRENT_USER` returns `resource.uri` (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`)\n- **Organization URI**: Found in current user response at `resource.current_organization`\n- **Event UUID**: Extract from event URI or list responses\n- **Event type URI**: From `CALENDLY_LIST_USER_S_EVENT_TYPES` response\n\nImportant: Never use `\"me\"` as a user parameter in list\u002Ffilter endpoints. Always resolve to the full URI first.\n\n### Pagination\nMost Calendly list endpoints use token-based pagination:\n- Set `count` for page size (default 20)\n- Follow `page_token` from `pagination.next_page_token` until absent\n- Sort with `field:direction` format (e.g., `start_time:asc`, `created_at:desc`)\n\n### Time Handling\n- All timestamps must be in UTC format: `yyyy-MM-ddTHH:mm:ss.ffffffZ`\n- Use `min_start_time` \u002F `max_start_time` for date range filtering on events\n- Available times queries have a maximum 7-day range; split longer searches into multiple calls\n\n## Known Pitfalls\n\n### URI Formats\n- All entity references use full Calendly API URIs (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`)\n- Never pass bare UUIDs where URIs are expected, and never pass `\"me\"` to list endpoints\n- Extract UUIDs from URIs when tools expect UUID parameters (e.g., `CALENDLY_GET_EVENT`)\n\n### Scope Requirements\n- `CALENDLY_LIST_EVENTS` requires exactly one scope (user, organization, or group) - no more, no less\n- Organization\u002Fgroup scoped queries may require admin privileges\n- Token scope determines which operations are available; 403 errors indicate insufficient permissions\n\n### Data Relationships\n- Events have invitees (attendees who booked)\n- Event types define scheduling pages (duration, availability rules)\n- Organizations contain users and groups\n- Scheduling links are tied to event types, not directly to events\n\n### Rate Limits\n- Calendly API has rate limits; avoid tight loops over large datasets\n- Paginate responsibly and add delays for batch operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get current user | `CALENDLY_GET_CURRENT_USER` | (none) |\n| Get user by UUID | `CALENDLY_GET_USER` | `uuid` |\n| List events | `CALENDLY_LIST_EVENTS` | `user`, `status`, `min_start_time` |\n| Get event details | `CALENDLY_GET_EVENT` | `uuid` |\n| Cancel event | `CALENDLY_CANCEL_EVENT` | `uuid`, `reason` |\n| List invitees | `CALENDLY_LIST_EVENT_INVITEES` | `uuid`, `status`, `email` |\n| Get invitee | `CALENDLY_GET_EVENT_INVITEE` | `event_uuid`, `invitee_uuid` |\n| List event types | `CALENDLY_LIST_USER_S_EVENT_TYPES` | `user`, `active` |\n| Get event type | `CALENDLY_GET_EVENT_TYPE` | `uuid` |\n| Check availability | `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` | event type URI, `start_time`, `end_time` |\n| Create scheduling link | `CALENDLY_CREATE_SCHEDULING_LINK` | `owner`, `max_event_count` |\n| List availability schedules | `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` | user URI |\n| Get organization | `CALENDLY_GET_ORGANIZATION` | `uuid` |\n| Invite to org | `CALENDLY_CREATE_ORGANIZATION_INVITATION` | `uuid`, `email` |\n| List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` |\n| Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID |\n| Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Calendly Automation via Rube MCP\n\nAutomate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Calendly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n- Many operations require the user's Calendly URI, obtained via `CALENDLY_GET_CURRENT_USER`\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`\n3. If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and View Scheduled Events\n\n**When to use**: User wants to see their upcoming, past, or filtered Calendly events\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get authenticated user URI and organization URI [Prerequisite]\n2. `CALENDLY_LIST_EVENTS` - List events scoped by user, organization, or group [Required]\n3. `CALENDLY_GET_EVENT` - Get detailed info for a specific event by UUID [Optional]\n\n**Key parameters**:\n- `user`: Full Calendly API URI (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`) - NOT `\"me\"`\n- `organization`: Full organization URI for org-scoped queries\n- `status`: `\"active\"` or `\"canceled\"`\n- `min_start_time` \u002F `max_start_time`: UTC timestamps (e.g., `2024-01-01T00:00:00.000000Z`)\n- `invitee_email`: Filter events by invitee email (filter only, not a scope)\n- `sort`: `\"start_time:asc\"` or `\"start_time:desc\"`\n- `count`: Results per page (default 20)\n- `page_token`: Pagination token from previous response\n\n**Pitfalls**:\n- Exactly ONE of `user`, `organization`, or `group` must be provided - omitting or combining scopes fails\n- The `user` parameter requires the full API URI, not `\"me\"` - use `CALENDLY_GET_CURRENT_USER` first\n- `invitee_email` is a filter, not a scope; you still need one of user\u002Forganization\u002Fgroup\n- Pagination uses `count` + `page_token`; loop until `page_token` is absent for complete results\n- Admin rights may be needed for organization or group scope queries\n\n### 2. Manage Event Invitees\n\n**When to use**: User wants to see who is booked for events or get invitee details\n\n**Tool sequence**:\n1. `CALENDLY_LIST_EVENTS` - Find the target event(s) [Prerequisite]\n2. `CALENDLY_LIST_EVENT_INVITEES` - List all invitees for a specific event [Required]\n3. `CALENDLY_GET_EVENT_INVITEE` - Get detailed info for a single invitee [Optional]\n\n**Key parameters**:\n- `uuid`: Event UUID (for `LIST_EVENT_INVITEES`)\n- `event_uuid` + `invitee_uuid`: Both required for `GET_EVENT_INVITEE`\n- `email`: Filter invitees by email address\n- `status`: `\"active\"` or `\"canceled\"`\n- `sort`: `\"created_at:asc\"` or `\"created_at:desc\"`\n- `count`: Results per page (default 20)\n\n**Pitfalls**:\n- The `uuid` parameter for `CALENDLY_LIST_EVENT_INVITEES` is the event UUID, not the invitee UUID\n- Paginate using `page_token` until absent for complete invitee lists\n- Canceled invitees are excluded by default; use `status: \"canceled\"` to see them\n\n### 3. Create Scheduling Links and Check Availability\n\n**When to use**: User wants to generate a booking link or check available time slots\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get user URI [Prerequisite]\n2. `CALENDLY_LIST_USER_S_EVENT_TYPES` - List available event types [Required]\n3. `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` - Check available slots for an event type [Optional]\n4. `CALENDLY_CREATE_SCHEDULING_LINK` - Generate a single-use scheduling link [Required]\n5. `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` - View user's availability schedules [Optional]\n\n**Key parameters**:\n- `owner`: Event type URI (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fevent_types\u002F{uuid}`)\n- `owner_type`: `\"EventType\"` (default)\n- `max_event_count`: Must be exactly `1` for single-use links\n- `start_time` \u002F `end_time`: UTC timestamps for availability queries (max 7-day range)\n- `active`: Boolean to filter active\u002Finactive event types\n- `user`: User URI for event type listing\n\n**Pitfalls**:\n- `CALENDLY_CREATE_SCHEDULING_LINK` can return 403 if token lacks rights or owner URI is invalid\n- `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` requires UTC timestamps and max 7-day range; split longer searches\n- Available times results are NOT paginated - all results returned in one response\n- Event type URIs must be full API URIs (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fevent_types\u002F...`)\n\n### 4. Cancel Events\n\n**When to use**: User wants to cancel a scheduled Calendly event\n\n**Tool sequence**:\n1. `CALENDLY_LIST_EVENTS` - Find the event to cancel [Prerequisite]\n2. `CALENDLY_GET_EVENT` - Confirm event details before cancellation [Prerequisite]\n3. `CALENDLY_LIST_EVENT_INVITEES` - Check who will be affected [Optional]\n4. `CALENDLY_CANCEL_EVENT` - Cancel the event [Required]\n\n**Key parameters**:\n- `uuid`: Event UUID to cancel\n- `reason`: Optional cancellation reason (may be included in notification to invitees)\n\n**Pitfalls**:\n- Cancellation is IRREVERSIBLE - always confirm with the user before calling\n- Cancellation may trigger notifications to invitees\n- Only active events can be canceled; already-canceled events return errors\n- Get explicit user confirmation before executing `CALENDLY_CANCEL_EVENT`\n\n### 5. Manage Organization and Invitations\n\n**When to use**: User wants to invite members, manage organization, or handle org invitations\n\n**Tool sequence**:\n1. `CALENDLY_GET_CURRENT_USER` - Get user and organization context [Prerequisite]\n2. `CALENDLY_GET_ORGANIZATION` - Get organization details [Optional]\n3. `CALENDLY_LIST_ORGANIZATION_INVITATIONS` - Check existing invitations [Optional]\n4. `CALENDLY_CREATE_ORGANIZATION_INVITATION` - Send an org invitation [Required]\n5. `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` - Revoke a pending invitation [Optional]\n6. `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` - Remove a member [Optional]\n\n**Key parameters**:\n- `uuid`: Organization UUID\n- `email`: Email address of user to invite\n- `status`: Filter invitations by `\"pending\"`, `\"accepted\"`, or `\"declined\"`\n\n**Pitfalls**:\n- Only org owners\u002Fadmins can manage invitations and removals; others get authorization errors\n- Duplicate active invitations for the same email are rejected - check existing invitations first\n- Organization owners cannot be removed via `CALENDLY_REMOVE_USER_FROM_ORGANIZATION`\n- Invitation statuses include pending, accepted, declined, and revoked - handle each appropriately\n\n## Common Patterns\n\n### ID Resolution\nCalendly uses full API URIs as identifiers, not simple IDs:\n- **Current user URI**: `CALENDLY_GET_CURRENT_USER` returns `resource.uri` (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`)\n- **Organization URI**: Found in current user response at `resource.current_organization`\n- **Event UUID**: Extract from event URI or list responses\n- **Event type URI**: From `CALENDLY_LIST_USER_S_EVENT_TYPES` response\n\nImportant: Never use `\"me\"` as a user parameter in list\u002Ffilter endpoints. Always resolve to the full URI first.\n\n### Pagination\nMost Calendly list endpoints use token-based pagination:\n- Set `count` for page size (default 20)\n- Follow `page_token` from `pagination.next_page_token` until absent\n- Sort with `field:direction` format (e.g., `start_time:asc`, `created_at:desc`)\n\n### Time Handling\n- All timestamps must be in UTC format: `yyyy-MM-ddTHH:mm:ss.ffffffZ`\n- Use `min_start_time` \u002F `max_start_time` for date range filtering on events\n- Available times queries have a maximum 7-day range; split longer searches into multiple calls\n\n## Known Pitfalls\n\n### URI Formats\n- All entity references use full Calendly API URIs (e.g., `https:\u002F\u002Fapi.calendly.com\u002Fusers\u002F{uuid}`)\n- Never pass bare UUIDs where URIs are expected, and never pass `\"me\"` to list endpoints\n- Extract UUIDs from URIs when tools expect UUID parameters (e.g., `CALENDLY_GET_EVENT`)\n\n### Scope Requirements\n- `CALENDLY_LIST_EVENTS` requires exactly one scope (user, organization, or group) - no more, no less\n- Organization\u002Fgroup scoped queries may require admin privileges\n- Token scope determines which operations are available; 403 errors indicate insufficient permissions\n\n### Data Relationships\n- Events have invitees (attendees who booked)\n- Event types define scheduling pages (duration, availability rules)\n- Organizations contain users and groups\n- Scheduling links are tied to event types, not directly to events\n\n### Rate Limits\n- Calendly API has rate limits; avoid tight loops over large datasets\n- Paginate responsibly and add delays for batch operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get current user | `CALENDLY_GET_CURRENT_USER` | (none) |\n| Get user by UUID | `CALENDLY_GET_USER` | `uuid` |\n| List events | `CALENDLY_LIST_EVENTS` | `user`, `status`, `min_start_time` |\n| Get event details | `CALENDLY_GET_EVENT` | `uuid` |\n| Cancel event | `CALENDLY_CANCEL_EVENT` | `uuid`, `reason` |\n| List invitees | `CALENDLY_LIST_EVENT_INVITEES` | `uuid`, `status`, `email` |\n| Get invitee | `CALENDLY_GET_EVENT_INVITEE` | `event_uuid`, `invitee_uuid` |\n| List event types | `CALENDLY_LIST_USER_S_EVENT_TYPES` | `user`, `active` |\n| Get event type | `CALENDLY_GET_EVENT_TYPE` | `uuid` |\n| Check availability | `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` | event type URI, `start_time`, `end_time` |\n| Create scheduling link | `CALENDLY_CREATE_SCHEDULING_LINK` | `owner`, `max_event_count` |\n| List availability schedules | `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` | user URI |\n| Get organization | `CALENDLY_GET_ORGANIZATION` | `uuid` |\n| Invite to org | `CALENDLY_CREATE_ORGANIZATION_INVITATION` | `uuid`, `email` |\n| List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` |\n| Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID |\n| Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":40,"source":43,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Fcalendly-automation","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill calendly-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill calendly-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill calendly-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fcalendly-automation\u002FSKILL.md",true,[],[71,94,120,130,143,160],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":44},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[83,84,42,85,86,87,88,89,90,91,92,93],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":44},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[101,102,103,104,105,106,42,107,108,109,110,111,112,113,114,115,116,117,118,119],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":44},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[127,128,101,112,113,114,115,105,42,117,129,118,119,111,109,108,107,116,106,104],"trend radar","radar","pulse",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[137,138,139,140,141,142],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":44},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[145,90,153,154,155,93,112,156,157,158,103,159,116],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":44},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[162,167,168,169,116,170,157,171,172,173,174,175],"status","play","go","latest","github","discover","control","cmd","volume"]