Plecto
v1.0.2Plecto integration. Manage Organizations, Persons, Deals, Pipelines, Activities, Notes and more. Use when the user wants to interact with Plecto 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
medium confidencePurpose & Capability
Name/description (Plecto integration) match the instructions: the SKILL.md exclusively documents using the Membrane CLI to connect to Plecto, discover actions, run actions, and proxy API requests. Nothing unrelated (e.g., cloud credentials, unrelated services) is requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, logging in via browser, creating/using a Plecto connection, listing actions, running actions, and proxying requests through Membrane. The skill does not instruct the agent to read arbitrary local files or exfiltrate data to unexpected endpoints; proxied requests go through Membrane to Plecto as expected.
Install Mechanism
No formal install spec in the registry (instruction-only), but the SKILL.md instructs installing a global npm package (npm install -g @membranehq/cli). Installing a global npm CLI will run third‑party code on the host (moderate supply‑chain/execution risk). This is proportionate to using Membrane, but deserves verification of the package source and trustworthiness.
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane handle auth (browser login). That is consistent with the described workflow; it does not request unrelated secrets or config paths.
Persistence & Privilege
The registry flags show no forced persistence (always: false) and normal autonomous invocation settings. The skill does not request special agent-wide config changes or access to other skills' credentials.
Assessment
This skill is internally consistent: it uses the Membrane CLI to talk to Plecto rather than asking you for API keys. Before installing and using it, verify and trust the @membranehq/cli package (check the npm page and GitHub repo, review recent releases and maintainers). Consider installing the CLI in an isolated environment (container, VM, or non‑privileged user) if you want to reduce risk from running a global npm package. Be aware that once you authenticate, Membrane will be able to issue arbitrary proxied requests to your Plecto instance on your behalf, so only connect accounts you trust and review Membrane’s privacy/security docs if that matters.Like a lobster shell, security has layers — review code before you run it.
latestvk971485f4vf240hb752088q2s5843ys1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.