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
- CryptoZephyr/zoomtheir own version, first seen Nov 1, 2026
- obra/muse-skillstheir own version, first seen Oct 13, 2026
- Shaybush/claude-skillstheir own version, first seen Sep 10, 2026
- zcaceres/skillstheir own version, first seen Aug 19, 2026
- glebis/claude-skillstheir own version, first seen Jul 1, 2026
- JAVICHILEON/claude---Skillstheir own version, first seen Jul 1, 2026
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.
KISHOR403Skillagency-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
KISHOR403Skillbrand-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
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- glebis/claude-skills★ 410same name
- sonichi/sutando★ 396same name
- refly-ai/refly-skills★ 204same name
- obra/muse-skills★ 20same name
- zcaceres/skills★ 7same name
- Shaybush/claude-skills★ 3same name
- CryptoZephyr/zoom★ 1same name
- JAVICHILEON/claude---Skills★ 0same name
- KISHOR403/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- anecdotesSkill
- backupSkill
- checkSkill
- cite-syncSkill
- dataSkill
- diariosSkill
- distill-styleSkill
- driveSkill
- dropboxSkill
- fetch-annotationsSkill
- findings-auditSkill
- findingsSkill
- gmailSkill
- handoffSkill
- howtoSkill
- hypothesisSkill
- iatSkill
- ideaSkill
- inboxSkill
- institutionsSkill
- literatureSkill
- llmkitSkill
- meetSkill
- memory-auditSkill
- new-pipelineSkill
- new-projectSkill
- nextSkill
- otterSkill
- outlookSkill
- questionsSkill
- referee-panelSkill
- siteSkill
- style-checkSkill
- style-reviewSkill
- style-reviseSkill
- tactiqSkill
- theorySkill
- validate-sectionSkill
- whatsappSkill
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
- Distinctive: line 8
Create a Google Calendar event with the user's personal Zoom room link.
- Distinctive: line 52
Ask for confirmation before creating
- Very specific: line 60
If a contact name is ambiguous or not found in contacts.yaml, ask the user.
- Very specific: line 61
If a contact has multiple emails, use default_email unless the user specifies otherwise.
- Distinctive: line 64
If no time is given, ask for it — don't guess.
“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.
Files
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 1hset up zoom meeting with Sergio tomorrow 3pm
Extract:
- Who — one or more contact names/nicknames → resolve via contacts.yaml
- When — day and time → resolve relative to today's date and the default timezone
- 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_emailunless 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.
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
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.

