Wepay
v1.0.0WePay integration. Manage data, records, and automate workflows. Use when the user wants to interact with WePay data.
⭐ 0· 46·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (WePay integration) match the instructions: the SKILL.md exclusively documents using the Membrane CLI to create a WePay connection, list/run actions, and proxy requests. Nothing requested (no env vars, no unrelated binaries) is out of scope for a connector helper.
Instruction Scope
Runtime instructions are narrowly scoped to installing and using @membranehq/cli, creating connections, listing actions, running actions, and proxying API calls. The instructions do not ask the agent to read unrelated files, leak other credentials, or send data to third-party endpoints beyond Membrane/WePay.
Install Mechanism
There is no formal install spec in the package registry (instruction-only skill). SKILL.md recommends installing @membranehq/cli via npm -g (a public npm package) and also uses npx in examples. Installing a global npm package is a reasonable approach but has moderate system-level impact; you can use npx or a local install to reduce persistence.
Credentials
The skill declares no required environment variables or credentials. SKILL.md explicitly advises letting Membrane handle credentials and not asking users for API keys, which is proportionate to its purpose.
Persistence & Privilege
The skill is not forced-always and is user-invocable; it does not request special platform-wide persistence or alter other skills' configs. Autonomous invocation is allowed (platform default) and is not combined with other concerning flags.
Assessment
This skill is coherent but exercise normal caution before installing and using the Membrane CLI: verify the @membranehq/cli package and its GitHub repo are official (check publisher and repo contents on npm/github), prefer running with npx or a local install if you want to avoid a global npm package, and review what permissions/accounts you grant during 'membrane login' (Membrane will act as a proxy and will have access to connected WePay data). Because this is an instruction-only skill, there is no local code to inspect in the package listing — if you need stronger assurance, review the Membrane CLI source and the Membrane privacy/security docs before connecting production WePay accounts.Like a lobster shell, security has layers — review code before you run it.
latestvk975psqp3n83d4m0hxja0vjzfs84fjep
License
MIT-0
Free to use, modify, and redistribute. No attribution required.