Skills/ClawHub/openclaw-skill-ansible

openclaw-skill-ansible@0.1.6

VERIFIED· install only

Publisher claims: "Operate and secure mesh workflows across gateways, including plugin bootstrap, invite/join auth handshake, resilient routing, capability contract lifecycle,..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher likesjx · publishing for 259 daysInstalls 1,531Last detonated 1 h ago
$clawhub install openclaw-skill-ansible
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 9 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.0sprocessexited 1: ./scripts/package_skill.sh: line 3: $1: unbound variable
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.0sprocessexited 1: ./scripts/promote_skill.sh: line 3: $1: unbound variable
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexec /usr/bin/tee
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ./actions/collect-logs.sh: line 4: $1: unbound variable
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ./actions/deploy-skill.sh: line 4: $1: unbound variable
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ./actions/preflight.sh: line 4: $1: unbound variable
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ./actions/run-cmd.sh: line 4: $1: unbound variable
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ./actions/setup-ansible-plugin.sh: line 4: $1: unbound variable
0.2sprocess8 of 9 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.2sprocessscript backend runs setup only
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedsrc/handler.py:60 · Python subprocess execution detectedresult = subprocess.run(["/bin/bash", str(script), task_path], check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 2,105 lines in 21 files.

Cost to the agent

Instructions loaded
≈2,164 tok
2 files · 21 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.