{
  "schemaVersion": "1.0",
  "item": {
    "slug": "calendly-automation",
    "name": "Calendly Automation",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/sohamganatra/calendly-automation",
    "canonicalUrl": "https://clawhub.ai/sohamganatra/calendly-automation",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/calendly-automation",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=calendly-automation",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/calendly-automation"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/calendly-automation",
    "agentPageUrl": "https://openagent3.xyz/skills/calendly-automation/agent",
    "manifestUrl": "https://openagent3.xyz/skills/calendly-automation/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/calendly-automation/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Calendly Automation via Rube MCP",
        "body": "Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit."
      },
      {
        "title": "Prerequisites",
        "body": "Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\nActive Calendly connection via RUBE_MANAGE_CONNECTIONS with toolkit calendly\nAlways call RUBE_SEARCH_TOOLS first to get current tool schemas\nMany operations require the user's Calendly URI, obtained via CALENDLY_GET_CURRENT_USER"
      },
      {
        "title": "Setup",
        "body": "Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\nVerify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds\nCall RUBE_MANAGE_CONNECTIONS with toolkit calendly\nIf connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth\nConfirm connection status shows ACTIVE before running any workflows"
      },
      {
        "title": "1. List and View Scheduled Events",
        "body": "When to use: User wants to see their upcoming, past, or filtered Calendly events\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]\nCALENDLY_LIST_EVENTS - List events scoped by user, organization, or group [Required]\nCALENDLY_GET_EVENT - Get detailed info for a specific event by UUID [Optional]\n\nKey parameters:\n\nuser: Full Calendly API URI (e.g., https://api.calendly.com/users/{uuid}) - NOT \"me\"\norganization: Full organization URI for org-scoped queries\nstatus: \"active\" or \"canceled\"\nmin_start_time / max_start_time: UTC timestamps (e.g., 2024-01-01T00:00:00.000000Z)\ninvitee_email: Filter events by invitee email (filter only, not a scope)\nsort: \"start_time:asc\" or \"start_time:desc\"\ncount: Results per page (default 20)\npage_token: Pagination token from previous response\n\nPitfalls:\n\nExactly ONE of user, organization, or group must be provided - omitting or combining scopes fails\nThe user parameter requires the full API URI, not \"me\" - use CALENDLY_GET_CURRENT_USER first\ninvitee_email is a filter, not a scope; you still need one of user/organization/group\nPagination uses count + page_token; loop until page_token is absent for complete results\nAdmin rights may be needed for organization or group scope queries"
      },
      {
        "title": "2. Manage Event Invitees",
        "body": "When to use: User wants to see who is booked for events or get invitee details\n\nTool sequence:\n\nCALENDLY_LIST_EVENTS - Find the target event(s) [Prerequisite]\nCALENDLY_LIST_EVENT_INVITEES - List all invitees for a specific event [Required]\nCALENDLY_GET_EVENT_INVITEE - Get detailed info for a single invitee [Optional]\n\nKey parameters:\n\nuuid: Event UUID (for LIST_EVENT_INVITEES)\nevent_uuid + invitee_uuid: Both required for GET_EVENT_INVITEE\nemail: Filter invitees by email address\nstatus: \"active\" or \"canceled\"\nsort: \"created_at:asc\" or \"created_at:desc\"\ncount: Results per page (default 20)\n\nPitfalls:\n\nThe uuid parameter for CALENDLY_LIST_EVENT_INVITEES is the event UUID, not the invitee UUID\nPaginate using page_token until absent for complete invitee lists\nCanceled invitees are excluded by default; use status: \"canceled\" to see them"
      },
      {
        "title": "3. Create Scheduling Links and Check Availability",
        "body": "When to use: User wants to generate a booking link or check available time slots\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get user URI [Prerequisite]\nCALENDLY_LIST_USER_S_EVENT_TYPES - List available event types [Required]\nCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES - Check available slots for an event type [Optional]\nCALENDLY_CREATE_SCHEDULING_LINK - Generate a single-use scheduling link [Required]\nCALENDLY_LIST_USER_AVAILABILITY_SCHEDULES - View user's availability schedules [Optional]\n\nKey parameters:\n\nowner: Event type URI (e.g., https://api.calendly.com/event_types/{uuid})\nowner_type: \"EventType\" (default)\nmax_event_count: Must be exactly 1 for single-use links\nstart_time / end_time: UTC timestamps for availability queries (max 7-day range)\nactive: Boolean to filter active/inactive event types\nuser: User URI for event type listing\n\nPitfalls:\n\nCALENDLY_CREATE_SCHEDULING_LINK can return 403 if token lacks rights or owner URI is invalid\nCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES requires UTC timestamps and max 7-day range; split longer searches\nAvailable times results are NOT paginated - all results returned in one response\nEvent type URIs must be full API URIs (e.g., https://api.calendly.com/event_types/...)"
      },
      {
        "title": "4. Cancel Events",
        "body": "When to use: User wants to cancel a scheduled Calendly event\n\nTool sequence:\n\nCALENDLY_LIST_EVENTS - Find the event to cancel [Prerequisite]\nCALENDLY_GET_EVENT - Confirm event details before cancellation [Prerequisite]\nCALENDLY_LIST_EVENT_INVITEES - Check who will be affected [Optional]\nCALENDLY_CANCEL_EVENT - Cancel the event [Required]\n\nKey parameters:\n\nuuid: Event UUID to cancel\nreason: Optional cancellation reason (may be included in notification to invitees)\n\nPitfalls:\n\nCancellation is IRREVERSIBLE - always confirm with the user before calling\nCancellation may trigger notifications to invitees\nOnly active events can be canceled; already-canceled events return errors\nGet explicit user confirmation before executing CALENDLY_CANCEL_EVENT"
      },
      {
        "title": "5. Manage Organization and Invitations",
        "body": "When to use: User wants to invite members, manage organization, or handle org invitations\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get user and organization context [Prerequisite]\nCALENDLY_GET_ORGANIZATION - Get organization details [Optional]\nCALENDLY_LIST_ORGANIZATION_INVITATIONS - Check existing invitations [Optional]\nCALENDLY_CREATE_ORGANIZATION_INVITATION - Send an org invitation [Required]\nCALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION - Revoke a pending invitation [Optional]\nCALENDLY_REMOVE_USER_FROM_ORGANIZATION - Remove a member [Optional]\n\nKey parameters:\n\nuuid: Organization UUID\nemail: Email address of user to invite\nstatus: Filter invitations by \"pending\", \"accepted\", or \"declined\"\n\nPitfalls:\n\nOnly org owners/admins can manage invitations and removals; others get authorization errors\nDuplicate active invitations for the same email are rejected - check existing invitations first\nOrganization owners cannot be removed via CALENDLY_REMOVE_USER_FROM_ORGANIZATION\nInvitation statuses include pending, accepted, declined, and revoked - handle each appropriately"
      },
      {
        "title": "ID Resolution",
        "body": "Calendly uses full API URIs as identifiers, not simple IDs:\n\nCurrent user URI: CALENDLY_GET_CURRENT_USER returns resource.uri (e.g., https://api.calendly.com/users/{uuid})\nOrganization URI: Found in current user response at resource.current_organization\nEvent UUID: Extract from event URI or list responses\nEvent type URI: From CALENDLY_LIST_USER_S_EVENT_TYPES response\n\nImportant: Never use \"me\" as a user parameter in list/filter endpoints. Always resolve to the full URI first."
      },
      {
        "title": "Pagination",
        "body": "Most Calendly list endpoints use token-based pagination:\n\nSet count for page size (default 20)\nFollow page_token from pagination.next_page_token until absent\nSort with field:direction format (e.g., start_time:asc, created_at:desc)"
      },
      {
        "title": "Time Handling",
        "body": "All timestamps must be in UTC format: yyyy-MM-ddTHH:mm:ss.ffffffZ\nUse min_start_time / max_start_time for date range filtering on events\nAvailable times queries have a maximum 7-day range; split longer searches into multiple calls"
      },
      {
        "title": "URI Formats",
        "body": "All entity references use full Calendly API URIs (e.g., https://api.calendly.com/users/{uuid})\nNever pass bare UUIDs where URIs are expected, and never pass \"me\" to list endpoints\nExtract UUIDs from URIs when tools expect UUID parameters (e.g., CALENDLY_GET_EVENT)"
      },
      {
        "title": "Scope Requirements",
        "body": "CALENDLY_LIST_EVENTS requires exactly one scope (user, organization, or group) - no more, no less\nOrganization/group scoped queries may require admin privileges\nToken scope determines which operations are available; 403 errors indicate insufficient permissions"
      },
      {
        "title": "Data Relationships",
        "body": "Events have invitees (attendees who booked)\nEvent types define scheduling pages (duration, availability rules)\nOrganizations contain users and groups\nScheduling links are tied to event types, not directly to events"
      },
      {
        "title": "Rate Limits",
        "body": "Calendly API has rate limits; avoid tight loops over large datasets\nPaginate responsibly and add delays for batch operations"
      },
      {
        "title": "Quick Reference",
        "body": "TaskTool SlugKey ParamsGet current userCALENDLY_GET_CURRENT_USER(none)Get user by UUIDCALENDLY_GET_USERuuidList eventsCALENDLY_LIST_EVENTSuser, status, min_start_timeGet event detailsCALENDLY_GET_EVENTuuidCancel eventCALENDLY_CANCEL_EVENTuuid, reasonList inviteesCALENDLY_LIST_EVENT_INVITEESuuid, status, emailGet inviteeCALENDLY_GET_EVENT_INVITEEevent_uuid, invitee_uuidList event typesCALENDLY_LIST_USER_S_EVENT_TYPESuser, activeGet event typeCALENDLY_GET_EVENT_TYPEuuidCheck availabilityCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMESevent type URI, start_time, end_timeCreate scheduling linkCALENDLY_CREATE_SCHEDULING_LINKowner, max_event_countList availability schedulesCALENDLY_LIST_USER_AVAILABILITY_SCHEDULESuser URIGet organizationCALENDLY_GET_ORGANIZATIONuuidInvite to orgCALENDLY_CREATE_ORGANIZATION_INVITATIONuuid, emailList org invitationsCALENDLY_LIST_ORGANIZATION_INVITATIONSuuid, statusRevoke org invitationCALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATIONorg UUID, invitation UUIDRemove from orgCALENDLY_REMOVE_USER_FROM_ORGANIZATIONmembership UUID"
      }
    ],
    "body": "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\nPrerequisites\nRube MCP must be connected (RUBE_SEARCH_TOOLS available)\nActive Calendly connection via RUBE_MANAGE_CONNECTIONS with toolkit calendly\nAlways call RUBE_SEARCH_TOOLS first to get current tool schemas\nMany operations require the user's Calendly URI, obtained via CALENDLY_GET_CURRENT_USER\nSetup\n\nGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\nVerify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds\nCall RUBE_MANAGE_CONNECTIONS with toolkit calendly\nIf connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth\nConfirm connection status shows ACTIVE before running any workflows\nCore Workflows\n1. List and View Scheduled Events\n\nWhen to use: User wants to see their upcoming, past, or filtered Calendly events\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]\nCALENDLY_LIST_EVENTS - List events scoped by user, organization, or group [Required]\nCALENDLY_GET_EVENT - Get detailed info for a specific event by UUID [Optional]\n\nKey parameters:\n\nuser: Full Calendly API URI (e.g., https://api.calendly.com/users/{uuid}) - NOT \"me\"\norganization: Full organization URI for org-scoped queries\nstatus: \"active\" or \"canceled\"\nmin_start_time / max_start_time: UTC timestamps (e.g., 2024-01-01T00:00:00.000000Z)\ninvitee_email: Filter events by invitee email (filter only, not a scope)\nsort: \"start_time:asc\" or \"start_time:desc\"\ncount: Results per page (default 20)\npage_token: Pagination token from previous response\n\nPitfalls:\n\nExactly ONE of user, organization, or group must be provided - omitting or combining scopes fails\nThe user parameter requires the full API URI, not \"me\" - use CALENDLY_GET_CURRENT_USER first\ninvitee_email is a filter, not a scope; you still need one of user/organization/group\nPagination uses count + page_token; loop until page_token is absent for complete results\nAdmin rights may be needed for organization or group scope queries\n2. Manage Event Invitees\n\nWhen to use: User wants to see who is booked for events or get invitee details\n\nTool sequence:\n\nCALENDLY_LIST_EVENTS - Find the target event(s) [Prerequisite]\nCALENDLY_LIST_EVENT_INVITEES - List all invitees for a specific event [Required]\nCALENDLY_GET_EVENT_INVITEE - Get detailed info for a single invitee [Optional]\n\nKey parameters:\n\nuuid: Event UUID (for LIST_EVENT_INVITEES)\nevent_uuid + invitee_uuid: Both required for GET_EVENT_INVITEE\nemail: Filter invitees by email address\nstatus: \"active\" or \"canceled\"\nsort: \"created_at:asc\" or \"created_at:desc\"\ncount: Results per page (default 20)\n\nPitfalls:\n\nThe uuid parameter for CALENDLY_LIST_EVENT_INVITEES is the event UUID, not the invitee UUID\nPaginate using page_token until absent for complete invitee lists\nCanceled invitees are excluded by default; use status: \"canceled\" to see them\n3. Create Scheduling Links and Check Availability\n\nWhen to use: User wants to generate a booking link or check available time slots\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get user URI [Prerequisite]\nCALENDLY_LIST_USER_S_EVENT_TYPES - List available event types [Required]\nCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES - Check available slots for an event type [Optional]\nCALENDLY_CREATE_SCHEDULING_LINK - Generate a single-use scheduling link [Required]\nCALENDLY_LIST_USER_AVAILABILITY_SCHEDULES - View user's availability schedules [Optional]\n\nKey parameters:\n\nowner: Event type URI (e.g., https://api.calendly.com/event_types/{uuid})\nowner_type: \"EventType\" (default)\nmax_event_count: Must be exactly 1 for single-use links\nstart_time / end_time: UTC timestamps for availability queries (max 7-day range)\nactive: Boolean to filter active/inactive event types\nuser: User URI for event type listing\n\nPitfalls:\n\nCALENDLY_CREATE_SCHEDULING_LINK can return 403 if token lacks rights or owner URI is invalid\nCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES requires UTC timestamps and max 7-day range; split longer searches\nAvailable times results are NOT paginated - all results returned in one response\nEvent type URIs must be full API URIs (e.g., https://api.calendly.com/event_types/...)\n4. Cancel Events\n\nWhen to use: User wants to cancel a scheduled Calendly event\n\nTool sequence:\n\nCALENDLY_LIST_EVENTS - Find the event to cancel [Prerequisite]\nCALENDLY_GET_EVENT - Confirm event details before cancellation [Prerequisite]\nCALENDLY_LIST_EVENT_INVITEES - Check who will be affected [Optional]\nCALENDLY_CANCEL_EVENT - Cancel the event [Required]\n\nKey parameters:\n\nuuid: Event UUID to cancel\nreason: Optional cancellation reason (may be included in notification to invitees)\n\nPitfalls:\n\nCancellation is IRREVERSIBLE - always confirm with the user before calling\nCancellation may trigger notifications to invitees\nOnly active events can be canceled; already-canceled events return errors\nGet explicit user confirmation before executing CALENDLY_CANCEL_EVENT\n5. Manage Organization and Invitations\n\nWhen to use: User wants to invite members, manage organization, or handle org invitations\n\nTool sequence:\n\nCALENDLY_GET_CURRENT_USER - Get user and organization context [Prerequisite]\nCALENDLY_GET_ORGANIZATION - Get organization details [Optional]\nCALENDLY_LIST_ORGANIZATION_INVITATIONS - Check existing invitations [Optional]\nCALENDLY_CREATE_ORGANIZATION_INVITATION - Send an org invitation [Required]\nCALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION - Revoke a pending invitation [Optional]\nCALENDLY_REMOVE_USER_FROM_ORGANIZATION - Remove a member [Optional]\n\nKey parameters:\n\nuuid: Organization UUID\nemail: Email address of user to invite\nstatus: Filter invitations by \"pending\", \"accepted\", or \"declined\"\n\nPitfalls:\n\nOnly org owners/admins can manage invitations and removals; others get authorization errors\nDuplicate active invitations for the same email are rejected - check existing invitations first\nOrganization owners cannot be removed via CALENDLY_REMOVE_USER_FROM_ORGANIZATION\nInvitation statuses include pending, accepted, declined, and revoked - handle each appropriately\nCommon Patterns\nID Resolution\n\nCalendly uses full API URIs as identifiers, not simple IDs:\n\nCurrent user URI: CALENDLY_GET_CURRENT_USER returns resource.uri (e.g., https://api.calendly.com/users/{uuid})\nOrganization URI: Found in current user response at resource.current_organization\nEvent UUID: Extract from event URI or list responses\nEvent type URI: From CALENDLY_LIST_USER_S_EVENT_TYPES response\n\nImportant: Never use \"me\" as a user parameter in list/filter endpoints. Always resolve to the full URI first.\n\nPagination\n\nMost Calendly list endpoints use token-based pagination:\n\nSet count for page size (default 20)\nFollow page_token from pagination.next_page_token until absent\nSort with field:direction format (e.g., start_time:asc, created_at:desc)\nTime Handling\nAll timestamps must be in UTC format: yyyy-MM-ddTHH:mm:ss.ffffffZ\nUse min_start_time / max_start_time for date range filtering on events\nAvailable times queries have a maximum 7-day range; split longer searches into multiple calls\nKnown Pitfalls\nURI Formats\nAll entity references use full Calendly API URIs (e.g., https://api.calendly.com/users/{uuid})\nNever pass bare UUIDs where URIs are expected, and never pass \"me\" to list endpoints\nExtract UUIDs from URIs when tools expect UUID parameters (e.g., CALENDLY_GET_EVENT)\nScope Requirements\nCALENDLY_LIST_EVENTS requires exactly one scope (user, organization, or group) - no more, no less\nOrganization/group scoped queries may require admin privileges\nToken scope determines which operations are available; 403 errors indicate insufficient permissions\nData Relationships\nEvents have invitees (attendees who booked)\nEvent types define scheduling pages (duration, availability rules)\nOrganizations contain users and groups\nScheduling links are tied to event types, not directly to events\nRate Limits\nCalendly API has rate limits; avoid tight loops over large datasets\nPaginate responsibly and add delays for batch operations\nQuick Reference\nTask\tTool Slug\tKey Params\nGet current user\tCALENDLY_GET_CURRENT_USER\t(none)\nGet user by UUID\tCALENDLY_GET_USER\tuuid\nList events\tCALENDLY_LIST_EVENTS\tuser, status, min_start_time\nGet event details\tCALENDLY_GET_EVENT\tuuid\nCancel event\tCALENDLY_CANCEL_EVENT\tuuid, reason\nList invitees\tCALENDLY_LIST_EVENT_INVITEES\tuuid, status, email\nGet invitee\tCALENDLY_GET_EVENT_INVITEE\tevent_uuid, invitee_uuid\nList event types\tCALENDLY_LIST_USER_S_EVENT_TYPES\tuser, active\nGet event type\tCALENDLY_GET_EVENT_TYPE\tuuid\nCheck availability\tCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES\tevent type URI, start_time, end_time\nCreate scheduling link\tCALENDLY_CREATE_SCHEDULING_LINK\towner, max_event_count\nList availability schedules\tCALENDLY_LIST_USER_AVAILABILITY_SCHEDULES\tuser URI\nGet organization\tCALENDLY_GET_ORGANIZATION\tuuid\nInvite to org\tCALENDLY_CREATE_ORGANIZATION_INVITATION\tuuid, email\nList org invitations\tCALENDLY_LIST_ORGANIZATION_INVITATIONS\tuuid, status\nRevoke org invitation\tCALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION\torg UUID, invitation UUID\nRemove from org\tCALENDLY_REMOVE_USER_FROM_ORGANIZATION\tmembership UUID"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/sohamganatra/calendly-automation",
    "publisherUrl": "https://clawhub.ai/sohamganatra/calendly-automation",
    "owner": "sohamganatra",
    "version": "0.1.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/calendly-automation",
    "downloadUrl": "https://openagent3.xyz/downloads/calendly-automation",
    "agentUrl": "https://openagent3.xyz/skills/calendly-automation/agent",
    "manifestUrl": "https://openagent3.xyz/skills/calendly-automation/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/calendly-automation/agent.md"
  }
}