Publish OpenClaw skills or plugins to npm and ClawHub with a guarded workflow. Use this whenever the user asks to release, publish, ship, or republish a skil...
Security Analysis
high confidenceThe skill's code, instructions, and requirements are coherent with its stated purpose (guarded publishing to npm and ClawHub); no disproportionate credential access, unexpected network exfiltration, or risky install behavior is present.
The skill is designed to prepare a temporary release directory, run local checks, and guide explicit npm / clawhub publish steps; the included scripts (release_guard.py + pattern rules) match that purpose. Minor metadata inconsistency: SKILL.md lists required tools (python3, git, clawhub, curl and implicitly npm) but the registry metadata declares no required binaries — this is a documentation/metadata mismatch but doesn't indicate hidden behavior.
SKILL.md instructs only repository-local actions (reading references, running scripts, preparing a temp release dir, and executing explicit npm/clawhub commands). The release_guard.py implementation performs file scanning, git calls, and selective copying; it does not perform network calls or request external endpoints. The instructions emphasize keeping real accounts in a local (gitignored) config file and not uploading secrets.
There is no install spec (instruction-only skill) and all code files are bundled in the skill. No remote downloads or archive extraction are performed by an install step, so the install risk is low.
The skill requests no environment variables or primary credentials and relies on a local config (config/publish.accounts.local.json) which the docs require to be gitignored. That is proportionate to a publishing helper. Note: the skill will call local CLIs (clawhub, npm, git) at runtime per instructions, so those tools and any credentials they use remain the user's responsibility.
The skill is user-invocable, not forced-always, and does not request persistent system-wide privileges or modify other skills. It performs only repository-local checks and copies into a temporary release directory.
Guidance
This skill is coherent for preparing and validating npm/ClawHub releases, but check these before using it: 1) Confirm your environment provides python3, git, npm, clawhub, and curl (SKILL.md lists them — metadata omitted them). 2) Create config/publish.accounts.local.json from the example and ensure it's in .gitignore; never commit it. 3) Inspect scripts/release_guard.py outputs (run with a safe repo copy and the --prepare-release-dir dry-run if available) — it uses subprocess to run git and copies files into a temp dir, but does not perform network calls itself. 4) When you run publishing steps (npm publish, clawhub publish) you will invoke CLIs that may use/require credentials; ensure those credentials are handled locally and not uploaded. 5) If you are concerned about sensitive files in the repo, run the release guard on a disposable clone first and review the list of files it plans to include/exclude. Overall the skill appears to do what it claims; pay attention to the small documentation/metadata mismatch about required tools and to safe handling of your local publish account file.
Latest Release
v1.0.6
Document ClawHub scan learnings and strengthen release_guard structural checks.
More by @humanlike2026
Published by @humanlike2026 on ClawHub
