Ixopay

v1.0.2

IXOPAY integration. Manage data, records, and automate workflows. Use when the user wants to interact with IXOPAY data.

0· 95·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name and description (IXOPAY integration) match the runtime instructions which exclusively use Membrane to proxy requests to IXOPAY. The guidance (install Membrane CLI, create a connection, run actions or proxied requests) is coherent with the stated purpose.
Instruction Scope
SKILL.md confines its actions to installing/using the Membrane CLI, performing Membrane login, listing/connecting actions, and proxying requests to IXOPAY. It does not instruct reading unrelated files, accessing unrelated env vars, or exfiltrating data to unexpected endpoints. It explicitly advises not to ask users for IXOPAY API keys.
Install Mechanism
There is no declared install spec in the registry, but the instructions tell users to run `npm install -g @membranehq/cli`. This is a reasonable, common install method, but the skill does not declare a required binary (npm/node) in metadata — a minor documentation mismatch to be aware of.
Credentials
The skill requests no environment variables or credentials. It relies on Membrane to manage IXOPAY authentication server-side, which is proportionate to the skill's function. No unrelated credential access is requested.
Persistence & Privilege
The skill is instruction-only, has no install manifest, and is not configured as always-enabled. It does not request elevated persistence or to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and tells the agent to use the Membrane CLI to talk to IXOPAY. Before installing/using it: (1) verify you trust Membrane (the skill delegates authentication and proxied API calls to Membrane — Membrane will handle IXOPAY credentials server-side); (2) confirm the npm package name (@membranehq/cli) is the official one and review the package (and its GitHub repo) if you can; (3) be aware the instructions assume you can run global npm installs (node/npm present) and that browser-based login will be used for authentication; (4) if you require an audit trail, check what data Membrane stores or logs for proxied requests. Overall the skill is coherent with its stated purpose, but only install/use it if you are comfortable delegating IXOPAY auth and API proxied traffic to Membrane.

Like a lobster shell, security has layers — review code before you run it.

latestvk972cfwzb1pevqcc5wnant5n0n842f7g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments