[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXMPN0ZXGFT5B8MECY24VZ":3,"skill-same:01M7EXMPN0ZXGFT5B8MECY24VZ":49},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EXMPN0ZXGFT5B8MECY24VZ","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcalendly-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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: critical\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\n## Example\n\n**User request:**\n\n> Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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\n## Example\n\n**User request:**\n\n> Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fcalendly-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill calendly-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill calendly-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill calendly-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcalendly-automation\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":57},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":57},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":57},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":57},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]