ClawHub

Paystack

v1.0.2

Paystack integration. Manage Customers, Transactions, Plans, Products, Splits. Use when the user wants to interact with Paystack data.

⭐ 0· 78·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
The name/description say 'Paystack integration' and the instructions exclusively use the Membrane CLI to create connections, run actions, and proxy requests to Paystack — the requested artifacts (Membrane CLI, a Membrane account) are proportional and expected.
✓
Instruction Scope
SKILL.md only instructs the agent/user to install and use the Membrane CLI, log in, list connections/actions, run actions, and optionally proxy API requests. It does not ask the agent to read unrelated files, harvest local secrets, or transmit data to unexpected endpoints.
ℹ
Install Mechanism
The install step recommends `npm install -g @membranehq/cli`. Using npm is a common, expected install path for CLIs, but global npm packages require trust in the package publisher and the npm registry; no arbitrary URLs or archives are used.
✓
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to handle Paystack credentials server-side, which is consistent with instructions that say not to ask users for API keys.
✓
Persistence & Privilege
The skill is instruction-only, has no install spec that writes files, and is not always-on. Model invocation is allowed (platform default), which is normal and not excessive here.
Assessment
This skill is coherent: it uses the Membrane CLI to access Paystack and does not request local secrets. Before installing, confirm you trust the @membranehq/cli npm package and its publisher (verify the npm/GitHub package page and version), and be aware that using it requires a Membrane account (authentication via browser). If you have policies about third-party SaaS handling payment credentials, review Membrane's privacy/security documentation before connecting live payment accounts.

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

latestvk978zn7e70n2f7c2x3mrhef325842y4z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments