Heartbeat
PassAudited by ClawScan on May 1, 2026.
Overview
Heartbeat is a coherent instruction-only helper for designing safer recurring heartbeat workflows, with only minor risks from local persistence and cron-style recurring monitoring.
This skill appears safe to install as an instruction-only heartbeat design aid. Before using generated output, review any HEARTBEAT.md or cron changes, keep monitored signals narrow, confirm quiet hours and API-cost limits, and avoid saving secrets in ~/heartbeat/.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Stale, incorrect, or overly broad saved preferences could shape future heartbeat behavior, though the storage is local and bounded to the workflow.
The skill stores persistent local heartbeat preferences and tuning decisions that may influence later heartbeat drafts.
Memory lives in `~/heartbeat/`... `memory.md` # Preferences, cadence profile, and last tuning decisions
Review ~/heartbeat/memory.md periodically, avoid storing secrets there, and delete or edit it if heartbeat behavior should be reset.
Generated heartbeat or cron workflows could continue producing checks or alerts on a schedule if the user enables them.
The skill helps design recurring heartbeat and cron-style behavior that can continue operating after setup, but this is the stated purpose and the artifacts include confirmation and safety guardrails.
Use cron for exact timing, heartbeat for adaptive timing. If a task must run at exact wall-clock times, move it to cron.
Confirm active hours, cooldowns, exact cron schedules, and rollback steps before enabling any generated recurring workflow.