Ansible
v1.0.2Ansible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ansible data.
⭐ 0· 103·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description indicate an Ansible integration and the SKILL.md exclusively instructs the agent to use the Membrane CLI to connect to Ansible, discover actions, run actions, or proxy HTTP requests — these requirements are coherent for an Ansible integration.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in via browser, creating/listing connections, discovering and running actions, and proxying requests to Ansible. The instructions do not ask the agent to read unrelated filesystem paths or environment variables or to transmit data to unexpected endpoints outside Membrane/Ansible.
Install Mechanism
This is an instruction-only skill (no files executed by the platform). It tells users to install @membranehq/cli via npm (global install or npx). Installing a global npm package is a normal step but carries the usual supply-chain risk; the skill itself does not bundle or fetch arbitrary code.
Credentials
The skill declares no required env vars or credentials. It explicitly delegates auth to Membrane (so users do not provide API keys directly). That delegation is reasonable for the stated purpose, but it does mean Membrane will hold/manage Ansible credentials on the user's behalf.
Persistence & Privilege
The skill does not request persistent privileges (always is false) and does not modify other skills or system-wide settings. It relies on a CLI the user explicitly installs and invokes.
Assessment
This skill appears internally consistent, but before installing: (1) Review the @membranehq/cli npm package (author, version, and npmjs listing or GitHub repo) because a global npm install can run arbitrary code; (2) Understand that Membrane will manage and see your Ansible credentials and proxied API traffic — confirm you trust Membrane's account/service and review its access scope; (3) Prefer using least-privilege Ansible credentials when creating the connection; and (4) If you need higher assurance, validate the Membrane CLI source code or use a dedicated service account with limited permissions.Like a lobster shell, security has layers — review code before you run it.
latestvk97egwk88d9ecpa6zh1eb0gh55842d17
License
MIT-0
Free to use, modify, and redistribute. No attribution required.