Snowflake
v1.0.0Snowflake integration. Manage data, records, and automate workflows. Use when the user wants to interact with Snowflake data.
⭐ 0· 26·0 current·0 all-time
byMembrane Dev@membranedev
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 (Snowflake integration) align with the instructions: all operations are done via the Membrane CLI which proxies to Snowflake. There are no unrelated required env vars, binaries, or config paths.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in, listing/creating connections, running actions, or proxying requests to Snowflake via Membrane. It does not direct reading unrelated local files, accessing unrelated credentials, or sending data to unexpected endpoints beyond Membrane/Snowflake.
Install Mechanism
The skill is instruction-only, but it tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard but non-trivial install step (writes to system PATH). This is a moderate-risk vector compared with an instruction-only skill with no install guidance; verify package provenance and consider using `npx` or a scoped/local install if preferred.
Credentials
No environment variables, secrets, or config paths are requested by the skill. The SKILL.md explicitly advises letting Membrane manage credentials server-side (no local API keys), which is proportional to the declared purpose.
Persistence & Privilege
The skill does not request always:true and has no install manifest that would persist code beyond the CLI the user chooses to install. Normal autonomous invocation settings remain, which is expected for an integration skill.
Assessment
This skill appears coherent: it operates by directing you to use the Membrane CLI which will handle Snowflake auth and proxy requests. Before installing or using it, consider the following: 1) Trust: the CLI routes Snowflake requests through Membrane — you are granting Membrane access to Snowflake data, so confirm you trust getmembrane.com/@membranehq and your organization’s security policy. 2) Package install: the instructions suggest `npm install -g @membranehq/cli` (global install). Prefer `npx @membranehq/cli` or a local install if you want to avoid writing binaries to system paths; verify the package name and check the package's homepage/repo for authenticity and recent activity. 3) Least privilege: use connections/accounts with scoped permissions (not full admin keys) when connecting Snowflake through third-party tooling. 4) Audit: review what data will be proxied (sensitive tables/queries) and, if needed, test in a non-production environment first. Overall, the skill’s requests and instructions align with its stated purpose, but you should only proceed if you trust Membrane and are comfortable installing a third-party CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk97bsc872s0tk5s2kd53f3pss9847xcv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.