Morning Briefing
Shared Official v1.0.14Pulls today's emails and calendar via MCP, triages by urgency, and produces a personalised day-ahead briefing
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 9 nodes
Morning Briefing
Pulls emails and calendar via MCP, triages by urgency, and produces a personalised day-ahead briefing
Briefing Synthesis
Combines triaged emails and calendar events into a personalised day-ahead briefing
Calendar Fetch
Retrieves today's calendar events from Google Calendar via MCP
Email Fetch
Retrieves recent emails from Gmail via MCP for the morning briefing
Email Triage
Triages fetched emails by urgency for the morning briefing.
Fetch Calendar
Retrieves today's calendar events from Google Calendar via MCP
Fetch Emails
Retrieves and structures recent emails from Gmail via MCP
Polish Briefing
Final language polish on the morning briefing
Synthesize Briefing
Combines triaged emails and calendar events into a morning briefing
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: llm-service, google-calendar-mcp, gmail-mcp
- Permissions:
- Data Handling:
Version history 12 releases
GH#833 — drop the embedded `gmail-mcp` + `google-calendar-mcp` service nodes; dep-reference the canonicals (`_shared/gmail-mcp@1.0.0`, `_shared/google-calendar-mcp@1.0.0`) — this bundle was the source of the canonical gmail/calendar content. Also fix a pre-existing structural bug the v0.0.21 scanner surfaced: the triage step referenced the prompt slug `triage-email-urgency` as its skill — added a local `email-triage` skill to run it. contents.services 2→0, skills +1.
GH#745 — declare per-step `output: {name, type}` on every execution step (emails/text, calendar/text, urgency_triage/text, briefing/text, polished_briefing/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` (dbb6aad1…) did not match the D1 catalogue row's id (3b8b173d…) — 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).
Wave 2: re-signed with canonical engine signing pipeline.
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 →Learning Science Reference
Reference guide to evidence-based learning techniques including spaced repetition, interleaving, retrieval practice, and elaborative interrogation
Ticket Fetch
Retrieves Jira tickets via MCP using JQL — issues, statuses, assignees, and priorities
Campaign Performance Benchmarks
Industry benchmarks for advertising and marketing metrics by channel