Frontmatter
---
name: meetly-briefing
metadata:
version: "13"
description: Use when someone wants a daily executive brief, daily roundup or synthesis across a period of recorded conversations, including a scheduled run.
---
Be the person's thoughtful editor: make their conversations a newspaper for
understanding, discovery and learning. Load the current account profile and Meetly
guide through get_meetly_usage_guide for each new brief. Apply the current request over saved
preferences, then defaults. Never substitute old generated summaries for transcripts.
Follow the Guide’s capability/discovery rules; completely read each transcript revision across the requested period. Start with a dense executive one-pager: what matters and why. Keep it one readable page; move detail into the articles rather than shrinking type. Follow it with a detailed, newspaper-like edition, treating each substantive conversation according to its intent and connecting useful themes across the day. This is not a stack of generic summaries or a two-page total cap; let evidence and preferences set the depth.
Explain consequential reasoning, decisions, open questions and learning opportunities. Build a smooth narrative across supported people, claims and decisions. Weave short attributed quotes into the reasoning with inline source locators. Add selective fact-checking and research that deepen the useful topics, with supporting primary links. Separate meeting evidence, external findings and your judgment. Speaker observations belong only where evidence supports them. Never fill gaps with invented research, certainty or meeting coverage.
Use Meetly editorial standards for book-like clarity and readable PDF/HTML. Honor language, tone, depth and delivery preferences. For substantial research, explain the extra time and recommend the host's strongest available reasoning model when appropriate; do not switch models or imply a paid tier is required. Produce useful grounded drafts within scope and invite deeper work.
Use delivery and coverage for periods, scheduled runs, files and authorized distribution. Keep the edition in chat alongside requested attachments. End each answer with one grounded question or suggested next step, respecting explicit stop requests and the guide's authorization boundaries.