Clinchpad
v1.0.2ClinchPad integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClinchPad data.
⭐ 0· 97·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 name/description (ClinchPad integration) match the instructions: all runtime steps use Membrane to talk to ClinchPad. Requiring a Membrane account and network access is appropriate for this integration.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the Membrane CLI, log in via browser, create connections, list actions, run actions, and proxy arbitrary requests to the ClinchPad API. Those steps stay within the integration's scope. One minor mismatch: the registry metadata lists no required binaries, but the instructions assume npm (to install the CLI) and a browser (for login) – this is a documentation/metadata omission rather than a functional mismatch.
Install Mechanism
The skill is instruction-only (no automatic install), but it tells users to install @membranehq/cli globally via npm. Installing a global npm package is a moderate-risk action (executing code from the npm registry). This is expected for a CLI-driven integration, but users should verify the package identity and origin before installing on sensitive systems.
Credentials
The skill requests no environment variables or secrets and explicitly instructs not to ask users for API keys, relying on Membrane to manage credentials. The requested access (browser-based login and a Membrane account) is proportionate to the described functionality.
Persistence & Privilege
The skill does not request always: true, does not include install-time code, and does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed by default but not combined with other privileged or unexplained access.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to access ClinchPad and does not ask for raw API keys. Before installing: (1) verify the npm package @membranehq/cli is the official package (check npm page and repository), (2) prefer installing the CLI in a sandbox/container or using a per-project install rather than globally on a production host, (3) be aware the login flow opens a browser and the CLI may store local session tokens, and (4) review Membrane's privacy/security documentation if you plan to let it manage credentials server-side.Like a lobster shell, security has layers — review code before you run it.
latestvk973q8gqn4fhkf75sgb63wpz6x842eqf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.