Chipax
v1.0.0Chipax integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chipax data.
⭐ 0· 52·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 skill claims to integrate with Chipax and all runtime instructions use the Membrane CLI and Membrane-managed connections to Chipax — this is coherent. Minor inconsistency: registry metadata states no required binaries or env vars, but the SKILL.md tells the user to install the @membranehq/cli (npm) and to have network access and a Membrane account.
Instruction Scope
SKILL.md stays within scope: it instructs the agent/operator to install and use the Membrane CLI to create connections, list/run actions, and proxy requests to the Chipax API. It does not instruct reading arbitrary local files, unrelated env vars, or transmitting data to unexpected endpoints beyond Membrane/Chipax.
Install Mechanism
There is no formal install spec in the registry; the instructions recommend installing @membranehq/cli globally via npm (and using npx for discovery). Installing an npm CLI is a common/expected approach here, but it is a network download from the npm registry — moderate trust in the package/author is required.
Credentials
The skill requests no environment variables or local secrets. It intentionally defers authentication to Membrane (the documented workflow uses browser-based login and connections), which is proportionate for a connector-style integration.
Persistence & Privilege
Skill is not always-enabled and is user-invocable; it does not request to modify other skills or system-wide settings. There is no evidence it requires elevated persistence or privileges.
Assessment
This skill appears to be a straightforward Chipax connector that relies on the Membrane CLI. Before installing or using it: (1) be prepared to install @membranehq/cli via npm or use npx; (2) you'll need a Membrane account and will authenticate in your browser (Membrane will handle Chipax credentials server-side); (3) verify the @membranehq package and the getmembrane.com project are the genuine sources you expect (npm package page, GitHub repo, and company homepage); and (4) note the registry metadata did not declare the CLI dependency — this is likely an oversight but worth checking. If you do not trust Membrane to proxy and hold your Chipax credentials, do not create a connection.Like a lobster shell, security has layers — review code before you run it.
latestvk9780s4chn8he3tzdc87rt10v984dagh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.