update-heartbeat

Update OpenClaw heartbeat configuration files and monitoring checklists.

4|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/marcel-heinz/clawcity.app --skill update-heartbeat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-heartbeat
Source: https://github.com/marcel-heinz/clawcity.app/tree/main/.claude/skills/update-heartbeat
Command: npx skills add https://github.com/marcel-heinz/clawcity.app --skill update-heartbeat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains the OpenClaw heartbeat configuration and monitoring checklist for ClawCity. Run this agent when game mechanics change that affect what agents should monitor.

Core Features & Use Cases

  • Centralizes heartbeat syncing across HEARTBEAT.md, public/heartbeat.md, and gateway heartbeat files to ensure consistency.
  • Automates updates to thresholds and checks when game logic evolves, reducing drift.
  • Provides a governance trail by keeping the skill state in sync with doc changes for auditability.

Quick Start

Trigger the heartbeat update process by scanning, analyzing, updating, and validating all related files.

Frequently Asked Questions about update-heartbeat

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

FAQPage Schema
How do I sync heartbeat configuration files when game mechanics change?

Sync heartbeat configuration by scanning, analyzing, updating, and validating HEARTBEAT.md, public/heartbeat.md, gateway heartbeat, and skill configuration files to ensure consistency when game mechanics evolve.

What is an OpenClaw heartbeat monitoring checklist used for?

An OpenClaw heartbeat monitoring checklist defines what agents should monitor in ClawCity, ensuring thresholds and checks stay aligned with current game mechanics for reliable monitoring workflows.

How do I automate heartbeat threshold updates across multiple configuration files?

Automate heartbeat threshold updates by coordinating file reads, analysis, and validation across HEARTBEAT.md, public/heartbeat.md, and gateway heartbeat files to reduce configuration drift and maintain consistency.

Why does my heartbeat configuration drift after updating game logic?

Heartbeat configuration drifts when game logic changes are not propagated across all monitoring files. Centralized syncing across HEARTBEAT.md, public/heartbeat.md, and skill state prevents this inconsistency.

Can I maintain a governance trail when updating heartbeat documentation?

Maintain a governance trail by keeping skill state in sync with heartbeat documentation changes, providing auditability across HEARTBEAT.md and public/heartbeat.md updates when game mechanics change.

When should I trigger a heartbeat configuration update for ClawCity agents?

Trigger a heartbeat configuration update whenever game mechanics change in ways that affect what agents should monitor, requiring coordinated updates across heartbeat files and skill configuration for validation.