Remind Me Later

Problem

When a user wants condition-based reminders to become manageable subscriptions, rather than repeated manual checks, temporary triggers, or constant monitoring, this skill is useful. It maps vague asks into objects that can be created, listed, updated, enabled, disabled, or canceled, covering stock tracking, strategy screening, rank lists, and arbitrary XS custom conditions. It fits requests like “remind me if it drops 5%” or “watch Moutai before earnings,” and can also answer “what reminders do I have.”

How it works

• Use the unified entry wm.sh run for actions such as list, create, get, update, enable, and cancel.
• create expects real product fields, such as type, name, and configuration; common types include pr_stock, strategy_screening, pr_rank / market_rank, and xs.
• Prefer type=xs for custom logic, and use the notify value returned through the notify-protocol to control push behavior.
• list, create, and get responses include deeplinks; use the provided Markdown links as-is, with wmToken included, pointing to subscription management /profile/subscriptions. Do not handcraft /reminders or legacy paths.
• On SCOPE_DENIED, surface grant_url and ask the user to authorize, then refresh the token, instead of describing manual console steps.
• trigger is disabled by default and requires explicit user confirmation plus the host flow.

Boundaries

• Use wm-watchlist when only organizing or viewing watchlist groups.
• Use wm-company-card for real-time price or market-trigger queries.
• There is no standalone earnings_window engine; earnings-related reminders still depend on push_control.push_time, events, or legacy copy hints.
• Do not configure push_channel keys, do not switch to third-party screeners for index gaps, and do not handcraft reminder landing URLs.