openclaw-heartbeat

Monitor system and service health with scheduled checks in OpenClaw.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/ollieb89/openrepo --skill openclaw-heartbeat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-heartbeat
Source: https://github.com/ollieb89/openrepo/tree/main/skills/openclaw-heartbeat
Command: npx skills add https://github.com/ollieb89/openrepo --skill openclaw-heartbeat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of periodically checking the health and status of various systems and services, ensuring that the OpenClaw agent is functioning optimally and alerting to potential issues proactively.

Core Features & Use Cases

  • Scheduled Monitoring: Configures and executes recurring checks for email, calendar, system health, and other critical services.
  • Batching Operations: Consolidates multiple checks into a single operational turn, reducing redundant API calls and improving efficiency.
  • Quiet Hours Enforcement: Implements user-defined quiet hours to prevent non-urgent notifications during sensitive times.
  • State Management: Tracks the last checked times and pending alerts to manage heartbeat status effectively.
  • Use Case: Set up daily checks for urgent emails, upcoming calendar events, and the status of key servers, with notifications only sent if critical issues are detected or during specified active hours.

Quick Start

Configure the heartbeat skill to check unread email and upcoming calendar events every 30 minutes.

Frequently Asked Questions about openclaw-heartbeat

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

FAQPage Schema
How do I automate periodic agent health checks and system monitoring?

Automate periodic agent health checks by configuring scheduled tasks in a HEARTBEAT.md file, which defines recurring monitoring operations for email, calendar, and system status services.

Can I schedule system status and email monitoring checks to run on a recurring basis?

Yes, you can schedule recurring system status and email monitoring checks by defining the tasks and intervals in the HEARTBEAT.md configuration file.

How does state persistence work for scheduled monitoring tasks?

State persistence for scheduled monitoring tasks works by tracking last checked times and pending alerts in a memory/heartbeat-state.json file to manage heartbeat status effectively.

What is the best way to prevent non-urgent notifications during quiet hours?

Prevent non-urgent notifications during quiet hours by implementing user-defined quiet hours enforcement, which stops alerts for scheduled monitoring tasks during sensitive times.

How do I reduce redundant API calls when running multiple agent monitoring tasks?

Reduce redundant API calls by batching multiple agent monitoring operations into a single operational turn, consolidating checks to improve overall system efficiency.