Reminders
Reminders for an agent: its own calendar of entries that wake it at a time, on a repeat, or when a condition turns true, with reminders, a per-owner policy and the history of every wake. Served by the main API at /api/v1/calendar/*, which forwards to AgentBoard's calendar; the brand comes from the caller's own token, never a parameter.
I built Reminders so your agent can return for a named job without waking every few minutes to ask whether anything changed. Give it a follow-up tomorrow, a weekly review until a chosen date, or a return when an approval card is done.
A model-free clock checks the calendar and supported conditions. While the card is pending, the agent can stay asleep instead of loading its instructions and memory just to check. Real work still uses model tokens. The clock may poll conditions; it does not need a model for those checks.
Reminders exposes 18 methods to manage entries, preview schedules, test conditions and read wake history. Check up to 50 conditions without saving an entry. Pause, move or cancel a planned return, and inspect outcomes and costs afterward.
Real wakes require live mode and must fit the owner's policy, limits and quiet hours. Shadow mode records fires without waking anyone. Pair Reminders with AgentBoard when a supported card status should start the next task. Install @opvs-ai/reminders and ask your agent to return when that approval is done.
Features5
Set a time, bounded repeat or supported condition for a named job.
Keep supported condition checks off the agent model; real work still uses tokens.
Preview schedules and test up to 50 conditions without creating an entry.
Keep real wakes within live mode, limits and quiet hours; record shadow fires.
Inspect fires, refusals and reminders with outcomes and costs.
Videos1 video
DemoReminders · Demo video
Demo · SpiderMediaArticles about Reminders1 article
Videos1 video
DemoReminders · Demo video
Demo · SpiderMediaArticles about Reminders1 article
Showing all 1
SKILL.mdthe file your agent reads
SKILL.md loads when you open this tab.
What's new3 releases · newest first · from the package's CHANGELOG
v0.1.22026-11-13Latest
- Add the approved MS-57 calendar hero and three film-derived marketplace panels. - Rewrite marketplace copy around purposeful returns and model-free checks, with live-mode and policy limits. - Add five verb-led features and marketplace discovery examples to the README. - Preserve the existing demo film, agent guidance, schemas and execution behavior.
v0.1.12026-11-12
- The marketplace listing shows the launch film. No skill change.
v0.1.02026-11-12
### Added - **First version under the store name Reminders (MS-42).** It replaces `@opvs-ai/calendar` 0.1.0 (SP-43, live as tier `internal` since 11 Nov) and is customer-visible (tier `beta`). The 18 routes are unchanged; the skill id is `reminders` and every method is renamed: | Was (`@opvs-ai/calendar`) | Now | |---|---| | `calendar_list` | `reminders_list` | | `calendar_create` | `reminders_create` | | `calendar_preview` | `reminders_preview` | | `calendar_get` | `reminders_get` | | `calendar_update` | `reminders_update` | | `calendar_cancel` | `reminders_cancel` | | `calendar_done` | `reminders_done` | | `calendar_pause` | `reminders_pause` | | `calendar_resume` | `reminders_resume` | | `calendar_renew` | `reminders_renew` | | `calendar_reminders` | `reminders_entry_reminders` | | `calendar_reminder_get` | `reminders_reminder_get` | | `calendar_record_check` | `reminders_record_check` | | `calendar_check_conditions` | `reminders_check_conditions` | | `calendar_due` | `reminders_due` | | `calendar_runs` | `reminders_runs` | | `calendar_policy_get` | `reminders_policy_get` | | `calendar_policy_set` | `reminders_policy_set` | The new prefix also keeps these names clear of the gateway's always-on native `calendar_add` / `calendar_list` / `calendar_cancel` / `calendar_preview` tools (skills-meta plugin). - The clock's own five calls (reminder deliver and fired, run create and complete, wakes) are still not methods; the reasons are in `scripts/surface_parity/not_for_agents/agents.yaml`. - No heartbeat methods: those come later from the heartbeat planner's code. - **Layers:** 4 references, 5 recipes, a registry of 6 entry bodies (each traced to a live entry), 8 learnings, `instructions/`, and the scripts `verify-entry`, `verify-condition`, `verify-run-report` with 20 `node --test` cases. ### Fixed (against the calendar code, compared with `calendar`) - `condition.value` is required on create and update (AgentBoard refuses it missing). - `reminders_update` carries the full nested shape of `condition` and `reminders`; reminder items gain `via`. - `reminders_check_conditions` `source` is the 10 check sources, which differ from the 9 an entry can save (`metric`, `activity` check-only; `factory_finding` entry-only). - `default_reminders` is keyed by entry kind (task, delegation, wait), not schedule kind.
Showing all 3
