ACI PAY.ON integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACI PAY.ON data.
58
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./skills/aci-payon/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill is an explicit integration with ACI PAY.ON, a payment gateway. It exposes domain-specific concepts (Payment, Payment Session, Transaction) and instructs using Membrane actions and proxy requests to call the ACI PAY.ON API (including POST/PUT methods and action runs). Those capabilities are specifically designed to create/process transactions and interact directly with a payment processor, i.e., to move money. Therefore it grants direct financial execution authority.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill requires installing/running the Membrane CLI (e.g. `npm install -g @membranehq/cli@latest` and `npx @membranehq/cli ...`), which fetches and executes remote package code at runtime from the npm registry (see https://www.npmjs.com/package/@membranehq/cli), so this is a runtime external dependency that can execute remote code.
f484c82
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.