
google-calendar-meeting-prep
✓ Official★ 4,081by openai · part of openai/plugins
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.
🧩 One of 7 skills in the openai/plugins package — works on its own, and pairs well with its siblings.
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
Google Calendar Meeting Prep
Use this skill when the user wants a prep brief, not just the event details.
Relevant Actions
- Use
read_eventorread_event_all_fieldsfor the focal meeting. - Use
search_eventswhen 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.
Copy & paste — that's it
npx skills add https://github.com/openai/plugins --skill google-calendar-meeting-prepRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.