Work · Community report
Make a morning brief
Make a morning brief with calendar conflicts, replies owed and local weather. An external reviewer reported two deliveries; check your own schedule and source access.
What you can get
Reaches your accounts Creates or changes things in accounts you connect, with your approval.
-
It does
- Reads connected calendar and email information if you grant access
- May deliver a briefing at the schedule you configure
-
It stops and asks
- Confirm the schedule is expressed in your intended timezone.
- Compare the first briefing with your calendar and inbox before treating it as complete.
- Check that conflicts and reply ages are presented as review cues, not decisions made for you.
-
You approve
- Permission to read the selected calendar and email information
- Your review before relying on an automated recurring briefing
Derived from this task's own brief and steps, not from the source.
- Define morning scopeStops for your approval
Set cadence, timezone, calendar and inbox selections, weather location, and conflict rule.
- Collect dated source items
Gather calendar events, reply candidates, and weather observations with references.
- Rank for scanability
Separate direct conflicts, replies owed, ordinary events, and missing-access notes.
- Validate deliveryStops for your approval
Compare the first briefing with source accounts and adjust filters or timezone.
Editorial, not from the source
Works when
- You want one compact morning view of a known calendar and inbox.
- You can check the first few briefings against the source accounts.
Does not work when
- You need a guarantee that every message or calendar is included.
- You need autonomous sending or rescheduling; confirm those actions in your own product first.
Make a morning brief: review template
| Brief section | Source and timing | Review result |
|---|---|---|
| [Calendar conflict] | [Event references and conflict type] | [Check] |
| [Reply owed] | [Sender, age, unresolved point] | [Review] |
| [Weather observation] | [Location, date, source time] | [Use or ignore] |
The source case
David Pawlan reports that Instinct delivered a weekday 7am briefing on two mornings, covering calendar items, conflicts, replies owed with their age, and weather. The linked report lists five messages and a completed result. We have not reproduced the test; it does not establish long-term reliability.
A public report by someone outside this library. Not independently reproduced here.
Suggested prompt
Bring Weekday, time and timezone, Calendar account or calendar selection, Email account or inbox selection. Acts Reads connected calendar and email information if you grant access. May deliver a briefing at the schedule you configure. Source community report, checked 2026-09-16.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Weekday, time and timezone
- Calendar account or calendar selection
- Email account or inbox selection
Connected
- Your own configured calendar and email access, if available
- A weather source available in your setup
How to try it
Editorial, not from the source
- Provide the weekday, time and timezone, plus the calendar and email accounts you want considered.
- Ask for a short draft that separates calendar items, conflicts, replies owed with age, and weather.
- Review the first delivery for missing accounts, timezone errors and stale email; decide yourself whether to keep using the cadence.
Define the morning window and source scope
Specify the weekday schedule, delivery time, timezone, selected calendars, selected inboxes, and location for weather before relying on a recurring brief. “Morning” is ambiguous across travel, daylight changes, and shared calendars, so the timezone belongs in the request. Decide what counts as a calendar conflict: overlapping events, insufficient travel time, double bookings, or all-day items needing preparation. For email, define which folders or labels are in scope and whether “replies owed” means unanswered direct questions, promises you made, or messages older than a threshold. These choices create a brief that can be checked instead of a vague digest. Record the brief’s source-check time where timing matters, since an event added after the collection window cannot be represented as a known omission.
Rank conflicts and replies without inventing urgency
Present calendar entries with source references and distinguish a direct overlap from a possible preparation or travel issue. List replies owed with age, sender, and the concrete point requiring attention; do not equate old mail with priority. Weather should be dated and tied to the chosen location, not used to infer a decision about travel or clothing. When access is absent or a source is stale, say which section is incomplete. The cited report describes two weekday deliveries, not a guarantee of continuing delivery, complete account coverage, or a particular connection in this user’s setup. Keep shared calendars distinguishable from personal calendars so an invitation is not presented as a commitment without its attendance status.
Validate a recurring brief against the originals
Run the first brief as a comparison exercise. Check a few appointments against the source calendar, test whether the timezone and date boundary are correct, and inspect each reply flag against the original message. Adjust filters when newsletters, auto-replies, shared events, or old threads overwhelm the useful signal. Keep the format compact enough to scan: today’s commitments, conflicts, replies owed, weather, and a missing-access note are usually more useful than every raw event. The brief should not send replies, alter calendar events, or conceal uncertainty behind a confident summary. For weather-sensitive plans, surface the forecast observation and location rather than extrapolating consequences beyond the source data. Present date-sensitive items with the source timezone when it differs from the briefing timezone, so the morning view does not quietly shift a deadline.
Open Instinct to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
- The cited external report covers two 7am weekday deliveries and five messages; it does not prove ongoing reliability or every setup.
- Calendar, email and weather access depend on your own product setup and permissions; confirm what is actually connected.
- A briefing can identify a reply that appears overdue, but only you can judge its priority and send it.
Editorial, not from the source
- Confirm the schedule is expressed in your intended timezone.
- Compare the first briefing with your calendar and inbox before treating it as complete.
- Check that conflicts and reply ages are presented as review cues, not decisions made for you.
Editorial, not from the source
- The briefing arrives at the wrong local time
- Check the configured timezone and weekday before changing the brief itself.
- Calendar or email information is absent
- Confirm the selected account has access in your own setup; do not infer that an unavailable source was checked.
- The reply list feels noisy
- Narrow the inbox or define what counts as owed; review the next output against the source mailbox.
Common questions
Which calendars and inboxes should a morning brief include?
Name the accounts, calendars, folders, or labels that are in scope. A selected scope is safer to validate than “everything,” especially when shared calendars, newsletters, and personal mail should be treated differently.
How should a calendar conflict be defined?
Choose whether conflicts mean overlapping times, insufficient travel time, double bookings, or preparation needs. Show the underlying events and label the conflict type, because an all-day item and a direct overlap require different attention.
What does the age of a reply owed mean?
Age is the time since the relevant message, not a priority score. Include the sender and unresolved point so you can decide whether an old thread is important, closed elsewhere, or still awaiting someone else.
What does the cited morning-brief source demonstrate?
It reports two weekday 7am deliveries with calendar, replies owed, and weather in one external test. It does not establish long-term reliability, complete account coverage, or that the same sources are connected in your setup.
How should I test the first scheduled briefing?
Compare its events and reply flags with the original accounts, verify timezone and date boundaries, and note missing access or noisy filters. Keep it under review until several deliveries match the scope you intended. Review the source accounts whenever an item looks surprising.
Next
More in Work
Get recurring task recommendations — ask your own agent to check for relevant updates.