google-calendar-meeting-prep
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.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- 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.
02 资源文件 3
- 参考文档agents/openai.yaml347 B
- 资产文件assets/icon.png25.5 KB
- 资产文件assets/logo.png63.1 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".