Acunetix
v1.0.2Acunetix integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acunetix data.
⭐ 0· 83·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 (Acunetix integration) matches the instructions: all actions are performed via the Membrane CLI which proxies to Acunetix. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, running membrane login/connect/action/request commands, and using Membrane's proxy when necessary. This stays within the stated purpose, but it means API calls and auth flows are routed through Membrane (getmembrane.com), so Acunetix data and authentication are handled by a third-party service rather than direct calls from the agent.
Install Mechanism
There is no platform install spec, but the docs recommend installing @membranehq/cli with npm (global). Installing an npm package is a reasonable, common step but carries the usual supply-chain considerations — users should vet the package and its GitHub source before installing globally.
Credentials
The skill requests no environment variables or local credentials (and explicitly tells users not to provide API keys). However, using Membrane means credentials and request payloads are managed/forwarded by Membrane's service; lack of local secrets is proportionate but requires trusting that external service.
Persistence & Privilege
always is false and the skill is user-invocable; there is no indication it modifies other skills or requests elevated persistent privileges. The agent-level autonomy default applies but is not combined with other risky flags.
Assessment
This skill appears coherent, but note it relies on Membrane as an intermediary. Before installing the recommended CLI: (1) verify and review the @membranehq/cli package and its GitHub repo, (2) confirm your organization is comfortable with Acunetix data and credentials being proxied/managed by Membrane (getmembrane.com), (3) prefer installing locally or in a controlled environment instead of npm -g if you have policy concerns, and (4) never paste secrets into chat — follow the described browser-based connector auth flow. If you need zero third‑party routing, consider using a direct Acunetix integration that accepts API keys you control.Like a lobster shell, security has layers — review code before you run it.
latestvk97fwp9e1nwat5kqgbwwbxn2w1842xdm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.