agentleFS
hsigstadhsigstad/research-kit/skills/zoom/SKILL.md

zoom

Skill0 starsChanged 4 months agoMITView on GitHub

Create a Zoom meeting as a Google Calendar event. Use when the user wants to schedule a meeting, e.g. 'set up zoom meeting with Darcio Tue 2pm'.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agency-docs-updater, brand-agency and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • KISHOR403Skill

    agency-docs-updater

    End-to-end pipeline for publishing Claude Code lab meetings. Automatically finds/creates Fathom transcript, downloads video, uploads to YouTube, generates fact-checked Russian summary, creates MDX documentation, and pushes to agency-docs for Vercel deployment. Single invocation replaces 5+ manual steps.

    Also in 3 projects that use this

  • KISHOR403Skill

    brand-agency

    Applies Agency brand colors and typography to artifacts including presentations, SVG graphics, documents, and web interfaces. This skill should be used when brand colors, visual formatting, neobrutalism style, or Agency design standards apply. Keywords - branding, corporate identity, visual identity, styling, brand colors, typography, visual formatting, visual design, neobrutalism.

    Also in 3 projects that use this

  • +10 more from KISHOR403

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a Google Calendar event with the user's personal Zoom room link.

    line 8
  2. Distinctive:

    Ask for confirmation before creating

    line 52
  3. Very specific:

    If a contact name is ambiguous or not found in contacts.yaml, ask the user.

    line 60
  4. Very specific:

    If a contact has multiple emails, use default_email unless the user specifies otherwise.

    line 61
  5. Distinctive:

    If no time is given, ask for it — don't guess.

    line 64

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zoom Meeting

Create a Google Calendar event with the user's personal Zoom room link.

Configuration

Read $RESEARCH/contacts.yaml for:

  • defaults: Zoom link, passcode, default duration, timezone, organizer email
  • contacts: name/nickname → email lookup

$RESEARCH is the research/ directory inside the workspace root (i.e. the directory containing rules/, skills/, contacts.yaml).

Parsing the request

The user may say things like:

  • /zoom Darcio Tue 2pm
  • /zoom Gui and Daniel Friday 10am 1h
  • set up zoom meeting with Sergio tomorrow 3pm

Extract:

  1. Who — one or more contact names/nicknames → resolve via contacts.yaml
  2. When — day and time → resolve relative to today's date and the default timezone
  3. Duration — if specified (e.g., "1h", "45 min"); otherwise use default from contacts.yaml

Creating the event

Use mcp__claude_ai_Google_Calendar__gcal_create_event with:

  • summary: "{OrganizerFirstName} and {Name1}" for one attendee, or "{OrganizerFirstName}, {Name1}, {Name2}, ..." for multiple (or a custom title if the user provides one). Use first names only. The organizer's first name comes from contacts.yaml defaults or the organizer email.
  • start: resolved datetime in RFC3339 with timezone from defaults
  • end: start + duration
  • location: Zoom link from defaults
  • description:
    Join Zoom Meeting
    {zoom_link}
    
    Passcode: {zoom_passcode}
  • attendees: resolved email(s) + organizer email (with organizer: true)
  • sendUpdates: "all" (so attendees get the invite)

Before sending

Show the user a summary of what will be created:

  • Title, attendees (name + email), date/time, duration
  • Ask for confirmation before creating

After creating

Show the event link and confirm it was sent.

Gotchas

  • If a contact name is ambiguous or not found in contacts.yaml, ask the user.
  • If a contact has multiple emails, use default_email unless the user specifies otherwise.
  • Resolve "tomorrow", "Tuesday", "next week" etc. relative to today's date.
  • "Tue" means the next upcoming Tuesday (today or later).
  • If no time is given, ask for it — don't guess.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.