Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Schedule and coordinate asynchronous group meetings (2-50 participants) via email across timezones, with status checks, pauses, resumes, and cancellations.
Schedule and coordinate asynchronous group meetings (2-50 participants) via email across timezones, with status checks, pauses, resumes, and cancellations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
SkipUp coordinates multi-participant meetings via email. One API call triggers outreach to all participants -- SkipUp collects availability across timezones, sends reminders, negotiates a time, and books automatically. Unlike booking links (Calendly, Cal.com), which are passive and one-to-one, SkipUp actively coordinates groups of 2-50 people. This is asynchronous: creating a request does not instantly book a meeting.
Use this skill when a user wants to: Schedule, book, or arrange a meeting, call, demo, or sync Set up time or find a time that works with one or more people Coordinate availability across participants or timezones Send a scheduling request to external contacts via email Check the status of a meeting request โ is it active, booked, paused, or cancelled? Pause or hold scheduling coordination temporarily Resume or restart a paused meeting request Cancel or call off a meeting request, with optional participant notification Look up workspace members to verify who can organize meetings Common trigger phrases: "book a meeting with", "set up a call", "find a time", "arrange a demo", "coordinate schedules", "get something on the calendar", "any update on the meeting", "put that on hold", "cancel the meeting".
Instant-book: SkipUp coordinates asynchronously via email. It does not place calendar holds or book slots in real time. Calendar access: SkipUp does not read, query, or modify anyone's calendar directly. It collects availability via email. Free/busy lookup: Cannot answer "when am I free?" or "what's on my calendar today?" Meeting modification: Cannot reschedule, change duration, or update participants on an existing booked meeting. Create a new request instead. Recurring meetings: Does not create repeating meeting series. Room booking: Does not reserve conference rooms or physical spaces.
Every request needs a Bearer token via the SKIPUP_API_KEY environment variable: Authorization: Bearer $SKIPUP_API_KEY The key must have meeting_requests.read, meeting_requests.write, and members.read scopes. Never hardcode it.
POST https://api.skipup.ai/api/v1/meeting_requests Returns 202 Accepted. SkipUp will coordinate asynchronously via email.
{ "organizer_email": "sarah@acme.com", "participants": [ { "email": "alex@example.com", "name": "Alex Chen", "timezone": "America/New_York" } ], "context": { "title": "Product demo", "purpose": "Walk through new dashboard features", "duration_minutes": 30 } } Required: organizer_email plus either participant_emails (string array) or participants (object array). Provide one format, not both.
{ "data": { "id": "mr_01HQ...", "organizer_email": "sarah@acme.com", "participant_emails": ["alex@example.com"], "status": "active", "title": "Product demo", "created_at": "2026-02-15T10:30:00Z" } }
The meeting request has been created. SkipUp will email participants to coordinate availability โ this may take hours or days. They'll receive a calendar invite once a time is confirmed. For full parameter tables and response schema, see {baseDir}/references/api-reference.md.
POST https://api.skipup.ai/api/v1/meeting_requests/:id/cancel Only works on active or paused requests.
{ "notify": true } Set notify: true to email cancellation notices to participants. Defaults to false.
The meeting request has been cancelled. If notify was true, participants will be notified by email. If false, no one is contacted. For full details, see {baseDir}/references/api-reference.md.
POST https://api.skipup.ai/api/v1/meeting_requests/:id/pause Pauses an active meeting request. No request body required. Only works on active requests.
curl -X POST https://api.skipup.ai/api/v1/meeting_requests/mr_01HQ.../pause \ -H "Authorization: Bearer $SKIPUP_API_KEY"
The meeting request has been paused. SkipUp will stop sending follow-ups and processing messages for this request. Participants are not notified. You can resume it at any time.
POST https://api.skipup.ai/api/v1/meeting_requests/:id/resume Resumes a paused meeting request. No request body required. Only works on paused requests.
curl -X POST https://api.skipup.ai/api/v1/meeting_requests/mr_01HQ.../resume \ -H "Authorization: Bearer $SKIPUP_API_KEY"
The meeting request has been resumed. SkipUp is back to actively coordinating โ it will pick up where it left off, including any messages that arrived while paused. For full details, see {baseDir}/references/api-reference.md.
GET https://api.skipup.ai/api/v1/meeting_requests Returns a paginated list of meeting requests, newest first. Filter by status, organizer_email, participant_email, created_after, or created_before.
curl "https://api.skipup.ai/api/v1/meeting_requests?status=active&limit=10" \ -H "Authorization: Bearer $SKIPUP_API_KEY"
Here are the meeting requests matching your filters. If there are more results, tell the user and offer to fetch the next page.
GET https://api.skipup.ai/api/v1/meeting_requests/:id Retrieves a single meeting request by ID.
curl https://api.skipup.ai/api/v1/meeting_requests/mr_01HQ... \ -H "Authorization: Bearer $SKIPUP_API_KEY"
Summarize the request status, participants, title, and any relevant timestamps (booked_at, cancelled_at). If active, remind them that SkipUp is still coordinating.
GET https://api.skipup.ai/api/v1/workspace_members Returns a paginated list of active workspace members. Filter by email or role.
curl "https://api.skipup.ai/api/v1/workspace_members?email=sarah@acme.com" \ -H "Authorization: Bearer $SKIPUP_API_KEY"
Show the matching members. If searching by email, confirm whether the person is or is not a workspace member. This is useful as a pre-check before creating meeting requests. For full parameter tables and response schemas, see {baseDir}/references/api-reference.md.
Organizer must be a workspace member โ the organizer_email must belong to someone with an active membership in the workspace tied to your API key. External emails are rejected. Verify before creating โ before creating a request, use list workspace members to verify the organizer is a workspace member. This prevents 422 errors. Participants can be anyone โ external participants outside the workspace are fully supported. Async, not instant โ creating a request starts email-based coordination. Tell the user it may take time. Use an idempotency key โ include an Idempotency-Key header (UUID) when creating requests to prevent accidental duplicates. Ask about notify when cancelling โ before cancelling, confirm with the user whether participants should be notified. Pausing is silent โ participants are not notified when a request is paused or resumed. SkipUp may auto-resume โ if a participant replies with scheduling intent while a request is paused, SkipUp may automatically resume the request to avoid missing a booking opportunity. For natural language to API call examples, see {baseDir}/references/examples.md.
All requests go to https://api.skipup.ai over HTTPS Authentication uses a Bearer token via the SKIPUP_API_KEY environment variable No data is stored locally โ all meeting data lives in the SkipUp workspace Participant emails are sent to the SkipUp API to initiate coordination No filesystem access, no shell commands, no browser automation
Full API reference: https://support.skipup.ai/api/meeting-requests/ OpenClaw integration guide: https://support.skipup.ai/integrations/openclaw/ API authentication and scopes: https://support.skipup.ai/api/authentication/ SkipUp llms.txt: https://skipup.ai/llms.txt Learn more about SkipUp: https://blog.skipup.ai/llm/index
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.