Public artifact · Tool workflows
Maintain trip context and regenerate the right travel reminders
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Travel reminders become unreliable when itinerary changes do not reach every traveller or the people expecting updates.
Agent job
Record trip details, regenerate affected reminders and route bounded itinerary changes to the selected travellers and watchers.
Expected output
Updated trip reminders and authorized itinerary notices reflecting the revised travel context.
Where this framing comes from
- Core problem: Editorial purpose framing
- Agent job: Editorial purpose framing
- Expected output: Editorial purpose framing
- Relevant job roles: Editorial purpose framing
- Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
Read the attributed source evidence and original caveats below ↓
Why use this
A changed flight or overnight stop can leave reminders correct in isolation but wrong for the revised journey. Travellers may need different alerts from people who only want a brief arrival update, especially across time zones.
A trip-change preview could show which reminders become obsolete and what each authorized recipient would receive. The owner could inspect the consequences of one itinerary edit without distributing a complete itinerary to everyone involved.
Why an agent / simpler alternative
- Useful judgment
Interpret an itinerary change and identify affected reminders while preserving the owner's recipient boundaries.
- Simpler alternative
Use calendar reminders for a simple solo trip with no routed updates.
- Unsuitable when
Recipient identities, trip dates or time zones are unresolved.
Proposed inputs
- Name
Itinerary revisions
- Owner
Traveller
- Minimum scope
Inventoried segments, local time zones and revision identifiers
- Quality check
Distinguish cancelled segments from delayed ones.
- Name
Notification matrix
- Owner
Trip organizer
- Minimum scope
Approved traveller and watcher roles with permitted fields
- Quality check
Confirm recipients and avoid inferring group membership.
Access and setup — proposed or unknown
- Proposed minimum
Read-only itinerary copies and a local reminder-difference preview.
- Compatibility unknowns
Unknown: current runtime, messaging routes, scheduling semantics and timezone handling.
- External actions requiring approval
Creating or cancelling reminders and sending bounded itinerary details to named recipients.
Expected deliverable and review checks
- Proposed artifact
Before-and-after reminder manifest plus per-recipient message previews.
- Critical checks
Each reminder uses the revised segment and correct local date.
Watcher notices reveal only the authorized subset of travel information.
- Missing output evidence
No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.
Failure signals and proposed responses
- Signal
An old departure alert survives a cancelled segment.
- Why it matters
A traveller may act on instructions that no longer apply.
- Proposed response
Link alerts to segment versions and place superseded alerts in the cancellation preview.
- Signal
A watcher receives lodging or group details they do not need.
- Why it matters
Recipient routing can disclose excess personal information.
- Proposed response
Rebuild that recipient's preview from the approved field allowlist.
Effort and cost — unknown
- Setup work
Normalize segment IDs, time zones and notification permissions.
- Ongoing review
Reconcile itinerary revisions and recipient changes.
- Unknowns
Unknown: delivery reliability, scheduler costs and handling of simultaneous edits.
First check — proposed, unexecuted
- Status
proposed_unexecuted
- Synthetic fixture
A fictional two-city trip moves a flight across midnight; one traveller and one watcher have different allowed fields.
- Acceptance checks
Identify obsolete reminders and the new local date.
Keep the watcher's preview limited to the approved arrival update.
- Stop conditions
Live messages, real locations or scheduler writes are required.
Limits
Recipient routing needs bounded authorization; a trip-context record alone does not authorize future notices.
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.
Original source
https://github.com/kmanan/spratt-skills ↗Attributed to: GitHub user kmanan
Public artifact- Original action type
- tool_action
- What the source supports
- OpenClaw records trip details; deterministic components regenerate affected reminders and route changes to the appropriate travellers and watchers.
- Source outcome limits
- The public artifact supports the described output. It does not by itself establish independent reproduction or end-to-end execution reliability.
- Evidence attribution caveat
- The public artifact supports the described output. It does not by itself establish independent reproduction or end-to-end execution reliability.
- Source approval description
- Recipient-routing setup asks whether travel is solo or group.
- Named tools
- OpenClaw; SQLite; Python; BlueBubbles; iMessage.
- Model or version
- Unknown
- Publication date
- Unknown
- Source last checked
- 2026-10-14
- Demonstrated in Canada
- Unknown
- Canadian availability
- Unknown
- Proposed Canadian adaptation
- Check Canadian carrier coverage, local time zones and explicit recipient consent. Use synthetic itineraries first.
- Recommended approval boundaries
- Approve travellers, watcher recipients and the bounded itinerary information shared.