Leandata

v1.0.0

LeanData integration. Manage data, records, and automate workflows. Use when the user wants to interact with LeanData data.

0· 62·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (LeanData integration) match the instructions: discover connectors/actions and run them via the Membrane CLI. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to LeanData via Membrane. It does not instruct reading unrelated files, exfiltrating data, or accessing unrelated system state.
Install Mechanism
The skill is instruction-only and asks the user to install @membranehq/cli via npm (global install shown). This is expected for a CLI-focused integration but installing global npm packages executes third-party code on the machine—consider using npx or reviewing the package first.
Credentials
No environment variables, credentials, or config paths are required by the skill itself; auth is handled interactively by Membrane. This is proportionate to the described functionality.
Persistence & Privilege
The skill is not marked always:true and does not request persistent system-wide configuration. It relies on the Membrane CLI for auth and runtime state, which is normal for this type of integration.
Assessment
This skill appears coherent and uses the Membrane CLI to access LeanData, but before installing: (1) verify the @membranehq/cli package on npm and the publisher (use the official org/repo), (2) prefer npx over a global npm install if you want to avoid installing third-party binaries system-wide, (3) understand that Membrane will hold/authenticate access to LeanData and can proxy API requests—only grant connections to services you trust, and (4) run the CLI in an environment you control (not shared CI runners or multi-user shells) if the data is sensitive. If you need higher assurance, inspect the Membrane CLI repository and npm release, and confirm the connection/auth flow meets your security policies.

Like a lobster shell, security has layers — review code before you run it.

latestvk97f16fym2f8np4zf4y9zdbh2984bkz8

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments