Calendly Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Calendly Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/calendly-automation from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Calendly Automation via Rube MCP Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
Call RUBEMANAGECONNECTIONS with toolkit calendly
If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
Confirm connection status shows ACTIVE before running any workflows
CALENDLYGETCURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]
CALENDLYLISTEVENTS - List events scoped by user, organization, or group [Required]
CALENDLYGETEVENT - Get detailed info for a specific event by UUID [Optional]
Imported Workflow Notes
Imported: Setup
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.
Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit calendly
If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
Confirm connection status shows ACTIVE before running any workflows
Imported: Core Workflows
1. List and View Scheduled Events
When to use: User wants to see their upcoming, past, or filtered Calendly events
Tool sequence:
CALENDLY_GET_CURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]
CALENDLY_LIST_EVENTS - List events scoped by user, organization, or group [Required]
CALENDLY_GET_EVENT - Get detailed info for a specific event by UUID [Optional]
Key parameters:
user: Full Calendly API URI (e.g., https://api.calendly.com/users/{uuid}) - NOT "me"
organization: Full organization URI for org-scoped queries
status: "active" or "canceled"
min_start_time / max_start_time: UTC timestamps (e.g., 2024-01-01T00:00:00.000000Z)
invitee_email: Filter events by invitee email (filter only, not a scope)
sort: "start_time:asc" or "start_time:desc"
count: Results per page (default 20)
page_token: Pagination token from previous response
Pitfalls:
Exactly ONE of user, organization, or group must be provided - omitting or combining scopes fails
The user parameter requires the full API URI, not "me" - use CALENDLY_GET_CURRENT_USER first
invitee_email is a filter, not a scope; you still need one of user/organization/group
Pagination uses count + page_token; loop until page_token is absent for complete results
Admin rights may be needed for organization or group scope queries
2. Manage Event Invitees
When to use: User wants to see who is booked for events or get invitee details
Tool sequence:
CALENDLY_LIST_EVENTS - Find the target event(s) [Prerequisite]
CALENDLY_LIST_EVENT_INVITEES - List all invitees for a specific event [Required]
CALENDLY_GET_EVENT_INVITEE - Get detailed info for a single invitee [Optional]
Key parameters:
uuid: Event UUID (for LIST_EVENT_INVITEES)
event_uuid + invitee_uuid: Both required for GET_EVENT_INVITEE
email: Filter invitees by email address
status: "active" or "canceled"
sort: "created_at:asc" or "created_at:desc"
count: Results per page (default 20)
Pitfalls:
The uuid parameter for CALENDLY_LIST_EVENT_INVITEES is the event UUID, not the invitee UUID
Paginate using page_token until absent for complete invitee lists
Canceled invitees are excluded by default; use status: "canceled" to see them
3. Create Scheduling Links and Check Availability
When to use: User wants to generate a booking link or check available time slots
Tool sequence:
CALENDLY_GET_CURRENT_USER - Get user URI [Prerequisite]
CALENDLY_LIST_USER_S_EVENT_TYPES - List available event types [Required]
CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES - Check available slots for an event type [Optional]
CALENDLY_CREATE_SCHEDULING_LINK - Generate a single-use scheduling link [Required]
CALENDLY_CREATE_ORGANIZATION_INVITATION - Send an org invitation [Required]
CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION - Revoke a pending invitation [Optional]
CALENDLY_REMOVE_USER_FROM_ORGANIZATION - Remove a member [Optional]
Key parameters:
uuid: Organization UUID
email: Email address of user to invite
status: Filter invitations by "pending", "accepted", or "declined"
Pitfalls:
Only org owners/admins can manage invitations and removals; others get authorization errors
Duplicate active invitations for the same email are rejected - check existing invitations first
Organization owners cannot be removed via CALENDLY_REMOVE_USER_FROM_ORGANIZATION
Invitation statuses include pending, accepted, declined, and revoked - handle each appropriately
Imported: Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Calendly connection via RUBE_MANAGE_CONNECTIONS with toolkit calendly
Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Many operations require the user's Calendly URI, obtained via CALENDLY_GET_CURRENT_USER
Examples
Example 1: Ask for the upstream workflow directly
Use @calendly-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @calendly-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @calendly-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @calendly-automation using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/calendly-automation, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Quick Reference
Task
Tool Slug
Key Params
Get current user
CALENDLY_GET_CURRENT_USER
(none)
Get user by UUID
CALENDLY_GET_USER
uuid
List events
CALENDLY_LIST_EVENTS
user, status, min_start_time
Get event details
CALENDLY_GET_EVENT
uuid
Cancel event
CALENDLY_CANCEL_EVENT
uuid, reason
List invitees
CALENDLY_LIST_EVENT_INVITEES
uuid, status, email
Get invitee
CALENDLY_GET_EVENT_INVITEE
event_uuid, invitee_uuid
List event types
CALENDLY_LIST_USER_S_EVENT_TYPES
user, active
Get event type
CALENDLY_GET_EVENT_TYPE
uuid
Check availability
CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES
event type URI, start_time, end_time
Create scheduling link
CALENDLY_CREATE_SCHEDULING_LINK
owner, max_event_count
List availability schedules
CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES
user URI
Get organization
CALENDLY_GET_ORGANIZATION
uuid
Invite to org
CALENDLY_CREATE_ORGANIZATION_INVITATION
uuid, email
List org invitations
CALENDLY_LIST_ORGANIZATION_INVITATIONS
uuid, status
Revoke org invitation
CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION
org UUID, invitation UUID
Remove from org
CALENDLY_REMOVE_USER_FROM_ORGANIZATION
membership UUID
Imported: Common Patterns
ID Resolution
Calendly uses full API URIs as identifiers, not simple IDs:
Current user URI: CALENDLY_GET_CURRENT_USER returns resource.uri (e.g., https://api.calendly.com/users/{uuid})
Organization URI: Found in current user response at resource.current_organization
Event UUID: Extract from event URI or list responses
Event type URI: From CALENDLY_LIST_USER_S_EVENT_TYPES response
Important: Never use "me" as a user parameter in list/filter endpoints. Always resolve to the full URI first.
Pagination
Most Calendly list endpoints use token-based pagination:
Set count for page size (default 20)
Follow page_token from pagination.next_page_token until absent
Sort with field:direction format (e.g., start_time:asc, created_at:desc)
Time Handling
All timestamps must be in UTC format: yyyy-MM-ddTHH:mm:ss.ffffffZ
Use min_start_time / max_start_time for date range filtering on events
Available times queries have a maximum 7-day range; split longer searches into multiple calls
Imported: Known Pitfalls
URI Formats
All entity references use full Calendly API URIs (e.g., https://api.calendly.com/users/{uuid})
Never pass bare UUIDs where URIs are expected, and never pass "me" to list endpoints
Extract UUIDs from URIs when tools expect UUID parameters (e.g., CALENDLY_GET_EVENT)
Scope Requirements
CALENDLY_LIST_EVENTS requires exactly one scope (user, organization, or group) - no more, no less
Organization/group scoped queries may require admin privileges
Token scope determines which operations are available; 403 errors indicate insufficient permissions
