heartbeat
Skill17 starsChanged 7 months agoMITView on GitHub
Proactive check-in with pre-gathered context. Run automatically via launchd every 30 minutes.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- bradbushSFAI/noltytheir own version, first seen Nov 16, 2026
- BarzinL/barzins-cc-improvementstheir own version, first seen Nov 15, 2026
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- genericService/claude-skillstheir own version, first seen Nov 8, 2026
- naman10parikh/wikimemtheir own version, first seen Nov 8, 2026
- modimihir07/agentic-ostheir own version, first seen Oct 25, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
roronoazoroshao369Skillmemory-compression
Also in 5 projects that use this
KirchliveSkillskill-routing
Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.
Also in 5 projects that use this
sublimotionSkillagent-runtime
Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).
Also in 5 projects that use this
GoZippySkillrepo-scout
Also in 5 projects that use this
- +5 more from naman10parikh
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- frank890417/taiwan-md★ 1.2ksame name
- aaronjmars/aeon★ 794same name
- aeonfun/aeon★ 793same name
- modimihir07/agentic-os★ 209same name
- crisandrews/ClawCode★ 64same name
- reneyuxi0402/claude-cant-sleep★ 43same name
- systemind-team/AICOO-Skills★ 35same name
- aaronjmars/miroshark-aeon★ 20same name
- MiroShark/miroshark-aeon★ 20same name
- naman10parikh/agentgrid★ 9same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- distill-sessionSkill
- humanizerSkill
- memory-updateSkill
- playwright-cliSkill
- promoteSkill
- researchSkill
- search-memorySkill
- self-improveSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
If the channel server is DEAD -> run bash ./bin/start-agent.sh to restart (the watchdog also does this, but belt-and-suspenders)
- Distinctive: line 25
If there are urgent pending items -> send a notification and summarize what needs attention
- Distinctive: line 26
If there are stale uncommitted changes -> suggest committing or stashing
- Distinctive: line 27
If nothing needs attention -> do nothing (don't generate output for the sake of it)
- Very specific: line 32
NEVER call Telegram's getUpdates API via curl — this competes with the bun long-poller and breaks message delivery
- Very specific: line 36
If the channel is flaky, inspect .claude/runtime/watchdog.log, .claude/runtime/incidents/*.log, and the latest …
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proactive heartbeat — gather context first, then reason:
- Gather context (deterministic, no reasoning yet):
bash .claude/scripts/gather-context.sh - Read the output and assess:
- Is the configured channel server alive? If DEAD -> this is critical, notify immediately
- Are there pending/follow-up items with passed or imminent deadlines?
- Are there uncommitted changes that have been sitting for a long time?
- Is disk space running low?
- Are there duplicate claude/tmux processes? (expected: 1 each)
- Any patterns in today's log that suggest an unfinished thread?
- Act based on what you find:
- If the channel server is DEAD -> run
bash ./bin/start-agent.shto restart (the watchdog also does this, but belt-and-suspenders) - If there are urgent pending items -> send a notification and summarize what needs attention
- If there are stale uncommitted changes -> suggest committing or stashing
- If nothing needs attention -> do nothing (don't generate output for the sake of it)
- If the channel server is DEAD -> run
- Only notify if something is actionable. Silent heartbeats are good. Don't be noisy.
Debugging rules
- NEVER call Telegram's
getUpdatesAPI via curl — this competes with the bun long-poller and breaks message delivery - Safe to check:
getWebhookInfo(read-only, no side effects) - Safe to check:
pgrep -f "bun.*server\.ts"(process alive?) - Safe to check:
lsof -i -P | grep bun(network connections?) - If the channel is flaky, inspect
.claude/runtime/watchdog.log,.claude/runtime/incidents/*.log, and the latest.claude/runtime/agent-session-*.logbefore restarting anything
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

