Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/loop-heartbeat
Scheduled discovery automation that runs scans on a heartbeat interval, classifies findings, and routes them to goals or triage inbox.
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
and 16 more in the full report
14 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our recurring scan file, we want to cap overall scanning spending at $2.00 per hour. What key path and structure under the budget block configures this limit?
| Checked | Without skill | With skill |
|---|---|---|
| Configures maxDollarsPerHour set to 2.0 under budget | Missed | Passed |
The instructions your model reads when the skill loads.
Scheduled discovery automation that runs scans, finds issues, and routes findings to goals or triage. The heartbeat is what makes a loop a loop — not a one-shot run.
Based on Addy Osmani's Loop Engineering: "Automations are the thing that makes a loop an actual loop. Run prompts on a schedule. Findings go to a triage inbox; empty runs archive themselves."
/heartbeat start to begin scheduled scans/heartbeat run for a one-shot scanThe heartbeat is the "discovery layer" of a loop. It answers: "What's broken right now?" on a recurring basis without human prompting.
Every 30 minutes:
┌─ Run test suite ─── PASS → skip
├─ Run linter ─────── FAIL → create goal (auto-fix)
├─ Audit deps ─────── FAIL → triage inbox (human decision)
└─ Type check ─────── PASS → skip
Create .claude/heartbeat.yaml in the project root:
heartbeat:
interval: "30m"
scans:
- name: "test-health"
command: "npm test 2>&1 | tail -10"
onFailure: "auto-goal"
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.