[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSDB504C8Q8V53EEHRYKM3":3,"skill-same:01M6CSDB504C8Q8V53EEHRYKM3":76},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6CSDB504C8Q8V53EEHRYKM3","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.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\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],"automation","calendly automation","MCP","search","Tools","first","automate","tracking","management","scheduling","community","composio","organization","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: 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","# 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":42,"source":34,"date_added":43,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcalendly-automation",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill calendly-automation",{"tool":58,"command":59},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill calendly-automation",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill calendly-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fcalendly-automation\u002FSKILL.md",true,[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"Workflows\u002FAudit.md","REFERENCE","参考文档",1780,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FBitterPillEngineering\u002FWorkflows\u002FAudit.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"Workflows\u002FQuickCheck.md",854,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FLifeOS\u002Finstall\u002Fskills\u002FBitterPillEngineering\u002FWorkflows\u002FQuickCheck.md",[77,88,104,119,138,165],{"skillNo":78,"name":79,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":37},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[86,87],"Test Skill","test",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":37},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[95,96,97,98,99,100,101,34,102,103],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":37},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[110],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,112,113,29,28,27,26,114,115,30,42,116,117,35,34,118,32,31],"zoom automation","zoom","via","meeting","creation","webinars","recordings",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":37},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[125],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,24,128,129,130,131,132,34,27,133,35,134,42,30,28,135,102,136,26,137],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":37},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[148,149,150,151,152,103,153,154,155,156,157,158,98,159,160,161,162,34,163,164],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":37},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,175,176,177,178,179,180,34,181,182,183,184,185,186,187,188,189,190,26],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]