Zeet

v1.0.2

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

0· 95·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
Name/description claim Zeet integration and all runtime instructions exclusively describe using the Membrane CLI to discover and run Zeet-related actions or proxy API requests. Required resources (network, Membrane account, Membrane CLI) are consistent with the purpose.
Instruction Scope
Instructions are narrowly scoped to installing/running the Membrane CLI, creating connections, listing actions, running actions, and proxying API requests. They do not ask to read unrelated local files or exfiltrate arbitrary data. Note: the skill instructs the user to install a global npm package and to authorize via a browser flow — both are normal for this integration but carry the usual operational risks (installing third-party CLI code, granting a third-party service access to Zeet data).
Install Mechanism
There is no bundled installer in the skill metadata (instruction-only). The SKILL.md recommends `npm install -g @membranehq/cli` (and uses `npx` in examples). Installing a package from npm is a moderate-risk action compared with no install; it is a common and expected approach for a CLI-based integration but you should verify the package and publisher (@membranehq) before installing globally.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The SKILL.md explicitly advises creating a Membrane connection rather than sharing API keys, which is appropriate and proportionate for a connector-style integration.
Persistence & Privilege
The skill does not request permanent presence (always:false) and does not attempt to modify other skills or system-wide settings. It relies on the Membrane CLI for auth/session management; that behavior is consistent with the stated integration.
Assessment
This skill is coherent: it uses the Membrane CLI to talk to Zeet and requests no unrelated secrets. Before installing/running anything: 1) verify the @membranehq/cli package and publisher on npm (and prefer `npx` for one-off use if you don't want a global install); 2) inspect the Membrane project's homepage/repo/packge release to ensure it matches the expected vendor; 3) when authorizing via the browser, review the permission scopes being granted to the connector (Membrane will proxy requests and thus can access Zeet data); and 4) avoid pasting API keys into chat — follow the connection flow so credentials are handled by Membrane. If you need higher assurance, ask for the exact package version and repository link so you (or an auditor) can review the CLI source before installing.

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

latestvk971qtz3dhbpc51evgy1z0q7fn843tqn

License

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

Comments