Skip to content
Back to skills

Google Calendar Meeting Prep

ASecurity

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.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
businessgo

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 23, 2026

npx -y skills add stanfish06/skillquarium --skill google-calendar-meeting-prep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Google Calendar Meeting Prep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Google Calendar Meeting Prep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/stanfish06-google-calendar-meeting-prep/badge)](https://www.skillsdirectory.com/skills/stanfish06-google-calendar-meeting-prep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: google-calendar-meeting-prep
description: 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.
---

# 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

1. Start from the event itself: title, description, attendees, recurrence context, attachments, and any obvious linked materials.
2. If the event points to connected docs, decks, or notes and they are cheap to follow, inspect them before writing the brief.
3. 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.
4. Highlight what the user should read or prepare first rather than dumping every detail.
5. 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.

Files in this skill

  • SKILL.md1.6 KB
  • agents/openai.yaml347 B
  • assets/icon.png25.5 KB
  • assets/logo.png63.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…