HZL

PassAudited by ClawScan on May 1, 2026.

Overview

HZL is a coherent task-ledger skill, but it installs an external CLI and persists task/checkpoint data that may be shared across agents.

Use this skill if you want an external local task-ledger CLI for resumable or multi-agent work. Keep task descriptions and checkpoints non-sensitive, scope shared projects carefully, and do not use force/prune deletion commands unless you explicitly intend to delete HZL data.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If misused, force or prune commands could permanently delete HZL task history.

Why it was flagged

The CLI includes destructive operations that can erase ledger data, but the skill explicitly labels them as destructive and instructs agents not to run them unless the user asks.

Skill content
`hzl init --force --yes` | **DELETES ALL DATA WITHOUT CONFIRMATION.**
Recommendation

Only allow destructive HZL commands when you intentionally want to delete ledger data, and avoid `--yes` unless you are sure.

What this means

Installing the skill requires trusting the Homebrew or npm package that provides the `hzl` command.

Why it was flagged

The skill relies on installing an external CLI package rather than shipping reviewable code in the artifact set. This is normal for a CLI skill but still means the installed package should be trusted.

Skill content
`brew` | package: `hzl` | creates binaries: `hzl`; `node` | package: `hzl-cli` | creates binaries: `hzl`
Recommendation

Install from the documented package source only if you trust the HZL project and your package manager configuration.

What this means

Future agents may read and act on stored HZL task/checkpoint information.

Why it was flagged

The skill intentionally stores task progress for later reuse. Persistent task/checkpoint content can influence future sessions or agents if it contains sensitive data, stale assumptions, or untrusted instructions.

Skill content
Checkpoint progress so work survives session boundaries
Recommendation

Do not put secrets in HZL tasks or checkpoints, and review stored task state before relying on it for important actions.

What this means

Agents using the same HZL projects may see, claim, or recover work from shared task queues.

Why it was flagged

The skill supports shared project pools, leases, claims, and task stealing for multi-agent coordination. That is purpose-aligned, but shared task pools can expose task context to other participating agents.

Skill content
Coordinate across multiple agents with leases and dependencies
Recommendation

Use separate projects or clear agent IDs for sensitive work, and keep shared tasks limited to information the participating agents should see.