42Crunch
v1.0.042Crunch integration. Manage data, records, and automate workflows. Use when the user wants to interact with 42Crunch data.
⭐ 0· 50·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
The name/description say '42Crunch integration' and the SKILL.md exclusively documents using the Membrane CLI to discover actions, create a connection, run actions, and proxy requests to 42Crunch — which matches the stated purpose. There are no unrelated required env vars, binaries, or config paths.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in (browser-based OAuth flow), creating/listing connections, running actions, and proxying requests to 42Crunch. The skill does not instruct reading arbitrary local files, grabbing unrelated credentials, or sending data to unexpected endpoints. The guidance is somewhat broad (e.g., 'use action names and parameters as needed') but that is appropriate for a generic connector.
Install Mechanism
This is an instruction-only skill with no install spec, but it instructs the user to run 'npm install -g @membranehq/cli' or use npx. Installing a global npm CLI is a normal way to obtain the tooling, but it does write to disk and pulls code from the npm registry — the user should verify the package source and version before installing.
Credentials
The skill requests no environment variables or local secrets. Authentication is delegated to Membrane (browser OAuth), which is proportional; however, delegating auth means the Membrane service will hold/mediate credentials for 42Crunch, so the user must trust that service.
Persistence & Privilege
The skill is not always-enabled and is user-invocable (normal). It does not request persistent system-wide privileges, nor does it declare modifications to other skills or system configs.
Assessment
This skill is coherent and focused: it tells the agent to use the Membrane CLI to connect to 42Crunch and run actions. Before installing/using it: (1) verify you trust Membrane (https://getmembrane.com) because it will hold/mediate your 42Crunch authentication; (2) review the @membranehq/cli npm package and install from a trusted environment (consider using npx or a local install instead of global -g if you prefer); (3) be aware that 'membrane request' can proxy arbitrary API calls to 42Crunch — only run requests you expect and ensure you understand what data may be returned; (4) the skill is instruction-only (no bundled code), so it will only act if the agent runs the documented CLI commands or you run them locally. If you need higher assurance, inspect the Membrane CLI source or the connector configuration in your Membrane account before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97ak2xgcjx18p3d7mnhnv0ae184cgff
License
MIT-0
Free to use, modify, and redistribute. No attribution required.