Skipup - AI Meeting Scheduling
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a straightforward SkipUp scheduling integration, but it can use your SkipUp API key to email participants and run scheduling workflows after the initial request.
Before installing, be comfortable giving the agent a scoped SkipUp API key and letting it contact meeting participants through SkipUp. Confirm recipients and meeting details before write actions, avoid including unnecessary sensitive context, and use cancel rather than pause if you need scheduling to stop completely.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using the skill gives the agent delegated access to create, cancel, view, and manage SkipUp meeting requests and view member information within the scoped workspace.
The skill requires a provider API key with permission to read/write meeting requests and read workspace members.
Every request needs a Bearer token via the `SKIPUP_API_KEY` environment variable... The key must have `meeting_requests.read`, `meeting_requests.write`, and `members.read` scopes.
Use a least-privilege SkipUp key, store it as an environment variable, do not paste it into chats, and rotate it if it may have been exposed.
If invoked with wrong recipients, organizer, or context, external people may receive unintended scheduling emails or meeting invites.
Creating a meeting request is a write action with external side effects: it can email participants and ultimately book a meeting.
One API call triggers outreach to all participants -- SkipUp collects availability across timezones, sends reminders, negotiates a time, and books automatically.
Confirm organizer email, participant list, meeting purpose, duration, and notification choices before creating or cancelling requests.
A paused request may not be a complete stop; scheduling activity can resume and continue outside the immediate chat session.
The external scheduling workflow can continue or resume based on later participant messages, even after the initial agent action.
If a participant sends a message with scheduling intent while the request is paused, SkipUp may automatically resume the request to avoid missing a booking opportunity.
Use cancellation, not pause, when you need to definitively stop coordination, and check request status after pausing important meetings.
Participant emails, names, timezones, meeting purpose, and optional business context may be processed by the external SkipUp service.
Meeting context, including potentially sensitive CRM notes or tone guidance, can be sent to SkipUp for AI-assisted outreach.
`context.description` | string | | Free-text instructions for the AI (e.g. CRM notes, tone guidance)
Only include context that is appropriate to share with SkipUp and potentially use in participant-facing scheduling communications.
Installer or registry prompts may not fully warn about the SkipUp API key requirement before reviewing the files.
Registry-level metadata under-declares the API key requirement that SKILL.md and package.json otherwise disclose.
Required env vars: none ... Env var declarations: none ... Primary credential: none
Treat SKIPUP_API_KEY as required despite the registry metadata and verify the installed version's metadata before use.