Aci Payon

v1.0.2

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

0· 68·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
Name/description, CLI usage, and references to ACI PAY.ON and Membrane are consistent. The skill only requires network access and a Membrane account, which fits its stated function.
Instruction Scope
SKILL.md only instructs use of the Membrane CLI (login, create connection, list and run actions, proxy requests). It does not ask the agent to read unrelated files, request unrelated credentials, or exfiltrate data to unexpected endpoints.
Install Mechanism
No install spec for the skill itself (instruction-only). The guide suggests installing @membranehq/cli globally via npm (moderate-risk third-party package install). This is expected for a CLI-driven integration but verify package provenance (use npx as an alternative).
Credentials
SKILL.md declares no required env vars or credentials; authentication is handled via Membrane's browser login/connection flow, which is proportionate to the integration's needs.
Persistence & Privilege
Skill is not always-enabled and does not request system-wide configuration changes or other skills' credentials. Default autonomous invocation is allowed (platform default) but not combined with other concerning flags.
Assessment
This skill is an instruction-only integration that uses the Membrane CLI to proxy calls to ACI PAY.ON; it's internally consistent but take these practical precautions before installing: (1) Verify the CLI package author (npm org @membranehq) and prefer running with npx or audit the package before a global install. (2) Confirm the repository/homepage (links are provided in SKILL.md) match the official vendor. (3) Understand that Membrane will handle auth in a browser flow—trust in Membrane is required because they will hold/refresh connectors' credentials and can make proxied API calls on your behalf. (4) When creating connections, inspect the connector permissions and avoid pasting secrets into chat or unexpected places. (5) If you are uncomfortable with the agent autonomously invoking the skill, restrict its use in your agent settings. Overall the skill appears coherent for its stated purpose.

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

latestvk976yn9np5crycnngpqbgx4sj5842yz8

License

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

Comments