Radar
v1.0.2Radar integration. Manage Organizations. Use when the user wants to interact with Radar data.
⭐ 0· 99·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
medium confidencePurpose & Capability
The skill is an instruction-only Radar integration that delegates auth and API calls to the Membrane CLI—this matches the described purpose. Minor mismatch: the skill instructs installing an npm package globally but the registry metadata lists no required binaries (node/npm), so the SKILL.md assumes tools that aren't declared.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests to the Radar API via Membrane. The guide explicitly says not to ask users for Radar API keys and to let Membrane handle credentials; it does not instruct reading unrelated files or environment variables.
Install Mechanism
No formal install spec is provided in the registry (skill is instruction-only), but the SKILL.md recommends 'npm install -g @membranehq/cli' (a package from npm). Using npm is a common path but implies Node/npm must be present and a global install may require elevated privileges—this is a modest operational/administrative concern, not an incoherence.
Credentials
The skill declares no required environment variables or credentials and the instructions rely on Membrane to manage auth. There are no requests for unrelated secrets or credentials.
Persistence & Privilege
The skill does not request always: true and has no install-time persistence. Autonomous invocation is allowed (platform default); that is expected for a usable integration but users should be aware the agent could call the Membrane CLI when permitted.
Assessment
This skill appears to do what it claims: it uses the Membrane CLI to access Radar. Before installing or using it: (1) confirm you trust the Membrane service and the CLI package (@membranehq/cli) because the CLI will hold/mediate your connections and credentials; (2) note that SKILL.md assumes node/npm are available—global npm installs can require elevated privileges, so prefer using npx or a per-user install if you don't want to modify the system; (3) review and verify the Membrane account login flow and any permissions granted during connection setup; (4) be cautious with autonomous agents that can run the CLI and make proxied API calls—ensure the agent's scope and prompts are restricted to avoid unintended data access or exfiltration. If you want higher confidence, ask the author for an explicit list of required binaries (node, npm) and a verified package/release URL for the CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk97bs170msjfqv6df8mk9ssfzn842gag
License
MIT-0
Free to use, modify, and redistribute. No attribution required.