Comeet
v1.0.2Comeet integration. Manage data, records, and automate workflows. Use when the user wants to interact with Comeet data.
⭐ 0· 69·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
Name/description match the instructions: the skill uses the Membrane CLI to access Comeet. No unrelated environment variables, binaries, or configuration paths are requested.
Instruction Scope
SKILL.md restricts actions to installing/using @membranehq/cli, logging in, creating connections, listing/running actions, and proxying Comeet API requests. This stays within the integration purpose. Caution: Membrane acts as a proxy and will be able to access Comeet data/credentials and proxy arbitrary API requests — you must trust that service.
Install Mechanism
No packaged install spec in the registry (instruction-only). The guide recommends npm install -g @membranehq/cli or using npx. Installing an npm package (especially global) has moderate risk (postinstall scripts, privilege to write global bins); using npx reduces persistence risk.
Credentials
The skill declares no environment variables or secrets. It explicitly instructs to avoid collecting API keys locally and to use Membrane-managed connections, which is proportionate to the stated purpose. Be aware that authentication is delegated to Membrane (a third party).
Persistence & Privilege
always is false and there is no install script or code written by the skill. The skill does not request elevated or persistent platform privileges beyond installing/using the Membrane CLI if you choose to.
Assessment
This skill is coherent for interacting with Comeet via the Membrane proxy, but installing the Membrane CLI means trusting Membrane with your Comeet credentials and API traffic. Before installing: verify the @membranehq/cli npm package and the project's GitHub (https://github.com/membranedev/application-skills), prefer using npx if you don't want a global install, review the npm package contents or repository for unexpected postinstall scripts, and confirm what permissions the Membrane connection will request from Comeet (least privilege). If you cannot trust Membrane with your data, do not create the connection and instead use a direct Comeet integration that you control.Like a lobster shell, security has layers — review code before you run it.
latestvk97exzp42k719vn23s2g13dth5843rqt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.