Meeting Prep
Shared Official v1.0.15Pulls calendar event details and related email threads via MCP, then produces a personalised prep document with context, talking points, and questions
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 8 nodes
Meeting Prep
Fetches meeting details and related emails via MCP, then produces a personalised prep document
Context Gather
Searches Gmail for email threads related to meeting attendees and topics
Event Fetch
Retrieves meeting details from Google Calendar via MCP — attendees, description, time, and location
Prep Synthesis
Produces a meeting prep document with context, talking points, and questions to ask
Fetch Event
Retrieves meeting details from Google Calendar via MCP
Gather Context
Searches Gmail for email threads related to meeting attendees and topics
Polish Prep
Final language polish on the meeting prep document
Synthesize Prep
Produces a meeting prep document from event details and email context
Requirements 3 services, 2 permissions, 1 data type
- LLM Service
- gmail-mcp
- google-calendar-mcp
- network:googleapis.com
- network:console.cloud.google.com
- pii
Security Passed
Detected
- Services: gmail-mcp, llm-service, google-calendar-mcp
- Permissions:
- Data Handling:
Version history 12 releases
GH#833 — drop the embedded `gmail-mcp` + `google-calendar-mcp` service nodes; dep-reference the canonical `_shared/gmail-mcp@1.0.0` + `_shared/google-calendar-mcp@1.0.0`. contents.services 2→0.
GH#760 — degrade the `polish-prep` voice section cleanly (paired with #704). The `## Voice Profile` block rendered `{{step.context.voice_profile}}` with no adjacent guard, so a profile-less user saw an empty header. Added the "If a voice profile is provided above …" reviewer-note guard, mirroring the guarded sibling `synthesise-prep`. Content-only; no bindings or logic changes.
GH#745 — declare per-step `output: {name, type}` on every execution step (event/text, context/text, prep_brief/text, polished_prep/text). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
Fix-forward after Row 3b v1.0.11 publish failure. The v1.0.11 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (1e2fdf5d…) did not match the D1 catalogue row's id (0e5ca764…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.12 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.11; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Shared
View all →Blog Drafting
Writes a complete blog post from a content brief — the core generation step
Intent Classification
Analyses text input and classifies it into intent categories
Report Authoring
Generates a structured outline and drafted prose sections for a report or thesis from a brief