Lucidworks
v1.0.2Lucidworks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lucidworks data.
⭐ 0· 79·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 SKILL.md instructs the agent to use the Membrane CLI to discover connections, create a Lucidworks connection, run actions, and proxy raw API requests — this matches the stated purpose (manage Lucidworks data). The requirement to have a Membrane account is mentioned in the skill metadata and is coherent with using Membrane as the middleware.
Instruction Scope
Instructions only reference running the Membrane CLI (membrane login, connection list, action run, request proxying). The skill does not instruct the agent to read arbitrary local files or environment variables. However, proxying requests via Membrane means request payloads and credentials are sent to Membrane's service — users should expect their Lucidworks requests and data to flow through Membrane.
Install Mechanism
This is an instruction-only skill (no install spec). The docs recommend installing @membranehq/cli globally via npm and sometimes use npx @membranehq/cli@latest. That is a normal way to get a CLI, but it does involve fetching and running code from the npm registry. This is expected for a CLI-based integration but carries the usual supply-chain considerations (verify package identity and prefer pinned versions where appropriate).
Credentials
The skill declares no env vars or local credentials; instead it relies on a Membrane account and browser-based login. This is proportionate to the described behavior. Be aware that Membrane will manage and store credentials server-side and see proxied requests, so trusting the Membrane service/privacy is required.
Persistence & Privilege
The skill does not request persistent/always-on privileges; it is user-invocable and does not modify other skills or system-wide settings. No suspicious persistence is requested.
Assessment
This skill appears to be what it says: a Lucidworks integration implemented by instructing users/agents to use the Membrane CLI. Before installing or using it, consider: (1) Membrane is a third-party intermediary — your Lucidworks requests, data, and auth will flow through their service, so confirm you trust their privacy/security practices; (2) the instructions recommend installing an npm package or running npx, which fetches code from the npm registry — verify the @membranehq/cli package and repository (check publisher, package checksum/signature if possible), and prefer a pinned version rather than always using @latest in sensitive environments; (3) run the CLI in an isolated environment if you are worried about supply-chain risk. If you want direct integration without a third-party proxy, seek a skill that calls Lucidworks APIs directly and documents required API keys and scopes.Like a lobster shell, security has layers — review code before you run it.
latestvk97aetz9f1601j8q9pzacg740h843w81
License
MIT-0
Free to use, modify, and redistribute. No attribution required.