Reconstruct the thread
Find the latest ask, response, invite, cancellation, RSVP, and any windows that have gone stale.
Meeting Scheduling Copilot · Skill showcase
Make the next meeting move.
Turn scattered email and calendar context into a short, decision-ready queue: what needs action, who should attend, which times work, and what to say next.
Sample data only · No email sent · No invite created
From thread to next step
A scheduling queue with the context intact.
The skill checks the latest chronology before it recommends a reply or a time.
Rank a few viable times
Honor client windows first, check the required attendees, resolve timezone assumptions, and suppress duplicates.
Hand back a clear draft
See who should attend, why it matters now, the best next action, and a reply ready for your review.
Try the workflow
Build a sample review queue.
Use a fictional client and choose what the latest thread context shows. The same deterministic transformation powers the sample and manual path.
OUTPUT
Your review queue will appear here.
Enter a fictional client and meeting purpose, choose the latest thread state, then generate a draft for review.
Thread stateNext actionReply draft
Privacy: The demo uses deterministic browser-side logic. It does not connect to Outlook, send your fields to an AI model, or store them. If PostHog is configured, only the approved event names, scenario, mode, and aggregate counts are sent; field contents are excluded.
Take the skill with you
Bring the full workflow into Codex.
Install the supplied skill package to review scheduling threads with your connected tools. The skill drafts next steps for your review; it does not send messages or create invites by default.
meeting-scheduling-copilot-v1.0.zipSkill · references · scripts
Download skillYour review stays in your hands.
The Site demo is synthetic and stays in your browser. The downloadable Codex skill works with the email and calendar context available when you invoke it, and returns drafts for review. No email is sent and no calendar invite is created unless you explicitly ask for that action in your connected workflow.