Cufinder
v1.0.2CUFinder integration. Manage data, records, and automate workflows. Use when the user wants to interact with CUFinder data.
⭐ 0· 92·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 (CUFinder integration) match the runtime instructions: install/use the Membrane CLI, create a CUFinder connection, list/run actions, or proxy requests. There are no requests for unrelated services or secrets.
Instruction Scope
SKILL.md only instructs using the Membrane CLI to authenticate, create connections, list actions, run actions, and proxy requests to CUFinder. It does not instruct reading local files, harvesting unrelated environment variables, or sending data to unknown endpoints outside Membrane/CUFinder.
Install Mechanism
This is an instruction-only skill (no install spec), and it recommends installing @membranehq/cli via npm (-g) or using npx. That's appropriate for the task, but installing global npm packages executes upstream package scripts — users should verify the package name and trust @membranehq before installing.
Credentials
The skill declares no required environment variables or local config paths. Auth is performed via Membrane (browser flow or headless code) and no API keys are requested by the skill itself, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request 'always' presence or modify other skills. It relies on Membrane's authentication flow which persists credentials server-side (expected behavior for a connector).
Assessment
This skill is instruction-only and coherent: it directs you to use the Membrane CLI to connect to CUFinder and does not ask for unrelated secrets. Before installing/using it: 1) Verify you trust Membrane (@membranehq) and the npm package name before running npm -g, since npm installs run upstream code. 2) Understand that requests proxied via Membrane route data through Membrane's servers — avoid sending sensitive data through the proxy unless you trust their service and privacy policies. 3) Use the browser-based login flow for interactive auth; in headless flows you'll paste codes into the CLI. 4) Confirm the connector IDs and action schemas returned by Membrane before running actions that modify data. If you want extra assurance, inspect the official Membrane CLI repository and CUFinder API docs referenced in SKILL.md before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97cmhgr8z86048g5vrqrfzgbs842rd6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.