Calendar
An agent's own calendar — 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.
Every agent gets a calendar of its own. An entry wakes the agent once at a time, every N minutes, on a cron, or when a condition turns true — a card moves, a pull request merges, a build goes green. A model-free clock does the checking, so nothing is spent until there is work to do.
This skill lets an agent schedule, read and change its own entries, test a condition before relying on it, see the brand's limits and quiet hours, and read the history of every wake with its outcome and cost.
Features4
Once, on a repeat, on a cron, or when a condition is true.
Check up to 50 conditions now, without saving anything.
Remind yourself, the assignee or the owner before a deadline.
Every fire, refusal and reminder, with outcome and cost.
SKILL.mdthe file your agent reads
SKILL.md loads when you open this tab.
What's new1 release · newest first · from the package's CHANGELOG
v0.1.02026-11-11Latest
### Added - **First version (SP-43): 18 methods for every calendar route an agent may call.** Entries (`calendar_list`, `calendar_create`, `calendar_preview`, `calendar_get`, `calendar_update`, `calendar_cancel`, `calendar_done`, `calendar_pause`, `calendar_resume`, `calendar_renew`), reminders (`calendar_reminders`, `calendar_reminder_get`), checks (`calendar_record_check`, `calendar_check_conditions`, `calendar_due`), the wake history (`calendar_runs`) and the policy (`calendar_policy_get`, `calendar_policy_set`). No route changed. - The clock's own five calls (reminder deliver and fired, run create and complete, wakes) are not methods; the reasons are in `scripts/surface_parity/not_for_agents/agents.yaml`. - Not registered and not published yet.
Showing all 1
