Check the input, then compare the complete deliverables
Explore the original materials, item-by-item outcomes and full report below. Attempt the input independently before using the reference to find omissions or disagreements.
All events and background are synthetic. No real Calendar, inbox or company news was read, and no invitation was accepted, declined or changed.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "google-calendar-meeting-brief",
"data": {
"target_date": "2026-10-19",
"timezone": "Asia/Shanghai",
"events": [
{
"id": "E01",
"title": "Product review",
"start": "2026-10-19T02:00:00Z",
"end": "2026-10-19T03:00:00Z",
"status": "confirmed",
"agenda": null,
"response": "accepted"
},
{
"id": "E02",
"title": "Client redesign discussion",
"start": "2026-10-19T02:30:00Z",
"end": "2026-10-19T03:30:00Z",
"status": "confirmed",
"agenda": "Homepage scope",
"response": "needsAction",
"background": "B01: price and delivery date remain unconfirmed"
},
{
"id": "E03",
"title": "Cancelled demo",
"start": "2026-10-19T07:00:00Z",
"end": "2026-10-19T08:00:00Z",
"status": "cancelled"
},
{
"id": "E04",
"title": "Materials due",
"start_date": "2026-10-19",
"end_date_exclusive": "2026-10-20",
"all_day": true
}
]
}
}Processing rules
Cover 2026-10-19 in Asia/Shanghai. Retain cancelled events in the audit trail, excluding them from active meetings. List all-day events separately. Flag overlapping active timed intervals; touching endpoints are not overlaps. Preserve unknown agendas, prices and dates. Cite only B01 as background.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Event | Asia/Shanghai | State and context | Preparation |
|---|---|---|---|
| E01 | 10:00–11:00 | Active; agenda missing | Request an agenda; overlaps E02 by 30 minutes |
| E02 | 10:30–11:30 | Active; invitation unanswered; B01 | Prepare homepage scope; price/date unconfirmed |
| E03 | 15:00–16:00 | Cancelled | Exclude from active meetings, retain evidence |
| E04 | All day | Materials deadline | Show as a reminder without inventing a meeting time |
E01 and E02 overlap from 10:30 to 11:00. Flag the conflict without rescheduling.
B01 says the price and date remain open; it does not establish an agreement.
Meeting brief — October 19, synthetic exercise 10:00–11:00 Product review [E01]: request the agenda, decisions and materials. 10:30–11:30 Client discussion [E02]: prepare homepage scope; price/date unconfirmed [B01]; response needsAction. Conflict: 10:30–11:00, 30 minutes; the user must choose an arrangement. All-day reminder: materials due [E04]. Excluded: cancelled E03. Missing: participant details, previous minutes and public news. No invitation changed.
Prepare the materials and check your tools
Start with the practice files
- Download the input and rules before the reference results.
- Confirm October 19 and Asia/Shanghai.
- Timed events use UTC timestamps; the all-day event uses dates.
Before using real services
- Verify the Calendar account, calendar identity and read tools.
- Start with one day; retain event ids, update times and pagination status.
- Define a separate scope for historical email or public news.
Complete one file-based exercise first. For real services, verify the actual account, available tools and operation scope, then follow the acceptance check at each stage.
Download the original input and rules ↓Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Read the agreed date, time zone and supplied context; prepare conflicts, gaps and meeting briefs.
Requires confirmation
Confirm event creation, rescheduling, cancellation, invitations and delivery to others. Do not commit to prices or delivery dates.
Take over after a failure
Stop inference when events, time zones or permissions are unclear. Report coverage; have the user inspect Calendar or take over login, then rerun a small batch.
Fix the date, time zone and calendar scope
Relative dates depend on the execution time zone. Distinguish the event time zone from the display zone. An exclusive all-day end date is a boundary, not an overnight meeting.
Read the uploaded input only. Restate the target date, display time zone, four event ids and date fields. Separate timed and all-day events. Do not connect Calendar or create invitations. Save scope.md.A dated event index.
Use 2026-10-19; do not turn E04 into a midnight meeting.
Normalize status and time before finding overlaps
Remove cancelled events from active interval comparisons. Compare starts and ends, retaining original timestamps so another reader can verify the conversion.
Convert start/end to Asia/Shanghai and retain originals. Mark cancelled events excluded and all-day items separate. Calculate active interval intersections with start, end and minutes. Save normalized.csv.A 30-minute E01/E02 overlap.
E01 is 10:00–11:00; E02 is 10:30–11:30; E03 is excluded.
Use only background you actually received
A title is not an agenda or proof of a decision. This input supplies only B01; missing context should become preparation questions.
For E01–E04 and B01, list known topics, supporting ids, missing material and three preparation questions. Mark unavailable participants/news as not obtained. Do not infer a price, date or client position.Preparation notes with source ids.
E01 has no agenda; E02 price and delivery date remain open.
Write a brief that separates decisions from reminders
Put conflicts, unanswered invitations and missing agendas first, followed by the timetable. Preparing a briefing does not decide attendance.
Write brief.md with the timetable, conflict, missing agendas, unanswered invitations, all-day items and unchecked sources. Retain event/background ids. Generate text only; do not accept, decline, reschedule or notify anyone.A complete one-page meeting brief.
All four inputs have an outcome; cancelled events do not inflate active counts.
Try one read-only day in your calendar
Real reads may involve pagination, recurring instances and updates. Record actual coverage rather than assuming a returned list contains every event.
Verify <account/calendar>. Read only <specific date/time zone>, at most 10 events. Report tools, pagination, event ids and updates. Handle cancellations, all-day events and recurring instances separately. List missing context without modifying Calendar or scanning the inbox.A traceable read-only day, or a clear blocker.
Account, date and coverage are explicit; incomplete reads are not called complete.
Check reruns and date rollover before scheduling
An event may move after the first briefing. Recheck the same day and a cross-day boundary; distinguish no meetings from a failed connection.
Draft a meeting-brief Skill with explicit date, Asia/Shanghai, scope, pagination, event id/update time, overlap rules and missing sources. Propose a weekday 21:00 Routine but do not create it. Refresh changed events; report connection failures separately.A reusable method and schedule proposal.
Reruns create no invitations; an empty calendar and a failed read have different statuses.
Find the evidence before choosing the next action
Every time is eight hours off
Check Z/offset on the original value and convert once. Do not add eight hours to an already localized timestamp.
Cancelled meetings remain active
Use the status field, not mere presence in the response.
All-day items fill the conflict table
Keep reminders separate from timed commitments.
Background email is inaccessible
Deliver the event brief with missing context; do not invent it from the title.
Check every item before finishing
These page-local checkboxes reset on refresh. Checking them does not verify a real service connection.
Checked 0 / 6 items
Download the inputs separately from the reference answers
Start with input and rules without showing the reference answers. After acceptance, save the report and complete prompt set.
source-data.json↓Rules and scopeDefinitions, exceptions and delivery requirements.workflow-rules.md↓Item-by-item reference resultsCompare every input with its outcome.expected-results.csv↓Complete reference reportResults, evidence and missing information.reference-report.md↓All stage prompts6 instructions with expected outputs and acceptance checks.practice-prompts.txt↓Check documented capabilities and exercise results separately
Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Reviewed within the recorded scope ·
Reviewed event time bounds, time zones, pagination and recurring/cancelled-event parameters. Account tools and real calendar data remain untested.
Documentation review evidence and limits ↗
Live workflow verification: Unverified
Unverified: documentation review only. The current Bot tool catalog does not expose Calendar. The user needs to connect/provide an accessible test calendar and a date for a bounded read. Catalog absence does not establish global disconnection.
All events and background are synthetic. No real Calendar, inbox or company news was read, and no invitation was accepted, declined or changed.
- Google Calendar: Events list ↗
Check event time boundaries, pagination and returned instances; no live Calendar call was made here.
- Grok Bot: apps and the shared computer ↗
Check connected accounts, available tools, visibility and user takeover.
- Grok Bot: Skills and Routines ↗
Validate a manual run before saving a method or scheduling it.
Try another small batch of your own material
Retain original input and operation records. Verify that each result can be traced before adding connections or recurring runs.