@parad0x_labs/liquefy-openclaw-plugin
v0.2.1
Published
OpenClaw plugin wrapper for Liquefy CLI (scan/apply tools, safe defaults, vault-scan PII gate)
Maintainers
Readme
Liquefy OpenClaw Plugin Wrapper
This package is a Node.js/OpenClaw plugin wrapper for the Liquefy CLI. It exposes
safe OpenClaw tools (liquefy_scan, liquefy_pack_apply) and shells out to the
Liquefy CLI JSON contracts. It is defined with the OpenClaw SDK's defineToolPlugin
(TypeBox parameters + execute) and needs OpenClaw >= 2026.6.1.
liquefy_scan(read-only,--dry-run): the safe defaultliquefy_pack_apply(writes): registered as optional, so it must be allowlisted/liquefy_statuscommand: plugin version, Liquefy CLI compatibility and defaults- JSON contract integration (
liquefy openclaw --json) - ClawHub/OpenClaw skill pack: under
./skills/
Both tools take out (vault output directory); when omitted they use vaultOut from
the plugin config, and fail with missing_out if neither is set.
What it does
- Exposes safe OpenClaw-facing tools with JSON schemas
- Uses Liquefy CLI safe defaults (
--dry-runfor scan path) - Respects policy files / allow / deny / category overrides
- Supports explicit risky override phrase pass-through
Install (OpenClaw users)
1) Install Liquefy CLI locally (source bootstrap)
git clone https://github.com/Parad0x-Labs/openclaw-skills.git && \
cd openclaw-skills && \
./install.sh2) Install plugin in OpenClaw (pinned)
When this package is published, prefer a pinned install:
openclaw plugins install @parad0x_labs/[email protected] --pin
openclaw plugins enable liquefy
openclaw gateway restartPlugin settings go under config in the plugin entry (OpenClaw validates them against
openclaw.plugin.json):
{
"plugins": {
"entries": {
"liquefy": {
"enabled": true,
"config": { "vaultOut": "~/liquefy-vault", "profile": "default" }
}
}
}
}3) First safe run (scan only)
Use the plugin tool liquefy_scan first, or run the CLI directly:
./.venv/bin/python tools/liquefy_openclaw.py --workspace ~/.openclaw --out ./openclaw-vault --jsonRequired local dependency (plugin host)
You need a Liquefy CLI binary or script on the machine running the plugin.
Resolution order:
- plugin config
binaryPath - env var
LIQUEFY_OPENCLAW_BIN liquefyonPATH
The plugin intentionally does not bundle the CLI binary. This keeps the wrapper auditable and lets operators pin/verify their Liquefy install separately.
Security / trust posture
- Safe default is scan-first (
liquefy_scan) - Destructive/apply tool is optional and intended for allowlisting
- Liquefy policy denylist is enforced by default (secrets/configs blocked)
- The wrapper probes
liquefy openclaw --version --jsonand warns when the local Liquefy CLI is older than the plugin-tested minimum - Use pinned plugin versions (
--pin) and verify Liquefy release checksums (SHA256SUMS.txt) - Signed releases are recommended for production rollout (when available)
Local test
cd plugins/openclaw-plugin
npm ci --ignore-scripts # installs typebox and the openclaw peer used by the entry test
npm testPublish (npm)
cd plugins/openclaw-plugin
npm pack
# npm publish --access public # when org/package permissions are readyNotes
- This is a wrapper package. Compression/search/restore logic remains in the Liquefy CLI + Python engines.
- The npm package does not bundle the full Liquefy repo. Stable contract source-of-truth lives in the Liquefy repo under
docs/sdk.mdandschemas/. - ClawHub/OpenClaw skill pack scaffold lives in
./skills/liquefy-openclaw/.
