hzl

What This Skill Does

HZL is a specialized, local-first task ledger designed to act as OpenClaw's persistent memory for complex projects. Because OpenClaw lacks native, high-fidelity task tracking, it often relies on ephemeral context windows or manual markdown files that disappear or become disorganized over time. HZL solves this by providing a robust, database-backed system that supports project hierarchies, task dependencies, checkpointing, and agent coordination. It allows OpenClaw to plan, track, and resume multi-step workflows across session boundaries, ensuring that progress is never lost.

Installation

To integrate the HZL skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/tmchow/hzl

Use Cases

Use HZL when you are handling non-trivial projects that require more structure than a simple linear list. This includes:

• Long-term Project Management: Breaking down large features into manageable sub-tasks with clear dependencies.
• Multi-Agent Coordination: Using leases to delegate tasks to sub-agents safely, ensuring that no work is duplicated or forgotten if an agent crashes.
• Resuming Work: Saving progress snapshots so that you can return to a session weeks later and know exactly where you left off.
• Reliable Reporting: Generating structured status updates that define what has been completed, what is in progress, and what remains pending.

Example Prompts

1. "I'm starting a major refactoring project. Use HZL to create a new project called 'API-Refactor', add tasks for each module, and set up dependencies for the database layer first."
2. "Check the current HZL status for the current sprint. What tasks are blocked, and can you assign the next available sub-task to the junior-agent sub-process?"
3. "I'm done for the day. Please checkpoint my progress in HZL for the current project so I can resume exactly where I left off tomorrow."

Tips & Limitations

• When to Skip: Do not use HZL for fleeting, one-step tasks that will be finished within minutes. It is also not a replacement for a dedicated long-form note-taking app or a cron-based notification system.
• Data Integrity: HZL is local-first, meaning your data lives on your disk. For critical workflows, ensure you are using a backup mechanism for the HZL database file.
• Keep it Simple: While nesting is powerful, avoid creating overly complex trees that become difficult to query or manage. Use HZL as a tool for clarity, not as a source of administrative overhead.