Agent skill

Meeting Scheduler

by seb1n in seb1n/awesome-ai-agent-skills

Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing…

MITAuto-check passed

Install Meeting Scheduler

skills CLI
$ npx skills add seb1n/awesome-ai-agent-skills --skill meeting-scheduler -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install seb1n/awesome-ai-agent-skills meeting-scheduler --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/productivity-and-workflow/meeting-scheduler .claude/skills/meeting-scheduler && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
meeting-scheduler
GitHub stars
206
Token cost
~2k tokens
SKILL.md length
798 words
Files
1
Skills in repo
101
Repo updated
First seen
Licence
MIT

At a glance

Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing…

  • Works in 6 steps: Parse the Meeting Request → Resolve Time Zones → Check Calendar Availability → …
  • The user requests meeting scheduler
  • SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Meeting Scheduler is an agent skill from seb1n/awesome-ai-agent-skills. Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs. Use when the user requests meeting scheduler or provides relevant inputs for this workflow.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.

When your agent uses it

  • The user requests meeting scheduler
  • Provides relevant inputs for this workflow

Example prompts

  • “Use the meeting-scheduler skill to schedule meetings with internal and external stakeholders by parsing natural language requests, resolving time…”
  • “/meeting-scheduler”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Parse the Meeting Request
  2. Resolve Time Zones
  3. Check Calendar Availability
  4. Propose Optimal Time Slots
  5. Send Calendar Invitations
  6. Track RSVPs and Handle Changes

What it can do on your machine

Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Meeting Scheduler loads about 2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 798 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 798 words, ~1,983 tokens.

Download SKILL.mdSave it as .claude/skills/meeting-scheduler/SKILL.md (or your agent's skills folder).
name
meeting-scheduler
description
Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs. Use when the user requests meeting scheduler or provides relevant inputs for this workflow.
license
MIT
metadata.author
awesome-ai-agent-skills contributors
metadata.version
1.1.0

Meeting Scheduler

This skill enables an AI agent to handle end-to-end meeting coordination. Given a natural language request, the agent identifies participants, resolves time zone differences, queries calendar availability, proposes conflict-free time slots, dispatches calendar invitations, and tracks RSVPs. It integrates with Google Calendar, Microsoft Outlook, and Calendly to cover the most common enterprise and freelance scheduling workflows.

Workflow

  1. Parse the Meeting Request Extract structured data from the user's natural language input. Identify all required participants (by name, email, or team alias), the meeting topic or agenda, the desired duration, and any date or time constraints such as "next Tuesday afternoon" or "before end of sprint." Flag any ambiguous references for clarification before proceeding.

  2. Resolve Time Zones Look up each participant's configured time zone from their calendar profile or contact record. Convert all proposed windows into each participant's local time so that comparisons are accurate. When a participant's time zone is unknown, prompt the organizer to confirm it. Display all suggested times with explicit time zone labels (e.g., "3:00 PM EST / 12:00 PM PST") to avoid confusion.

  3. Check Calendar Availability Query each participant's calendar through the appropriate integration (Google Calendar API, Microsoft Graph API, or Calendly availability endpoint). Collect busy blocks for the requested date range and compute the intersection of free windows. Respect each participant's working-hours preferences and any configured focus-time or no-meeting blocks. Apply a configurable buffer (default 10 minutes) between adjacent meetings to allow transition time.

  4. Propose Optimal Time Slots Rank the available windows using a scoring heuristic: prefer slots that fall within standard working hours for all participants, minimize the number of early-morning or late-evening local times, and favor earlier dates when urgency is indicated. Present the top three ranked options to the organizer with a summary showing each participant's local time.

  5. Send Calendar Invitations Once the organizer confirms a slot, create the calendar event via the appropriate API. Attach the agenda, video-conferencing link (Zoom, Google Meet, or Teams), and any relevant documents. Send invitation emails to all participants. For external participants without calendar integration, send a standalone email with an .ics attachment.

  6. Track RSVPs and Handle Changes Monitor invitation responses as they arrive. Notify the organizer of acceptances, tentative replies, and declines. If a critical participant declines, automatically propose alternative slots from the remaining availability and initiate a rebooking flow. For recurring meetings, track attendance patterns and flag consistently conflicting participants so the organizer can adjust the cadence.

Usage

Provide a natural language request that includes the participants, topic, approximate duration, and any scheduling constraints. The agent will handle the rest.

"Schedule a 30-minute meeting with John and Jane to discuss the Q3 report sometime next week. Prefer mornings."

You can also ask for recurring meetings, rescheduling, or cancellations:

"Reschedule tomorrow's design review to Thursday. Same time if possible, otherwise find a new slot."
"Set up a weekly 15-minute standup with the backend team every Monday at 9:30 AM ET starting next week."

Examples

Example 1 — Cross-Timezone Meeting with Availability Matrix

User input:

"Schedule a 1-hour architecture review with Priya (IST), Marcus (CET), and Li (CST, China) this Thursday or Friday. Avoid early mornings for everyone."

Agent output:

I checked calendars for Priya, Marcus, and Li. Here is the availability matrix:

                        Priya (IST)    Marcus (CET)    Li (CST)
Thu 10:00–11:00 UTC     3:30 PM        11:00 AM        6:00 PM
Thu 12:00–13:00 UTC     5:30 PM        1:00 PM         8:00 PM ⚠️
Fri 09:00–10:00 UTC     2:30 PM        10:00 AM        5:00 PM  ✅ Best

Recommended: Friday 09:00–10:00 UTC
 — Falls within working hours for all three participants.
 — No conflicts detected.

Shall I send the invitation for Friday 09:00–10:00 UTC with a Google Meet link?
Example 2 — Rescheduling with Conflict Resolution

User input:

"The Wednesday product sync conflicts with Alice's dentist appointment. Move it to another day this week. Bob and Carol also attend."

Agent output:

Current meeting: Wednesday 2:00–2:30 PM ET (Alice, Bob, Carol)

Alice is unavailable Wednesday 1:00–4:00 PM ET (personal appointment).
Bob is unavailable Thursday all day (PTO).
Carol has no additional conflicts this week.

Available alternatives:
  1. Tuesday  2:00–2:30 PM ET  — all three free ✅
  2. Friday   10:00–10:30 AM ET — all three free
  3. Friday   3:00–3:30 PM ET  — all three free

Recommendation: Option 1 (Tuesday 2:00 PM ET) keeps the same time of day.

Shall I reschedule to Tuesday and notify all participants?
Show full SKILL.md (334 more words)Show less

Best Practices

  • Always display times with time zone labels. Never present a bare time like "3:00 PM" without specifying the zone. This prevents the most common source of scheduling errors.
  • Include buffer time between meetings. Default to 10 minutes. Back-to-back meetings cause fatigue and late arrivals. Allow organizers to configure this per-calendar.
  • Respect working-hours boundaries. Do not propose 7:00 AM or 9:00 PM slots unless the participant has explicitly marked those hours as available.
  • Confirm before sending. Always present the proposed slot and attendee list to the organizer for approval before dispatching invitations. Automated sends should be opt-in only.
  • Handle external participants gracefully. When a participant has no connected calendar, fall back to email-based availability polling or attach an .ics file they can import manually.
  • Track recurring meeting health. For recurring events, periodically report attendance rates and suggest cadence changes if attendance drops below a threshold (e.g., 60%).

Edge Cases

  • No overlapping availability found. When calendars have no common free window in the requested range, widen the search to the following week and inform the organizer. Alternatively, suggest splitting into two smaller meetings with partial attendance.
  • Unknown or ambiguous time zones. If a participant's time zone cannot be determined from their profile, ask the organizer to confirm before proposing slots. Never assume a default zone silently.
  • Participant not found. If a name cannot be resolved to a calendar or email address, list possible matches and ask the organizer to disambiguate.
  • Calendar API rate limits or outages. If an availability check fails, retry with exponential backoff up to three times. If the service remains unavailable, inform the organizer and offer to try again later or proceed with partial availability data.
  • Last-minute cancellations. If a participant declines within one hour of the meeting start, notify the organizer immediately and ask whether to proceed, cancel, or reschedule.
  • All-day events and focus blocks. Treat all-day calendar events as tentative unless they are explicitly marked "busy." Respect focus-time blocks as unavailable by default but allow the organizer to override.

© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in productivity-and-workflow/meeting-scheduler of seb1n/awesome-ai-agent-skills.

Open the folder on GitHubat commit 75865a5

Compare with similar skills

Meeting Scheduler next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Meeting Scheduler compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Meeting Scheduler this skillseb1n/awesome-ai-agent-skills206—~2kAutomated safety check: PassMIT
Scheduleasgeirtj/system_prompts_leaks69k—~2.9kAutomated safety check: PassCC0-1.0
Scheduleasgeirtj/system_prompts_leaks69k—~597Automated safety check: PassCC0-1.0
Meetingsalirezarezvani/claude-skills28k—~1.5kAutomated safety check: PassMIT
Meeting Minutesgithub/awesome-copilot40k2 repos~2kAutomated safety check: PassMIT
Meeting Schedulingamd/gaia1.6k—~420Automated safety check: PassMIT

Similar skills

  • Schedule

    asgeirtj/system_prompts_leaks

    Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.

    69k GitHub stars~2.9k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Schedule

    asgeirtj/system_prompts_leaks

    Create or update a scheduled task that runs automatically. An agent skill from asgeirtj/system_prompts_leaks.

    69k GitHub stars~597 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Meetings

    alirezarezvani/claude-skills

    A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…

    28k GitHub stars~1.5k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Meeting Minutes

    github/awesome-copilot

    Official

    Generate concise, actionable meeting minutes for internal meetings.

    40k GitHub starsUsed in 2 repos~2k tokens
    Productivity & AutomationAuto-check passed
  • Turn meeting requests in email into calendar decisions — accept, decline, or propose another time.

    1.6k GitHub stars~420 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Meeting Scheduler Helper

    jeremylongshore/tons-of-skills-marketplace

    Configure with meeting scheduler helper operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~591 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

More from seb1n/awesome-ai-agent-skills

All 101 skills in this repo
  • Agent Red Teaming

    seb1n/awesome-ai-agent-skills

    Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.

    206 GitHub stars~2.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Eu AI Act Readiness

    seb1n/awesome-ai-agent-skills

    Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…

    206 GitHub stars~3.3k tokensUpdated 2 mo ago
    Auto-check passed
  • Human In The Loop

    seb1n/awesome-ai-agent-skills

    Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • MCP Server Building

    seb1n/awesome-ai-agent-skills

    Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • PDF Processing

    seb1n/awesome-ai-agent-skills

    Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • Skill Supply Chain Audit

    seb1n/awesome-ai-agent-skills

    Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.

    206 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Meeting Scheduler

What does Meeting Scheduler do?

Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing…. Meeting Scheduler is an agent skill from seb1n/awesome-ai-agent-skills. Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs.

When should I use Meeting Scheduler?

Meeting Scheduler fits situations like: the user requests meeting scheduler; provides relevant inputs for this workflow.

How do I install Meeting Scheduler in Claude Code?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill meeting-scheduler -a claude-code`. Or copy the skill folder (productivity-and-workflow/meeting-scheduler in seb1n/awesome-ai-agent-skills) into .claude/skills/meeting-scheduler in your project. Claude Code loads it when a task matches its description.

How do I install Meeting Scheduler in Codex?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill meeting-scheduler -a codex`. Or copy the skill folder (productivity-and-workflow/meeting-scheduler in seb1n/awesome-ai-agent-skills) into .agents/skills/meeting-scheduler in your project. Codex loads it when a task matches its description.

Can I use Meeting Scheduler in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill meeting-scheduler -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-scheduler, .gemini/skills/meeting-scheduler, .github/skills/meeting-scheduler and .opencode/skills/meeting-scheduler in your project.

What does Meeting Scheduler need to run?

SKILL.md names no scripts, command-line tools or credentials: Meeting Scheduler is instructions for the agent only.

Does Meeting Scheduler access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Meeting Scheduler safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Meeting Scheduler use?

Meeting Scheduler is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meeting Scheduler use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Meeting Scheduler?

Skills that share tags, products or a category with Meeting Scheduler: Schedule (asgeirtj/system_prompts_leaks, 69k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars), Meetings (alirezarezvani/claude-skills, 28k stars) and Meeting Minutes (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meeting Scheduler?

seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.

Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.