← Back to Skills Marketplace
2431
Downloads
0
Stars
6
Active Installs
5
Versions
Install in OpenClaw
/install openclaw-deploy
Description
Build and deploy OpenClaw as Docker images or portable packages. Package OpenClaw with or without personal configuration for easy deployment to other servers.
Usage Guidance
This skill appears to be a legitimate packaging/deployment tool, but review and test before using on real data. Specific recommendations:
- Inspect the scripts (build-portable.sh, export-portable.sh, start.sh) yourself; do not run them until reviewed.
- Be aware: the 'full' package copies your OpenClaw config directory (~/.openclaw by default). That directory frequently contains API keys, gateway tokens, and other secrets — sanitize or back up separately if you don't want those included.
- The export script contains a broken heredoc/redirection that may fail to create the expected deploy.sh/README files; test in a disposable environment first.
- The start scripts use developer-specific hardcoded paths (/home/zfanmy/...), which may create unexpected directories on your host; adjust those paths before running.
- Prefer to run these scripts in an isolated VM/container or with copies of your install/config to verify behavior.
- If you intend to deploy remotely, review any deploy scripts for scp/ssh behavior and ensure they won't leak packages to untrusted hosts. If you need help auditing specific files or sanitizing configs, provide which files/paths you plan to package and I can point out what to remove.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-deploy
Version: 1.0.4
The skill is classified as suspicious due to the use of `curl -o- ... | bash` in `templates/install-node.sh` for NVM installation, which is a risky pattern for executing remote code and represents a supply chain vulnerability. Additionally, hardcoded paths like `/home/zfanmy/openclaw_data/workspace` in `scripts/start.sh` and specific NVM paths in `scripts/build-portable.sh` and `templates/start-*.sh` introduce vulnerabilities related to environment assumptions and potential permission issues. While the skill's primary purpose is deployment and backup, these practices introduce significant security risks without clear malicious intent.
Capability Assessment
Purpose & Capability
The skill's stated purpose (build/package/deploy OpenClaw) aligns with the included scripts which copy the application and config directories and create tarballs. However there are developer-specific hardcoded paths (e.g., /home/zfanmy/...) and references in documentation to including 'DreamMoon 配置' and gateway/channel tokens — these are expected for a migration/backup tool but should be explicit to users because sensitive tokens may be packaged.
Instruction Scope
Runtime scripts read and copy the user's OpenClaw installation and configuration directories (OPENCLAW_INSTALL_DIR, OPENCLAW_CONFIG_DIR, defaulting to user home paths). That means private credentials or tokens stored in the config could be packaged and transferred. The SKILL.md and scripts also reference deploy.sh and export/deploy.sh behavior; some expected files (deploy.sh) are not present in the repository but export-portable.sh attempts to create one — that creation contains a malformed redirection which will likely break and produce unexpected output/errors.
Install Mechanism
This is instruction-only with embedded scripts (no install spec, no downloads). Nothing is fetched from external URLs during installation; scripts run locally. From an install mechanism perspective this is low risk, but running the scripts will perform filesystem operations so they should be inspected before execution.
Credentials
The skill declares no required credentials, but the scripts will copy the entire OpenClaw install directory and (optionally) the user's config directory into output packages. Those config files can contain API keys, gateway tokens, channel tokens, and other secrets (README even mentions 飞书、网关 token). Requesting no env vars but acting on user config is proportionate for migration, but it is a sensitive action that should be signposted and optional; the current scripts default to including full config for the 'full' package.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or global agent settings. It will create local directories and output tarballs when run, and some scripts create/expect directories under a developer path (/home/zfanmy), which is awkward but not a privilege escalation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-deploy - After installation, invoke the skill by name or use
/openclaw-deploy - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
v1.0.4
- No file changes detected in this release.
v1.0.3
## openclaw-deploy v1.0.3
- No file changes detected in this release.
v1.0.2
- Added templates for deployment scripts and documentation, including README and utility shell scripts.
- Introduced environment variable support for customizable installation and output paths.
- Improved error handling and dependency checks in build and export scripts.
- Updated documentation with instructions for custom paths and detailed usage.
- Fixed hardcoded paths and added path validation.
v1.0.1
- Added SKILL.md metadata in standard format, including license, homepage, and required binaries.
- Updated directory name in documentation from "openclaw_docker" to "openclaw-deploy."
- The "keywords" field was restructured for better clarity.
- Introduced a "requires" section listing required command-line binaries.
v1.0.0
openclaw-deploy 1.0.0 initial release:
- Build and deploy OpenClaw as Docker images or portable packages.
- Package OpenClaw with or without personal configuration for easy migration.
- One-command remote deployment support.
- Provides scripts for building, exporting, and deploying packages.
- Backup and restore configuration functionality included.
Metadata
Frequently Asked Questions
What is Openclaw Deploy?
Build and deploy OpenClaw as Docker images or portable packages. Package OpenClaw with or without personal configuration for easy deployment to other servers. It is an AI Agent Skill for Claude Code / OpenClaw, with 2431 downloads so far.
How do I install Openclaw Deploy?
Run "/install openclaw-deploy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openclaw Deploy free?
Yes, Openclaw Deploy is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Openclaw Deploy support?
Openclaw Deploy is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Openclaw Deploy?
It is built and maintained by zfanmy (@zfanmy); the current version is v1.0.4.
More Skills