mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
SKILL.mdsrc/kiro_crew/apps/builtins/mochi/agents/skills/mochi-remind/SKILL.md
GitHub@mochi-remind — Handle Due Reminders
Handle reminders that have reached their trigger time.
Steps
1. Verify Meetings (if applicable)
For items with kind=meeting, only if the user has connected a calendar tool. Do not assume a
server or tool name — look at the tools you actually have and find one that lists events in a
time range.
- List events in a window around the meeting's
triggerAt(±2 hours) to find it. - Match by subject/title (fuzzy — the label may be abbreviated).
- Check the event status:
- Cancelled: Tell the user the meeting was cancelled. Mark the item
done. - Rescheduled (calendar start differs from the item's
notes.meetingStartby >1 min; if the item has nomeetingStart, treat it as on schedule): Tell the user the new time. Keep the user's lead time (meetingStartminustriggerAt) and callupdate_watchlistwithtriggerAt= new start minus that lead andnotes.meetingStart= new start. Do NOT mark done. - Still on schedule: Proceed to notify normally (step 2).
- Cancelled: Tell the user the meeting was cancelled. Mark the item
- If the lookup fails or returns no match, proceed with the reminder anyway — don't block notification on a calendar lookup failure.
Skip this step for kind=reminder items or when you have no calendar tool.
2. Notify the User
Before notifying, check activity log for duplicates:
Call read_mochi_file({ which: "activity" }) and scan the last 10 entries.
If you find a notification entry within the last 15 minutes that already communicated
the same reminder (same label/subject), skip the notification — it was already delivered
by a concurrent agent. Just mark the item done and finish. A "got moved to …" message
from a reschedule is NOT the reminder itself and does not count as a duplicate.
Right after 00:00 UTC the log rotates, so also check "activity-yesterday".
Use perform_pet_action({ action: "notify", pushToChat: true, source: "reminder", priority: "critical", summary: "<≤100 chars>" })
with natural language — summary is required (a notify without it is dropped), and
critical is what lets a due reminder through quiet mode and an in-flight chat turn.
Single reminder: "Hey! You asked me to remind you to review the design doc"
Meeting reminder: "Heads up — Team sync starts in 5 minutes!"
Cancelled meeting: "Good news — Team sync was cancelled, you've got a free slot 🎉"
Rescheduled meeting: "Heads up — Team sync got moved to 3:30 PM (was 2:00 PM)"
Multiple reminders: "A few things! You wanted to: review the design doc, check the deployment status, and prep for the 1:1."
Late reminder (idle resume): "Welcome back! You asked me to remind you about the design doc at 2:00 PM — sorry I'm late, you were away"
Use the pet's personality — warm, concise, with occasional emoji.
3. Mark Done
Call update_watchlist to mark each reminder as done:
update_watchlist({ update: [
{ id: '<reminder-id>', status: 'done' }
]})
For rescheduled meetings, update triggerAt (do NOT set nextCheckAfter — meetings use triggerAt only):
update_watchlist({ update: [
{ id: '<meeting-id>', triggerAt: '<new start minus lead, ISO>', notes: { meetingStart: '<new start ISO>' } }
]})
4. Finish
After marking reminders done (or rescheduling), you're done. No further action needed.
Tool Restrictions
Allowed tools:
update_watchlist— mark reminders as done or rescheduleperform_pet_action— notify the userread_mochi_file— check the activity log for duplicate notificationsget_watchlist— re-read an item's currentstatusbefore notifying (Dedup Rule)- A calendar tool, if the user has connected one — used only to verify a
kind=meetingitem. Whatever it is called; do not guess at a name that isn't in your tool list.
Dedup Rule
Before notifying, check if this reminder was already handled. If the item's status is already done, skip it — another agent or the system already processed it. Never push the same reminder content to chat twice.