setup-meetly

Frontmatter

---
name: setup-meetly
version: 3
description: Use when someone gets started with Meetly, changes briefing or writing preferences, or asks for a daily or recurring briefing.
---

Make the first useful briefing feel close. Ask one or two short, related questions per turn; reuse what the user and host memory already tell you. Use the standing evidence rules in the Meetly guide.

Learn the person

Start naturally: “What does your day job involve, and what kinds of conversations do you record?” Offer examples when helpful: engineering reviews, customer or research interviews, team decisions, brainstorms, lectures. Let them describe a mix. Use accessible transcripts to propose a meeting mix, then let them correct it; do not silently infer their job or identity.

Next learn the desired depth: quick highlights, a dense brief, or an in-depth read. Default to a dense brief, decisions and useful implications first, with short transcript quotes and references. Learn technical depth and priority topics only where not already answered. Each meeting's analysis adapts to its content.

Ask whether to keep briefings in chat or also attach a compact PDF. Default to chat; accept “PDF occasionally” as on-request. Keep the chat useful even when a document is attached. Offer speaking feedback and “write in my style” as optional capabilities, using meetly-communication-coach when chosen.

Draft useful next steps proactively. Ask before time-consuming external research; record a different research preference only if the user chooses one.

Get recording and access working

Ask their platform if unknown and whether they have already recorded and connected. Load app guidance for the relevant missing step, not a long checklist. Put the pairing key instructions directly beside the field in the authorization page; never ask for a key in chat. If they do not have the app, point to the platform download. Explain the loop simply: open Meetly, press record, finish and let it sync, then ask here.

Offer calendar linking and voice training one step at a time when useful. They are optional. Source calendar snapshots or labeled segments do not prove current device permissions, voice training or recording readiness. A successful retrieval confirms access to those records only.

Save and arrange delivery

Recap the proposed profile briefly and accept corrections. Use native host memory when permitted; update an existing Meetly profile when it can be found. If existing memory cannot be inspected, apply preferences here rather than create duplicates. Only claim a lasting save after a tool result or host-provided durable confirmation. Conversational acknowledgment alone is not proof.

For “daily briefing,” clarify whether they want today's brief or daily delivery if the intent is ambiguous. For a schedule, gather time, timezone and cadence; offer morning catch-up or evening recap, and inspect existing schedules before creating a duplicate. Use ChatGPT's native Scheduled capability when it supports authenticated Meetly execution. Check current capabilities; do not repeat outdated blanket claims that connected apps cannot run on schedules. A reminder alone is not an automatic briefing. If unsupported, give the brief now and state the limit.

The scheduled instructions include meetly-briefing, the approved profile, timezone, coverage interval and PDF choice, since future runs may not inherit memory. Confirm the actual schedule result. Use explicit rolling intervals if the host cannot keep a reliable last-success checkpoint; disclose overlap and late sync. Never create a Meetly server preference or an external scheduling workaround.

First result