agentleFS
koteitankoteitan/my-skills/skills/heart-beat/SKILL.md

heart-beat

Skill1 starsChanged 3 months agoMITView on GitHub

Keep working autonomously until the proof is complete, with a CronCreate heartbeat that wakes the session whenever it has been idle for X minutes. Use when the user says "heart-beat X分" / "heart-beat Xm" (X is a number of minutes).

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not end a turn at an X-minute boundary.

    line 19
  2. Distinctive:

    Start (or resume) the work on the proof right away, in the same turn.

    line 31
  3. Very specific:

    Use the offset minute M = min(3, 59 mod X).

    line 35
  4. Distinctive:

    If the only thing left is waiting for background agents or builds you started, check their status, do any other useful work, and end the …

    line 65
  5. Very specific:

    If you are blocked on input only the user can give, say the blocker in one sentence and CronDelete the heartbeat, so it does not fire in …

    line 68
  6. Very specific:

    Verify it (the project's proof checker passes, no sorry / oops / admitted steps remain).

    line 73
  7. Very specific:

    If the user says to stop the heart-beat, CronDelete the job and say so in one line.

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

heart-beat

The user says heart-beat X分 (or heart-beat Xm). Treat it as this instruction:

Set a heartbeat with CronCreate every X minutes and work autonomously until the proof is complete. X is not a work slice. X is the longest time the session may stay idle. Keep working continuously for as long as the work takes.

Meaning of X

  • X = the maximum idle time. It is not "work X minutes, then stop".
  • Cron jobs fire only while the REPL is idle. So the heartbeat never interrupts work. It only wakes the session after a turn has ended.
  • Do not end a turn at an X-minute boundary. Do not split the work into X-minute pieces. Keep working until the proof is complete.

Steps

  1. ToolSearch("select:CronCreate,CronList,CronDelete") to load the cron tools.
  2. CronList. Delete any earlier job whose prompt starts with [heart-beat], so only one heartbeat exists.
  3. CronCreate with recurring: true, the cron below, and the prompt below. Remember the returned job ID.
  4. Say in one line: the job ID, the interval, and that recurring jobs expire after 7 days.
  5. Start (or resume) the work on the proof right away, in the same turn.

Cron expression

Use the offset minute M = min(3, 59 mod X). It avoids the :00 rush, and it keeps every gap ≤ X, also across the hour boundary (the gap there is 60 - X·floor((59-M)/X), which is ≤ X only when M ≤ 59 mod X).

Xcronnote
1* * * * *
2–59M-59/X * * * *
603 * * * *
multiple of 60, = 60·H3 */H * * *
other X > 60round down to a multiple of 60say so to the user

Example: X = 10 → 3-59/10 * * * * (fires at :03, :13, …, :53).

Heartbeat prompt

Pass this as prompt (fill in X):

[heart-beat] Heartbeat (X min). You have been idle. Resume autonomous work
toward completing the proof: check where you left off (todo list, files,
build/check results, background agents) and continue. Work continuously; X is
the maximum idle time, not a work slice. When the proof is complete, delete
this heart-beat job with CronDelete and give a final recap.

When a heartbeat fires

  • Find the current state and continue the work. Do not only reply "still working".
  • If the only thing left is waiting for background agents or builds you started, check their status, do any other useful work, and end the turn with one short line. The next heartbeat will check again.
  • If you are blocked on input only the user can give, say the blocker in one sentence and CronDelete the heartbeat, so it does not fire in vain.

When the proof is complete

  1. Verify it (the project's proof checker passes, no sorry / oops / admitted steps remain).
  2. CronDelete the heartbeat job.
  3. Give a recap: what was proved, what changed, what is next.

Stopping early

If the user says to stop the heart-beat, CronDelete the job and say so in one line.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.