Openclaw Skill Ansible

Operate and secure mesh workflows across gateways, including plugin bootstrap, invite/join auth handshake, resilient routing, capability contract lifecycle,...

This skill is purpose-aligned for a MeshOps control plane, but review these before installing: - Resolve the manifest mismatch: the registry summary says "no required env vars/bins" but metadata.yaml inside the package lists several gates and binaries. Confirm the marketplace metadata matches the packaged metadata. - Treat the gating env vars (OPENCLAW_ALLOW_HIGH_RISK, OPENCLAW_ALLOW_RUN_CMD, OPENCLAW_ALLOW_DEPLOY_SKILL) as safety interlocks — ensure they default to disabled (0) and are only enabled deliberately for vetted tasks. - Confirm OPENCLAW_ALLOWED_CALLERS is set to a small trusted allowlist. If mis-set, remote callers could trigger deploy/run operations. - Audit the deploy-skill workflow: it downloads HTTPS artifacts and extracts them to /opt/openclaw/skills. Although it requires a sha256 and https, validate the artifact sources and verify the SHA before enabling deployment in production. - Review automatic behavior in SKILL.md: the design requires skills to auto-register capabilities and for executors to auto-claim tasks at reasoning start. If you do not want agents to autonomously claim/execute mesh tasks, do not load this skill into agents that must remain passive. - Test in an isolated environment first: verify preflight, allowlists, artifact root behavior, and that run-cmd only permits the exact commands you expect. If you want, I can list the exact lines/scripts that perform downloads, extractions, command execution, and automatic registration to make your audit easier.

Type: OpenClaw Skill Name: openclaw-skill-ansible Version: 0.1.6 The bundle implements a distributed coordination mesh with high-risk administrative capabilities, specifically remote command execution (run-cmd.sh) and remote skill deployment (deploy-skill.sh). While these actions are protected by multi-layered security gates—including environment variable toggles (OPENCLAW_ALLOW_HIGH_RISK), caller allowlists in src/handler.py, and SHA256 integrity checks for remote artifacts—the inherent capability to download and execute code or run shell commands across a mesh of gateways is high-risk. The documentation (SKILL.md and docs/) outlines a legitimate 'MeshOps' purpose with a 'Ring of Trust' governance model, suggesting these features are intended for orchestration rather than malice, but the potential for abuse remains significant.