/calendly
Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings,
$ npx -y skills add CoWork-OS/CoWork-OS --skill calendly --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/calendly
Context preview
The summary Claude sees to decide when to auto-load this skill.
Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings,
SKILL.md
calendly.SKILL.mdname: calendly
description: "Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings, scheduling links, or availability."
Calendly
Purpose
Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings, scheduling links, or availability.
Routing
- Use when: User asks about Calendly meetings, scheduling links, availability, booking, upcoming events, or wants to manage their Calendly calendar
- Do not use when: User asks about Google Calendar, Apple Calendar, Outlook calendar, or general time management without Calendly
- Outputs: Meeting agendas, invitee details, availability windows, scheduling links, webhook configurations
- Success criteria: User receives accurate calendar data formatted as a clear agenda with times in their timezone
Trigger Examples
Positive
- Use the calendly skill for this request.
- Help me with calendly.
- User asks about Calendly meetings, scheduling links, availability, booking, upcoming events, or wants to manage their Calendly calendar
- Calendly: provide an actionable result.
Negative
- User asks about Google Calendar, Apple Calendar, Outlook calendar, or general time management without Calendly
- Do not use calendly for unrelated requests.
- This request is outside calendly scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | No | What to check or manage (e.g., 'upcoming meetings', 'cancel 3pm tomorrow', 'my scheduling links') |
Runtime Prompt
- Current runtime prompt length: 845 characters.
- Runtime prompt is defined directly in `../calendly.json`.
Read more
name: calendly description: "Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings, scheduling links, or availability."
Calendly
Purpose
Manage Calendly scheduling via the v2 API. List event types, view scheduled events, check invitee details, manage availability schedules, cancel/reschedule events, create one-off links, and configure webhooks. Use when the user asks about their calendar, upcoming meetings, scheduling links, or availability.
Routing
- Use when: User asks about Calendly meetings, scheduling links, availability, booking, upcoming events, or wants to manage their Calendly calendar
- Do not use when: User asks about Google Calendar, Apple Calendar, Outlook calendar, or general time management without Calendly
- Outputs: Meeting agendas, invitee details, availability windows, scheduling links, webhook configurations
- Success criteria: User receives accurate calendar data formatted as a clear agenda with times in their timezone
Trigger Examples
Positive
- Use the calendly skill for this request.
- Help me with calendly.
- User asks about Calendly meetings, scheduling links, availability, booking, upcoming events, or wants to manage their Calendly calendar
- Calendly: provide an actionable result.
Negative
- User asks about Google Calendar, Apple Calendar, Outlook calendar, or general time management without Calendly
- Do not use calendly for unrelated requests.
- This request is outside calendly scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | No | What to check or manage (e.g., 'upcoming meetings', 'cancel 3pm tomorrow', 'my scheduling links') |
Runtime Prompt
- Current runtime prompt length: 845 characters.
- Runtime prompt is defined directly in `../calendly.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill