heartbeat-implementer

Name: heartbeat-implementer
Availability: InStock
Author: TinNguyen

Coordinates periodic heartbeat checks for AI agents and alerts only when needed.

1|Updated Jan 26, 2026

Search Tags:#agent #LLM #notifications #scheduling #delivery #heartbeat #timezones

Ready to run

npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill heartbeat-implementer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heartbeat-implementer
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/heartbeat-implementer
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill heartbeat-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automate the reliable scheduling of periodic heartbeat checks for AI agents and surface alerts only when attention is required.

Core Features & Use Cases

Timezone-aware heartbeat scheduling with configurable intervals
Token-based suppression to avoid duplicate alerts
Multi-channel delivery and per-agent configuration for cost control
Hot-reload capable with preserved timing state on config changes
Real-world pattern: keep agents responsive while minimizing unnecessary LLM usage

Quick Start

Set up a production-ready heartbeat system that checks for pending tasks every 30 minutes and delivers alerts to the configured channel only when needed.

Frequently Asked Questions about heartbeat-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I schedule periodic heartbeat checks for AI agents across multiple timezones?▼

You can schedule periodic heartbeat checks for AI agents using timezone-aware intervals that align with configurable active hours. This ensures checks only occur during designated times, preventing unnecessary LLM usage during off-hours.

How do I prevent duplicate alerts when running multiple AI agents?▼

Duplicate alerts in multi-agent systems are prevented through token-based suppression and duplicate detection mechanisms. These features identify redundant triggers and suppress them, ensuring notifications are delivered only once per event.

What is the best way to automate agent notifications only when attention is required?▼

Automating agent notifications only when attention is required involves implementing a production-grade guard chain that evaluates heartbeat states. Alerts are surfaced to delivery channels exclusively when pending tasks or failures are detected.

Can I preserve heartbeat timing state when reloading agent configurations?▼

Yes, heartbeat timing state is preserved during hot-reload configuration changes. The system maintains session timing restoration and wake scheduling, allowing updates without disrupting ongoing periodic check intervals.

How do I configure multi-channel alert delivery for different AI agents?▼

Multi-channel alert delivery for different AI agents is configured through per-agent settings that control notification routing and costs. This allows each agent to deliver heartbeat alerts to specific channels based on individual configuration.