OpenClaw Flow Kit

Fix common OpenClaw workflow bottlenecks: platform engage-gates/429 backoff helpers (starting with MoltX), standardized JSON result envelopes for chaining scripts, workspace path resolution helpers, and a simple skill release conductor (prepare/publish/draft announcements).

This skill appears to do what it says, but review and take these precautions before using it: - The 'publish' command runs the 'clawdhub' CLI via subprocess — ensure you have that CLI installed and trust it; the skill metadata does not list this binary as a requirement. - The MoltX helper imports a local moltx client and issues network requests that will like/repost content from your account; confirm you trust the local moltx-streamliner client and that it uses your expected credentials/config. - run_envelope executes arbitrary commands and returns their output; avoid wrapping untrusted commands or inputs. - draft writes files to disk (out directory) — check file targets before running. - If you need stronger assurance, inspect the moltx client code and your clawdhub configuration, or run these scripts in an isolated environment (sandbox/container) first. Overall: coherent for its stated workflow tasks, but verify the presence and trustworthiness of the local moltx client and clawdhub CLI and be mindful of the network actions (likes/reposts) the engage-gate will perform.

Type: OpenClaw Skill Name: openclaw-flow-kit Version: 1.0.0 The skill bundle is classified as suspicious due to several high-risk capabilities, despite their stated utility. The `scripts/run_envelope.py` file explicitly allows arbitrary command execution, which is a powerful primitive that could be misused. Additionally, `scripts/moltx_engage_gate.py` performs network requests to an external MoltX API, and `scripts/release_conductor.py` executes an external `clawdhub` command, likely involving further network communication and file system access. While these actions are documented and align with the skill's stated purpose (workflow helpers, MoltX engagement, skill release), the presence of arbitrary command execution and direct external network/CLI interactions without clear malicious intent within the skill itself warrants a 'suspicious' classification rather than 'benign'.