manage-heartbeats

List, enable, disable, and trigger heartbeat runs via dashboard API endpoints.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill manage-heartbeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-heartbeats
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/manage-heartbeats
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill manage-heartbeats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and control existing heartbeats — list them, enable/disable, trigger manual runs, and review run history and costs for proactive agents.

Core Features & Use Cases

  • List all heartbeats with status, interval, last run, and cost
  • Enable or disable heartbeats to manage proactive agents
  • Manually trigger a heartbeat run and inspect recent results
  • View detailed run histories (latest 10 runs) for auditing and cost awareness

Quick Start

Ask Evo to list heartbeats, review their status, and enable, disable, or trigger a manual run as needed.

Frequently Asked Questions about manage-heartbeats

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

FAQPage Schema
How do I monitor proactive agent heartbeats and view their run status?

Monitor proactive agent heartbeats by listing all configured heartbeats to view their status, interval, last run time, and cost. The tool retrieves this data via dashboard backend API endpoints to give you a clear overview of agent run management.

How do I manually trigger a heartbeat run for a proactive agent?

Manually trigger a heartbeat run by sending a request to the specific heartbeat's run API endpoint. This executes an immediate run outside the scheduled interval, allowing you to inspect the latest results and run history for auditing.

Can I enable or disable automated agent runs without deleting the configuration?

Yes, you can enable or disable automated agent runs by patching the heartbeat configuration. This pauses or resumes the proactive agent's execution schedule while preserving the heartbeat settings for future use.

How many run histories can I inspect for heartbeat cost auditing?

You can inspect the latest 10 run histories for each heartbeat to review detailed statuses and costs. This run history data helps you understand execution patterns and manage expenses for proactive agents.

What happens when I delete a heartbeat for a proactive agent?

Deleting a heartbeat removes the proactive agent's automated run schedule and its configuration from the dashboard backend. This action is permanent and stops all future automated and manual runs associated with that heartbeat.