Ibanity
v1.0.0Ibanity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ibanity data.
⭐ 0· 30·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the skill is explicitly an Ibanity integration that uses the Membrane CLI. It does not request unrelated credentials, binaries, or access.
Instruction Scope
SKILL.md stays on-topic: it instructs how to install and use the Membrane CLI to authenticate, create a connection, list actions, run actions, and proxy requests to Ibanity. It does not instruct reading unrelated files, harvesting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no install spec), and recommends installing @membranehq/cli via npm (global). Installing npm packages runs code from the registry — a normal but non-trivial installation step. The recommendation to use npx@latest (in examples) can change behavior over time; consider pinning a specific version if you want reproducible behavior.
Credentials
No env vars, config paths, or primary credentials are requested by the skill. It requires a Membrane account and browser-based login, which is appropriate for a proxying integration that should not ask for local API keys.
Persistence & Privilege
always is false and the skill is instruction-only with no install modifying agent config. The skill does not request persistent agent-wide privileges.
Assessment
This skill delegates all auth and API calls to the Membrane CLI — you will need to install @membranehq/cli (npm) and log in to a Membrane account which will be granted access to your Ibanity data. Before installing or running the CLI: (1) verify the Membrane package and organization (e.g., check the npm package, GitHub repo, and the getmembrane.com site) to ensure you trust the publisher; (2) be aware that installing global npm packages executes code from the registry — prefer pinned versions over 'latest' if you want stability; (3) review what access the Membrane connection will request and only grant it to accounts you control; (4) do not provide bank credentials to the skill itself — follow the CLI's browser-based auth flow as instructed; and (5) if you need stronger assurance, audit the Membrane project's repository and privacy/security documentation or test in a limited environment before using with production banking data.Like a lobster shell, security has layers — review code before you run it.
latestvk97fjt4x4mpjgv3wgn4gvkp05h846w3b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.