heartbeat-execution

Name: heartbeat-execution
Availability: InStock
Author: spiral-app-labs

Orchestrate heartbeat polling and task execution within a constrained API budget.

Updated Apr 8, 2026

Search Tags:#automation #logging #orchestration #task-management #sub-agent #heartbeat #api-budget

Ready to run

npx skills add https://github.com/spiral-app-labs/skills --skill heartbeat-execution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heartbeat-execution
Source: https://github.com/spiral-app-labs/skills/tree/main/heartbeat-execution
Command: npx skills add https://github.com/spiral-app-labs/skills --skill heartbeat-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates heartbeat polling within a strict API budget to ensure timely task evaluation and reporting without exceeding call limits.

Core Features & Use Cases

Budget-controlled task selection: fetches and runs up to a capped number of unblocked tasks per cycle.
Audit-friendly logging: records agent activity and generates a heartbeat summary artifact.
Deterministic execution with sub-agents: delegates heavy builds to sub-agents while preserving guardrails.
Artifact governance: mandates artifact generation (commit, spec, review, memory update) per heartbeat.

Quick Start

Run a heartbeat cycle using the default board and budget thresholds to start processing.

Frequently Asked Questions about heartbeat-execution

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

FAQPage Schema

How do I prevent my autonomous agent cycles from exceeding API rate limits?▼

Orchestrating heartbeat polling within a strict API budget prevents overuse by capping the number of unblocked tasks fetched and executed per cycle. This ensures timely task evaluation without exceeding call limits.

What is the best way to manage task selection and logging for autonomous agents?▼

Budget-controlled task selection fetches and runs up to a capped number of unblocked tasks per heartbeat cycle, generating audit-friendly logs and a heartbeat summary artifact to track all agent activity.

How do I delegate heavy builds to sub-agents without losing execution guardrails?▼

Deterministic execution with sub-agents delegates heavy builds to sub-agents while preserving strict guardrails, ensuring outcomes remain controlled and within the established API budget.

Does heartbeat execution require artifact generation for every task cycle?▼

Yes, artifact governance mandates artifact generation, such as a commit, spec, review, or memory update, for every heartbeat cycle to maintain strict auditability and execution tracking.

Can I run heartbeat polling on assigned boards using default budget thresholds?▼

Yes, you can run a heartbeat cycle using the default board and budget thresholds to immediately start processing unblocked tasks within the constrained API budget.

Why does my heartbeat run stop picking new tasks before the queue is empty?▼

Heartbeat runs stop picking new tasks once the strict API budget cap for that cycle is reached, preventing overuse and ensuring task evaluation stays within constrained call limits.