Unstructured
v1.0.0Unstructured integration. Manage data, records, and automate workflows. Use when the user wants to interact with Unstructured data.
⭐ 0· 55·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 (Unstructured integration) matches the instructions: all runtime steps call the Membrane CLI to discover connectors, create connections to Unstructured, run actions, or proxy API requests. No unrelated services, credentials, or system resources are requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in via browser, listing/connecting actions, running actions, and proxying requests. It does not instruct reading arbitrary local files, accessing unrelated env vars, modifying other skills, or exfiltrating data to unexpected endpoints. It does route requests through Membrane (server-side), which is expected for this integration.
Install Mechanism
The skill recommends installing @membranehq/cli via npm (global install or npx). Installing a CLI from npm is expected for this workflow but carries the usual supply-chain considerations (verify package ownership, review source repo). There is no download from untrusted URLs or extract/install of arbitrary archives in the instructions.
Credentials
No environment variables, local config paths, or credentials are requested by the skill. Authentication is delegated to Membrane's browser-based login flow, which aligns with the stated best practice 'let Membrane handle credentials.'
Persistence & Privilege
The skill does not request permanent presence (always:false) and does not instruct modifying agent-wide settings. Autonomous invocation is allowed by platform default but is not combined with broad credentials or other high-risk permissions.
Assessment
This skill is instruction-only and uses the Membrane CLI to interact with Unstructured; that is consistent with its purpose. Before installing/use: (1) verify the @membranehq/cli npm package and the GitHub repository (ensure the publisher is legitimate), (2) review Membrane's privacy and data handling policies because requests and document data will be proxied through Membrane and Unstructured, (3) prefer npx for one-off runs instead of global npm -g installs if you want less persistent footprint, and (4) be aware that running 'membrane login' opens a browser auth flow—in headless environments you'll copy codes manually. If you need higher assurance, inspect the Membrane CLI source on GitHub and the package's npm maintainers before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97bwg6kj43876p2j2t9nq79v984cgnm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.