Richrelevance
v1.0.2RichRelevance (Algonomy) integration. Manage data, records, and automate workflows. Use when the user wants to interact with RichRelevance (Algonomy) data.
⭐ 0· 75·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
Name/description match the instructions: all runtime steps use the Membrane CLI to discover, connect, and proxy requests to RichRelevance (Algonomy). Nothing in the SKILL.md requires unrelated services or credentials.
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying API requests. The document does not instruct reading arbitrary local files, harvesting env vars, or sending data to unexpected third-party endpoints beyond Membrane (the stated proxy).
Install Mechanism
The skill recommends installing @membranehq/cli globally via npm (npm install -g @membranehq/cli). This is a reasonable, traceable package install for a CLI-based integration, but any global npm install runs code from the registry—verify the package's legitimacy before installing and prefer installing in a controlled environment if you are cautious.
Credentials
The skill declares no required env vars, no primary credential, and no config paths. The SKILL.md explicitly instructs users not to supply API keys locally and to let Membrane manage auth, so requested access is proportionate to the described functionality.
Persistence & Privilege
The skill is instruction-only (no code files), does not request always:true, and is user-invokable. It does not instruct modifying other skills or system-wide settings.
Assessment
This skill appears coherent and limited to using Membrane's CLI to interact with RichRelevance. Before installing, verify the @membranehq/cli package on npm/GitHub (publisher, recent activity, integrity), and decide whether you trust Membrane to proxy API requests and hold auth tokens — proxying means request payloads and responses will flow through Membrane's service. If you have sensitive data, review Membrane's privacy/security documentation and consider testing the CLI in an isolated environment (container or VM) first.Like a lobster shell, security has layers — review code before you run it.
latestvk9707pfm2dxrxjgsrnfftm07j5842m63
License
MIT-0
Free to use, modify, and redistribute. No attribution required.