Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Docs safety hardening: add SECURITY.md; clarify heartbeat full-refresh reads include memory; note Telegram logging is optional.
What This Skill Does
Templates and docs for building a deterministic orchestration loop in OpenClaw, covering heartbeat tracking, an activities queue, sprint planning, and cron poll payloads. Completion requires artifact path evidence so tasks cannot be marked done without proof. The skill installs nothing and makes no config changes automatically.
Enforces artifact-path evidence before marking tasks done, preventing silent completion failures common in self-reporting agent loops.
When to use it
- Setting up a repeatable agent orchestration loop in OpenClaw
- Tracking active tasks with a lean portfolio queue
- Importing a project plan into a structured sprint
- Enforcing evidence-gated task completion for agent workflows
- Configuring cron-based heartbeat polling for long-running jobs
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Set up a deterministic controller for my OpenClaw workspace
- 1Copy HEARTBEAT.md, ACTIVITIES.md, and SPRINT_TEMPLATE.md into the workspace
- 2Set <TELEGRAM_GROUP_ID> placeholder in HEARTBEAT.md
- 3Add heartbeat prompt and cadence to openclaw.json using the provided config snippets
- 4Run setup_prompt.md to initialize the sprint from a project plan
- 5Paste poll_cron_payload.txt into the cron scheduler to activate polling
OpenClaw workspace configured with a deterministic heartbeat loop, activities queue, and evidence-gated sprint tracker
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.