Libraria
v1.0.2Libraria integration. Manage Libraries. Use when the user wants to interact with Libraria data.
⭐ 0· 112·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 (Libraria integration) align with the instructions: using Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Libraria. There are no unrelated env vars, binaries, or config paths declared.
Instruction Scope
Instructions are explicit about installing and using @membranehq/cli, logging in, creating connections, running actions, and proxying requests. They do not instruct reading unrelated files or harvesting environment variables. NOTE: API requests and document data will flow through Membrane's service (the CLI proxies requests and injects auth headers), so Membrane's servers will see proxied traffic and metadata — this is expected but important for privacy/security decisions.
Install Mechanism
This is an instruction-only skill (no install spec). The README tells the user to run npm install -g @membranehq/cli, which is a public npm package — a standard mechanism. Consider verifying the package identity and trustworthiness before global install.
Credentials
The skill declares no required environment variables or credentials. Runtime behavior relies on Membrane's login flow (browser-based OAuth) rather than asking for local API keys, which is proportionate to its purpose.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and contains no instructions to persist credentials locally. Autonomous invocation is permitted by platform default but not excessive here.
Assessment
This skill is coherent for connecting to Libraria via Membrane. Before installing/use: (1) Confirm you trust the Membrane service and the @membranehq/cli npm package (check publisher, repository, and npm page). (2) Understand that proxied API calls and document data will transit Membrane's platform — do not use it for data you cannot share with that service. (3) Prefer least-privilege connections on Membrane and avoid pasting sensitive credentials locally. (4) If you need an offline or self-hosted integration, this skill assumes use of Membrane and will not work without that service.Like a lobster shell, security has layers — review code before you run it.
latestvk97d1s9trws5jpzcxbg12zvtwd843e3w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.