Skill

Schedule meeting

Find meeting times that work for the user and one or more other people, draft the invite, and wait for confirmation before creating it. Does not auto-create or auto-send invites.

npx claudepluginhub sitloboi2012/team-marketplace --plugin team-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Invocation: user only.** This skill creates calendar artifacts that ping other humans — always wait for approval.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Schedule meeting

Invocation: user only. This skill creates calendar artifacts that ping other humans — always wait for approval.

Workflow

1. Parse the ask

From $ARGUMENTS extract:

Attendees (emails or @-names)
Topic / title
Duration (default 30 min if not given)
Constraints ("this week", "before Friday", "morning only", "avoid their Thursday", etc.)

Ask the user for anything material that's missing. Don't guess durations over an hour.

2. Check free/busy

Using the Google Workspace MCP:

Pull the user's calendar for the proposed window.
If attendees are inside the organization, pull their free/busy too. If they're external, skip and note that their availability is unknown.
Respect the team's timezone rule: the user's HQ timezone from CLAUDE.md, but also include each attendee's timezone if known.

3. Propose 3 slots

Pick 3 candidate slots that work for the user and fit the constraints. Prefer:

Avoid stacking against existing meetings with < 15 min buffer on either side.
Avoid before 9am or after 6pm in any attendee's timezone unless the user said otherwise.
Prefer contiguous blocks that don't fragment the user's focus time.

Output format:

Proposed: <topic>, <duration>, with <attendees>

Option A: <day YYYY-MM-DD> <HH:MM>–<HH:MM>  <TZ>  (also <HH:MM> in <other TZ>)
Option B: ...
Option C: ...

Conflicts checked: <who> — OK. <who external> — availability unknown, will propose all 3.

4. Draft the invite

Once the user picks an option (or asks for different slots):

Title: <title>
When: <selected slot>
Where: Google Meet (auto-generated)  | or physical | or "No video — async doc instead"
Attendees: <emails>
Description:
  <agenda — 2-4 bullets>
  <pre-read link if any>
  <desired outcome — 1 line>

Agenda is mandatory. If the user can't state a desired outcome in one line, flag that the meeting probably doesn't need to happen yet.

5. Wait, then create

The user says "create it" / "send it" / approves. Then:

Create the event via the Google Workspace MCP.
Return the event link + confirmation that invites were sent.

Don't

Don't propose 30+ min meetings for things that read like a Slack thread or a Notion doc. If the user's ask looks async-solvable, say so once and let the user override.
Don't schedule anything before the user confirms.
Don't include people the user didn't name.