Chef Inspec
v1.0.2Chef InSpec integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chef InSpec data.
⭐ 0· 77·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 say Chef InSpec integration and the SKILL.md consistently instructs use of the Membrane CLI to discover connections, list actions, run actions, and proxy API calls to Chef InSpec. Required resources (network + Membrane account) match the stated purpose; there are no unrelated credential or system access requests.
Instruction Scope
Instructions stay within the Chef InSpec use case (install Membrane CLI, login, create/inspect connections, run actions, proxy API calls). One notable capability: the 'membrane request' proxy accepts arbitrary API paths and methods, which legitimately supports advanced use but also increases the power of the skill (it can send arbitrary requests through the connected account). This is expected for a proxy feature but worth awareness.
Install Mechanism
No install spec is embedded; runtime instructions tell the user to install @membranehq/cli via npm (public registry). Using npm is proportional to the described functionality. There are no opaque downloads or extract/install steps from untrusted URLs.
Credentials
The skill does not request environment variables or local credentials and defers auth to Membrane (membrane login / browser-based flows). That matches the guidance in SKILL.md. The primary trust surface is the Membrane service and the connections you create there.
Persistence & Privilege
The skill is user-invocable, not always-enabled, and instruction-only — it does not request persistent elevated privileges or modify other skills/configs. Autonomous invocation is allowed by platform default but not unusually privileged here.
Assessment
This skill is coherent: it tells you to install the official Membrane CLI and use Membrane to manage Chef InSpec connections and API calls. Before installing/using it, consider: (1) you must trust Membrane (it will broker auth and can send proxied API requests on your behalf); (2) NPM global install is required for the CLI—ensure you are comfortable installing that package; (3) prefer using pre-built actions discovered via 'action list' rather than ad-hoc 'membrane request' calls to reduce risk of unintended data access; and (4) when creating connections, verify you are connecting to the correct Chef InSpec account/environment.Like a lobster shell, security has layers — review code before you run it.
latestvk9716rzqg7j89498j3phnbcfm5843z3m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.