Tribe Payments
v1.0.2Tribe Payments integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tribe Payments data.
⭐ 0· 75·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 name/description claim Tribe Payments integration and the SKILL.md consistently instructs using the Membrane CLI to connect and proxy requests to Tribe Payments. Required tools (npm/membrane CLI) and network access are proportionate to the stated purpose.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Tribe Payments. They do not request reading unrelated local files, extra environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill with no automated install spec. The SKILL.md recommends user-run npm install -g @membranehq/cli or npx commands; that is a reasonable, explicit user action rather than a hidden download or extract.
Credentials
The skill declares no required env vars or credentials. Authentication is delegated to Membrane CLI/browser flows, which is appropriate for a connector-style integration. There are no unexpected credential requests in the instructions.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system-level privileges. It also does not modify other skills or system configs. The skill allows normal autonomous invocation (platform default), which is expected for a skill of this type.
Assessment
This skill is an instructions-only guide for using the Membrane CLI to talk to Tribe Payments. Before installing/using it: (1) Confirm you trust Membrane (getmembrane.com / the listed GitHub repo) because the CLI will gain access to payment data once you authenticate. (2) Review connector scopes and only grant the minimum permissions needed. (3) Run npm installs in a controlled environment (or use npx to avoid a global install) and avoid using high-privilege accounts for the initial connection. (4) If you need stronger isolation, create a dedicated Membrane/Trove account with limited access and audit connection activity. Overall the skill is internally consistent, but connecting any CLI to payment systems grants it access to sensitive data — proceed with standard operational safeguards.Like a lobster shell, security has layers — review code before you run it.
latestvk977q69qbv2vak9c3sex643jv5843fqk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.