Bancontact Payconiq Company
v1.0.0Bancontact Payconiq Company integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bancontact Payconiq Company d...
⭐ 0· 28·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 match the instructions: the SKILL.md teaches how to use the Membrane CLI to connect to Bancontact/Payconiq. Nothing requested (no env vars, no unrelated binaries) is out of scope for a connector integration skill.
Instruction Scope
Runtime instructions are focused on installing and using @membranehq/cli (login, connect, action list/run, proxy request). They do not ask the agent to read unrelated files, harvest secrets, or contact unexpected endpoints. Note: proxying API requests via Membrane means Membrane will see request/response data — this is expected for a proxy-based integration but worth being aware of.
Install Mechanism
The skill is instruction-only (no install spec) but tells users to run `npm install -g @membranehq/cli`. Installing a public npm CLI is a reasonable step for this integration, but global npm installs execute code from the npm registry — verify the package and publisher. As a lower-friction alternative the skill even suggests using `npx` in some examples.
Credentials
The skill declares no required env vars or credentials; SKILL.md states Membrane handles authentication server-side and advises creating a connection via the CLI/browser. Requested permissions are proportional to the stated purpose.
Persistence & Privilege
The skill does not request always:true or modify other skills; it is user-invocable and allows autonomous invocation (platform default). There is no evidence of excessive persistence or cross-skill configuration.
Assessment
This skill looks coherent and reasonable for connecting to Bancontact/Payconiq via Membrane. Before installing/running anything: (1) verify the @membranehq/cli package and publisher on the npm registry and prefer using `npx` if you want to avoid a global install; (2) understand that Membrane will proxy requests and therefore can see request/response data and handle credentials on your behalf — only use if you trust the Membrane service; (3) when authenticating, use the browser flow as instructed and restrict the Membrane connection's permissions if possible; (4) if you need stricter control, review Membrane's docs and consider creating an account with limited-scoped access or using organization policies. Overall the skill's instructions and requirements align with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97f8dna6fh4tqvjpqqyd6b1318467hf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.