Openclaw Manager
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent OpenClaw deployment helper, but its environment validator can echo malformed secret-file lines and the skill asks for high-impact cloud and credential operations.
Use this skill only after you are ready for it to guide real deployment and cloud-configuration work. Verify the OpenClaw source repo and provider actions, pin versions where possible, and be especially careful with `.env` validation output because malformed lines may reveal secrets.
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.
A typo or unsupported format in a secrets file could cause API keys or tokens to appear in command output, chat transcripts, or logs.
The helper validates files expected to contain credentials, but its JSON output includes the full raw content of malformed lines. Common malformed entries such as `export OPENAI_API_KEY=...` could therefore print secret values.
"required": ["OPENCLAW_GATEWAY_TOKEN"], "require_any": [["OPENAI_API_KEY", "ANTHROPIC_API_KEY"]] ... "malformed_lines": [{"line": line_no, "content": line} for line_no, line in malformed]Redact malformed-line values before printing; report only line numbers and key names. Until fixed, run validation locally and inspect output before sharing it with an agent or support channel.
If followed without review, the workflow could alter cloud secrets, deploy services, or expose an OpenClaw instance publicly.
The skill openly declares high-impact deployment operations. These are aligned with its deployment-management purpose and are paired with security gates, but they can still change real infrastructure and exposure.
privileged_operations:
- provider_secret_writes
- public_network_exposure
- persistent_state_changesRequire an explicit user-approved plan, confirm rollback ownership, and review each provider or public-ingress change before execution.
A user could accidentally deploy an unexpected or changed version of OpenClaw if the source is not verified.
Hosted deployment relies on an external source repository selected during the workflow. That is expected for deployment, but the artifact does not pin a commit, release, or checksum.
Clone the selected OpenClaw source repo.
Use the official repository, pin a trusted release or commit, and record the deployed version in the operations ledger.
Operational details such as providers, environments, integrations, and secret profile names may persist across sessions.
The skill maintains a persistent operations ledger. The schema explicitly tries to avoid secret storage, but the ledger can still retain deployment metadata that future operators or agents may rely on.
Never record secret values. Record profile and key names only.
Keep the ledger in a private project location, do not store secret values in it, and review ledger contents before reusing them as context.