Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Activate "Sport Mode" for high-frequency monitoring (default 3m heartbeat) and auto-cleanup. Use when supervising intense tasks (Codex, builds, migrations).
Activate "Sport Mode" for high-frequency monitoring (default 3m heartbeat) and auto-cleanup. Use when supervising intense tasks (Codex, builds, migrations).
This item is timing out or returning errors right now. Review the source page and try again later.
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required. Then review README.md for any prerequisites, environment setup, or post-install checks.
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need. Then review README.md for any prerequisites, environment setup, or post-install checks.
Temporarily boost heartbeat frequency (default 3m) and inject a monitoring task into HEARTBEAT.md. Perfect for supervising background agents (Codex), long-running builds, or interactive games.
# Turn ON: Set heartbeat to 3m and set monitoring task sport-mode on --task "Check Codex progress. If done, run sport-mode off." # Custom Interval: Set to 1 minute sport-mode on --task "Game tick" --every "1m" # Turn OFF: Reset heartbeat to 30m and clear HEARTBEAT.md sport-mode off
ON: Patches ~/.openclaw/openclaw.json (hot-reload) to set heartbeat.every. Writes your task to HEARTBEAT.md with a "Sport Mode Active" header. OFF: Patches config back to 30m (default). Clears HEARTBEAT.md.
Unless you want an endless marathon, always define a termination condition in your task. โ Good: "Monitor build. If success or fail, run sport-mode off." โ Bad: "Monitor build." (Agent might keep reporting "Done" forever until you manually stop it).
For multi-step tasks (like games or staged deployments), let the agent update HEARTBEAT.md itself. Pattern: Read state -> Execute step -> Write new state -> Sleep. This keeps the agent "stateless" (doesn't rely on conversation history context window) but the task "stateful".
If the monitoring task involves terminal output (e.g., Codex coding, compiling), running the task in a tmux session is ideal. The agent can inspect the pane (tmux capture-pane) without interfering. The user can attach (tmux attach) to watch live.
For high-frequency modes (e.g., 1m), avoid spamming "Nothing happened". Configure the agent to reply HEARTBEAT_OK (silence) if the status hasn't changed. Only notify the user on milestone completion, errors, or final success.
This skill uses openclaw config set to safely patch configuration at runtime, triggering a seamless Gateway reload.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.