What problem does it solve? Autonomous agent missions need to know whether they run in an interactive session that goes idle between turns (requiring a heartbeat cron to stay alive) or in a persistent process that runs to completion. This Skill removes the need for callers to pass flags or environment variables by probing the runtime directly and acting on the result. ## Core Features & Use Cases - Runtime Probing: Inspects the tool inventory (including deferred tools via ToolSearch) to determine whether CronCreate is available, treating availability as the interactive-vs-persistent signal. - Automatic Heartbeat Setup: In interactive sessions, invokes the cron skill to schedule a per-minute heartbeat and returns the cron job id to the caller. - Persistent-Mode Sentinel: In persistent processes, returns the sentinel none (persistent process) so the caller records it in the loop file and drives the phase machine to completion without a cron. - Use Case: A rover mission starts up, invokes keepalive once, writes the returned value into the loop file's cron_job_id field, and proceeds—no host-specific configuration or caller-side branching required. ## Quick Start Invoke the keepalive skill at mission startup and write the returned cron job id or sentinel into the loop file's cron_job_id field.
