Paddle

Paddle integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Paddle data.

Key things to check before installing: 1) Clarify the mismatch — ask the publisher whether this skill targets Paddle payments only or also CRM entities (the description and SKILL.md disagree). 2) Inspect the Membrane CLI package and repository (@membranehq/cli) on npm/GitHub before running npm install -g; prefer a specific version instead of @latest. 3) If you must install globally, do so in a controlled environment (container or VM) or run a security review (npm audit, review package source). 4) Verify the homepage/repository (getmembrane.com and the GitHub link) match the package owner and look legitimate. 5) Confirm what permissions the Membrane login/connect flow will grant and that no unrelated credentials are requested. If you are uncomfortable with global npm installs or the origin, run the Membrane CLI in an isolated sandbox or ask the skill author to provide a pinned, signed release and clearer documentation. If you need higher confidence, request the skill author to fix the description mismatch and provide a link to the exact CLI package/release used.

Type: OpenClaw Skill Name: paddle-integration Version: 1.0.3 The skill facilitates Paddle integration by instructing the agent to install a global NPM package (@membranehq/cli) and delegate all API actions and credential management to the third-party Membrane platform. While these instructions in SKILL.md are aligned with the stated purpose of using Membrane as a middleware, the requirement for high-privilege shell commands (npm install -g) and the redirection of data through external infrastructure (getmembrane.com) constitute risky capabilities that warrant a suspicious classification despite the lack of clear malicious intent.