Llamaindex

v1.0.2

LlamaIndex integration. Manage data, records, and automate workflows. Use when the user wants to interact with LlamaIndex data.

0· 77·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description describe a LlamaIndex integration and the SKILL.md exclusively instructs use of the Membrane CLI to connect to LlamaIndex and run actions — the requested capabilities (network + Membrane account) are coherent with that purpose.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI (login, connection, action list/run, proxy requests). They do not instruct reading unrelated files, accessing unrelated env vars, or exfiltrating data. They do require interactive/browser auth for the user’s account, which is expected for connector flows.
Install Mechanism
No install spec in the skill bundle itself, but the SKILL.md recommends installing @membranehq/cli via npm (global). Installing an npm CLI from the public registry is a reasonable and expected mechanism, but it carries the usual moderate risk of third-party packages — verify the package/publisher before global install.
Credentials
The skill declares no required environment variables or local config paths. It relies on Membrane to manage credentials server-side, which aligns with the guidance in SKILL.md. There are no unexplained secret requests.
Persistence & Privilege
always is false and the skill is instruction-only (no code installed by the skill). There is no request to modify other skills or system-wide agent settings.
Assessment
This skill delegates all LlamaIndex interactions to the Membrane CLI and does not itself request secrets — that is coherent. Before installing: verify the @membranehq/cli npm package and its publisher (check the GitHub repo and npm page), review Membrane’s privacy/security docs because Membrane will proxy requests and handle your LlamaIndex credentials, and be aware the CLI login flow opens a browser (or prints a URL/code for headless use). If you handle sensitive data, confirm you are comfortable granting Membrane access to that data and consider using a sandbox/test account first.

Like a lobster shell, security has layers — review code before you run it.

latestvk970n7g1pxfw9s38bhaahdj5r9842qcj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments