Menu
Configure periodic background checklist runs
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Read, search, send, and manage messages across Gmail, Outlook, Telegram, and other platforms
An on-demand personal daily briefing — weather, headlines, the shape of your day, and one thing worth your attention — in a sharp executive-assistant voice. The general-purpose morning brief; richer work or admin digests compose it as their general layer.
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
Delegate a big or high-stakes job to a fleet of parallel subagents, orchestrated deterministically; runs unattended and reports back
Manage contacts, communication channels, access control, and invite links
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
| name | vellum-heartbeat |
| description | Configure periodic background checklist runs |
| compatibility | Designed for Vellum personal assistants |
| metadata | {"emoji":"💓","vellum":{"category":"system","display-name":"Heartbeat","activation-hints":["Set up a heartbeat, periodic checklist, background health check, or recurring background task"],"avoid-when":["One-off or recurring schedules with specific payloads - use the schedule skill instead"]}} |
The heartbeat feature runs your HEARTBEAT.md checklist periodically in a background conversation. Each run, the assistant works through the checklist and flags anything that needs attention.
Edit config.json using file_edit:
heartbeat.enabled to true.heartbeat.intervalMs (milliseconds between runs, default: 3600000 = 1 hour).heartbeat.activeHoursStart and heartbeat.activeHoursEnd (0-23) to restrict runs to certain hours. Both must be set together.Example config.json heartbeat section:
{
"heartbeat": {
"enabled": true,
"intervalMs": 1800000,
"activeHoursStart": 8,
"activeHoursEnd": 22
}
}
Then edit HEARTBEAT.md with the checklist items. The assistant will work through this file each heartbeat run.
heartbeat.enabled requires an assistant restart to take effect.HEARTBEAT.md take effect on the next heartbeat run (no restart needed).Heartbeat runs use the heartbeatAgent call site, which by default resolves to the
cost-optimized profile so background checks stay cheap. Override via
llm.callSites.heartbeatAgent in workspace config (profile, provider, model,
effort, thinking — whatever the profile supports).