Wallarm
v1.0.0Wallarm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wallarm data.
⭐ 0· 50·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill states it integrates with Wallarm and its runtime instructions consistently use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to the Wallarm API. The declared homepage and repository references align with Membrane.
Instruction Scope
SKILL.md confines itself to installing and using the Membrane CLI, creating a connection to Wallarm via Membrane, listing/running actions, and using 'membrane request' to proxy API calls. It does not instruct reading unrelated files, asking for arbitrary host credentials, or sending data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the skill metadata (instruction-only), but SKILL.md tells users to run 'npm install -g @membranehq/cli'. Installing a global npm package executes third-party code on the host and writes to disk — a reasonable requirement for this integration but worth caution: verify the package name, source, and version before installing, or use 'npx' to reduce persistence.
Credentials
The skill requests no environment variables, no config paths, and relies on Membrane's browser-based authentication flow. It explicitly instructs not to ask users for API keys, which is consistent with the proxy/auth model described.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and is user-invocable. Autonomous invocation is allowed (platform default) but not elevated here.
Assessment
This skill is coherent for integrating Wallarm via Membrane, but before installing anything: 1) Review the @membranehq/cli package on npm/GitHub and prefer running via 'npx' if you don't want a global install. 2) Understand that Membrane acts as a proxy and will see proxied API requests and responses — verify its privacy/terms if your data is sensitive. 3) When performing 'membrane login' you authenticate via browser; no local API keys are requested by the skill. 4) Only use connector IDs from trusted sources and audit any CLI output you paste into commands. If you want further assurance, ask the skill author for a pinned release/version and the package checksum or install instructions for an auditable binary distribution.Like a lobster shell, security has layers — review code before you run it.
latestvk97f3e0y9rqrc533616cpkbxrx84f65m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.