Checkoutcom
v1.0.2Checkout.com integration. Manage data, records, and automate workflows. Use when the user wants to interact with Checkout.com data.
⭐ 0· 51·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
medium confidencePurpose & Capability
The skill's stated purpose (Checkout.com integration) matches the instructions (use Membrane to connect and proxy Checkout.com API calls). However the registry metadata lists no required binaries or network/account requirements while SKILL.md explicitly requires network access and installing the @membranehq/cli — a minor inconsistency in declared requirements.
Instruction Scope
Runtime instructions only direct the agent/user to install and use the Membrane CLI to create connections, list actions, run actions, and proxy requests to Checkout.com. The instructions do not ask the agent to read unrelated local files, environment variables, or transmit data to unexpected endpoints beyond Membrane/Checkout.com.
Install Mechanism
There is no formal install spec in the registry; the SKILL.md instructs running `npm install -g @membranehq/cli`. Installing a global npm CLI is a reasonable way to enable the described functionality but carries typical supply-chain risk of npm packages and will write files/config to the system — the skill should have declared this dependency in metadata.
Credentials
The skill does not request environment variables or secrets. It explicitly advises using Membrane to avoid providing API keys locally. The requirement for a Membrane account and browser-based auth is proportional to the described purpose.
Persistence & Privilege
Skill is instruction-only, not marked always:true, and does not request elevated platform privileges. The Membrane CLI itself will persist credentials/config locally during login, which is expected for a CLI-based integration.
Assessment
This skill appears to do what it claims: it uses the Membrane CLI as a proxy to interact with Checkout.com. Before installing or using it, verify the @membranehq/cli npm package and the getmembrane.com service (check publisher reputation, npm package downloads and source repo). Be aware that installing the CLI will write files and credentials to your machine and open a browser login flow — only authenticate if you trust Membrane to hold your Checkout.com access. If you need stricter control, consider using official Checkout.com SDKs/APIs directly or running the CLI in an isolated environment. Also note the skill metadata omitted the CLI/network requirement — make sure your environment has npm and network access before relying on the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97242evmncdaxs5ghmj8433jx84224q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
