heartbeat-silence-check — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited heartbeat-silence-check (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A monitor-the-monitor. The heartbeat-collector writes workspace/system_memory/heartbeats.json every 15 minutes. When that write stops happening, the memory-sync audits silently report stale data forever. cont-14 found a 67-hour silence that 22 audits failed to escalate. This skill closes that gap by checking the file's mtime on a schedule and voice-alerting + Telegramming when it ages past 6 hours.
bash skills/heartbeat-silence-check/run.shExit codes:
--threshold-seconds N (default 21600 = 6h) — age past which RED fires--dry-run — print the verdict, skip voice-alert + Telegram--quiet — emit nothing on GREEN (default emits one-line status)4 misses = 60 min would be too tight. 6h is "definitely something is wrong, not a transient launchd hiccup."
+ Telegram priority=high. The whole point is to break through and notice. Low-priority would be the same failure mode this skill exists to fix.
(or a follow-up ops session) decides whether to re-bootstrap the collector vs. dig in.
build-prompt-checklist. The detection is a 20-line bash; no daemon, no library — fits the skill mold cleanly.
If the silence-detector itself fires repeatedly (say, every 30 min for hours because the underlying collector is broken and Cooper is asleep), the alerts would become noise. Mitigation: a data/state/heartbeat-silence-last-alert timestamp file. Re-alert at most once every 6 hours after first RED. Once the collector recovers (mtime fresh), the timestamp file is deleted on the next GREEN run. This avoids the alert-storm pattern.
com.dailyai.heartbeat-silence-check at 30-min cadence(StartInterval=1800).
config/launchd/com.dailyai.heartbeat-silence-check.plist.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.