Paymo
v1.0.2Paymo integration. Manage Organizations, Pipelines, Leads, Users, Goals, Filters. Use when the user wants to interact with Paymo data.
⭐ 0· 75·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
high confidencePurpose & Capability
The skill claims to integrate with Paymo and all instructions center on using the Membrane CLI to connect and proxy Paymo API calls. Requiring the Membrane CLI is coherent with the stated purpose and there are no unrelated env vars, binaries, or install artifacts requested.
Instruction Scope
SKILL.md tells the agent to install and run the Membrane CLI, perform browser-based login, create connections, list actions, run actions, and proxy requests. These steps stay within Paymo integration scope. Important note: proxying means request payloads and Paymo credentials are handled by Membrane's service — data will be sent to Membrane and then to Paymo.
Install Mechanism
Install is via npm install -g @membranehq/cli (a public npm package). This is a standard mechanism and not exotic, but it writes a global binary to disk and runs third-party code, so you should verify the package and repo (e.g., @membranehq/cli on npm/GitHub) before installing on production systems.
Credentials
The skill requests no environment variables or local credentials. Authentication is delegated to Membrane (browser OAuth flow). This is proportionate, though it means Membrane will hold/refresh the tokens — consider whether you trust that service with your Paymo data.
Persistence & Privilege
The skill is instruction-only and not set to always: true. It does not request permanent agent privileges or modify other skills. Autonomous invocation is allowed (platform default) but not a new privilege introduced by this skill.
Assessment
This skill is coherent: it uses the Membrane CLI to connect to Paymo rather than asking you for API keys. Before installing or using it: 1) Verify the @membranehq/cli package and the cited GitHub repo to ensure they are legitimate; 2) Understand that Membrane will proxy requests and store/refresh Paymo credentials — if that’s sensitive, decide whether you trust the service or prefer direct API keys; 3) Installing the CLI globally will add third-party binaries to your system—install in a sandbox or CI runner first if possible; 4) Confirm the agent environment can run npm and open browser-based auth flows (or use the headless flow securely). If any of these raise concern, audit the Membrane project or use a direct Paymo integration you control.Like a lobster shell, security has layers — review code before you run it.
latestvk97590dhvv5spdfa82f25qscth842ge4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.