Google Calendar Meeting Prep Skill for Codex

Build a practical meeting prep brief from a connected Google Calendar event and its nearby context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.

23k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

4915

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/openai/plugins --skill google-calendar-meeting-prep

What comes with it

91 102 bytes besides the instruction

agents/openai.yaml

assets/icon.png

assets/logo.png

The instruction itself

4 sections, as written by the author

Google Calendar Meeting Prep

Use this skill when the user wants a prep brief, not just the event details.

Relevant Actions

Use read_event or read_event_all_fields for the focal meeting.
Use search_events when recurrence history, adjacent meetings, or same-day context matters to the prep brief.

Workflow

Start from the event itself: title, description, attendees, recurrence context, attachments, and any obvious linked materials.
If the event points to connected docs, decks, or notes and they are cheap to follow, inspect them before writing the brief.
Build the prep brief around what the meeting appears to be for, what decisions or inputs seem likely, and what context is attached versus missing.
Highlight what the user should read or prepare first rather than dumping every detail.
Stay close to the event and its linked context. Do broader research only if the user explicitly asks for it.

Output Conventions

Lead with what this meeting appears to be about.
Call out the most relevant attachments, notes, or linked docs.
Separate confirmed context from missing context or open questions.
End with a short "what to do before this meeting" list when there is enough evidence to support it.

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens

Domain Name Brainstormer

by frostant

×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts

Scientific Brainstorming

by christophacham

×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens

GitHub Project Management

by ComeOnOliver

×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take openai/google-calendar-meeting-prep from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.