name	remind-me-tomorrow
description	Capture "remind me tomorrow to X" into a dated memory entry the morning-briefing surface will read back automatically.

Remind Me Tomorrow

Trigger on "remind me tomorrow", "remind me in the morning", "明日", "明日思い出させて", "朝リマインド". Complements the broader task-manager skill — that one handles generic "remind me to X" with no time anchor; this skill specifically captures tomorrow-morning intent into the shape morning_briefing already knows to read.

Default flow

Extract the task: everything after "remind me tomorrow to" or "明日…思い出させて". If the utterance is an adjective-only fragment ("the gas bill" / "ガス代"), wrap it as "remember to check ".
Store with a tomorrow tag: call remember { text: "[tomorrow] <extracted task>", namespace: "reminders" }. The [tomorrow] prefix is the contract morning_briefing scans for; leave it literal and bracket-surrounded.
Confirm: one sentence, never a question. Use the user's own words in the confirmation so they know we captured it verbatim. En: "Got it — I'll remind you tomorrow to X." JP: "了解。明日、 Xをリマインドします。".

Morning-surface contract

morning_briefing (both the tool and the MorningBriefingSuggestionRule) look up search_memory { query: "[tomorrow]" } and read back any hits found at the top of the daily briefing. After reading, the flow clears each read reminder via forget to prevent the item re-surfacing the following day. The skill does NOT need to schedule anything — no timers, no AlarmManager, no WorkManager. Calendar-like scheduling belongs to set_timer / set_alarm.

What this skill does NOT do

No multi-day horizons. "remind me next Tuesday" is not this skill's job; that belongs to set_alarm or a future schedule-reminder skill.
No repeating reminders. The entry is single-fire. Use quiet-hours / hydration-reminder for recurring nudges.
No urgency classification. The user picked "tomorrow" — we don't second-guess that with "this sounds urgent, today?".

Follow-ups

If the user adds details immediately after confirmation ("…and tell Alex"), append to the stored entry rather than creating a second one. One reminder per utterance is the contract.
If the user says "forget tomorrow's reminder" / "明日のリマインド消して", call forget { query: "[tomorrow]", namespace: "reminders" } and confirm "Cleared." / "消しました。".

Más de este repositorio

mismo repositorio

termux-automation

yuga-hashimoto/open-dash

Run shell commands through the user's Termux app when no first-class tool fits — e.g. "git status in my project folder", "list downloads", "run ffmpeg on this file". Only used when the user has opted in under Settings → Advanced → Termux shell access.

2026-04-213

sick-day

yuga-hashimoto/open-dash

Gentle rest mode for when the user is unwell — dim lights, low volume, quiet hours, and a single hydration reminder every two hours without lecturing.

2026-04-173

where-did-i-put-it

yuga-hashimoto/open-dash

Finds a misplaced item by searching the user's memory store for prior "I put X in Y" statements; if nothing matches, offers to remember the current location instead.

2026-04-173

leaving-home

yuga-hashimoto/open-dash

Quick send-off when the user is leaving — lights out, low-battery reminder, optional weather preview, all inside a single calm sentence.

2026-04-173

arrival-home

yuga-hashimoto/open-dash

Warm welcome when the user gets home — lights up the entry, says hi, and recaps the next calendar event plus any urgent notifications in one short line.

2026-04-173

rainy-day

yuga-hashimoto/open-dash

Rainy-day check-in — inspect the forecast, and if rain is likely today, suggest a cozy indoor plan (playlist, close blinds/windows reminder) without taking destructive action.

2026-04-173

Remind Me Tomorrow

Default flow

Extract the task: everything after "remind me tomorrow to" or "明日…思い出させて". If the utterance is an adjective-only fragment ("the gas bill" / "ガス代"), wrap it as "remember to check ".

Store with a tomorrow tag: call remember { text: "[tomorrow] <extracted task>", namespace: "reminders" }. The [tomorrow] prefix is the contract morning_briefing scans for; leave it literal and bracket-surrounded.

Confirm: one sentence, never a question. Use the user's own words in the confirmation so they know we captured it verbatim. En: "Got it — I'll remind you tomorrow to X." JP: "了解。明日、 Xをリマインドします。".

Morning-surface contract

What this skill does NOT do

No multi-day horizons. "remind me next Tuesday" is not this skill's job; that belongs to set_alarm or a future schedule-reminder skill.

No repeating reminders. The entry is single-fire. Use quiet-hours / hydration-reminder for recurring nudges.

No urgency classification. The user picked "tomorrow" — we don't second-guess that with "this sounds urgent, today?".

Follow-ups

If the user adds details immediately after confirmation ("…and tell Alex"), append to the stored entry rather than creating a second one. One reminder per utterance is the contract.

If the user says "forget tomorrow's reminder" / "明日のリマインド消して", call forget { query: "[tomorrow]", namespace: "reminders" } and confirm "Cleared." / "消しました。".