Apto Payments
v1.0.2Apto Payments integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apto Payments data.
⭐ 0· 76·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
The skill clearly intends to integrate Apto Payments via Membrane and the instructions match that purpose. One small inconsistency: the registry metadata lists no required binaries, but the SKILL.md instructs installing and running the Membrane CLI (so in practice you need node/npm and the membrane binary). This is an omission in declared requirements, not a functional mismatch.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, creating/using connections, running actions, and proxying API requests through Membrane. The instructions do not ask the agent to read arbitrary local files, environment variables, or transmits data to unknown endpoints beyond Membrane/Apto Payments.
Install Mechanism
There is no formal install spec in the registry; the SKILL.md tells the user to install @membranehq/cli globally via npm (and suggests npx for ad-hoc commands). Installing an npm package from the public registry is a reasonable approach but carries the usual supply-chain and trust considerations.
Credentials
The skill declares no required environment variables or local secrets and explicitly instructs not to ask users for Apto API keys. Authentication is delegated to Membrane (server-side), which is proportionate to the described function—but it does mean you must trust Membrane with credentials and proxied request payloads.
Persistence & Privilege
The skill does not request always:true, does not alter other skills' configurations, and is user-invocable. It relies on a CLI the user installs; there is no automatic or hidden persistence requested by the skill itself.
Assessment
This skill is instruction-only and uses the Membrane CLI to proxy Apto Payments API calls; it does not ask for unrelated secrets. Before installing: 1) confirm you trust Membrane/getmembrane.com and review the @membranehq/cli npm package and its GitHub repo for code and recent releases; 2) be aware the CLI will communicate with Membrane servers and will handle your Apto Payments credentials server-side — if you need to keep credentials local, this approach may not be appropriate; 3) installing a global npm package and using npx executes code from the registry, so only proceed if you trust the maintainer and supply chain; and 4) note the registry metadata should declare the membrane binary as a required binary (node/npm) — the absence is an authoring omission, not a functional change.Like a lobster shell, security has layers — review code before you run it.
latestvk976w4j92mnz37pndgcmsqdet18424hr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.