Jibble
v1.0.2Jibble integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jibble data.
⭐ 0· 104·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 (Jibble integration) matches the instructions: all actions are about discovering connectors, creating connections, running proxied requests and actions via the Membrane CLI. Nothing requested is unrelated to that purpose.
Instruction Scope
SKILL.md only instructs installing and running the Membrane CLI, performing browser-based authentication, creating a connector/connection, listing/running actions, and proxying requests to Jibble. It does not ask to read local secrets, system config, or unrelated files.
Install Mechanism
There is no built-in installer, but the skill instructs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal workflow but does introduce the usual supply-chain/privilege considerations for third-party CLI tools.
Credentials
The skill declares no required env vars or credentials and instructs users to use Membrane-hosted connections (browser auth). The requested permissions are proportional to the stated goal of accessing Jibble via Membrane.
Persistence & Privilege
The skill is not forced-always, is user-invocable, and allows normal autonomous invocation. That combination is standard for integrations and is not excessive here given the lack of additional credential requests.
Assessment
This skill is coherent: it tells you to use the Membrane CLI to connect to Jibble and does not ask for extra secrets. Before installing: (1) verify you trust the @membranehq/cli package on npm (review package source, maintainer, and popularity) because a global npm install executes code with your user privileges; (2) verify what access the Membrane connection will request from your Jibble account (scopes/permissions) before completing browser auth; (3) if you prefer not to install a global CLI, consider running the CLI via npx to avoid a permanent global install; and (4) be aware the agent can invoke the skill autonomously (default) — only enable that if you trust the integration and Membrane account behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97acfkhmfn5tz3d7r3vzd2hp9842q3q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.