Shipamax
v1.0.1Shipamax integration. Manage data, records, and automate workflows. Use when the user wants to interact with Shipamax data.
⭐ 0· 53·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
medium confidencePurpose & Capability
The skill's name and description match the runtime instructions: it delegates Shipamax interactions to the Membrane CLI and documents actions for listing, connecting, and proxying requests to Shipamax. Nothing in the instructions asks for unrelated cloud credentials or access.
Instruction Scope
Instructions stay within the stated purpose (using Membrane to call Shipamax APIs). They require network access and a Membrane account and describe browser-based auth and a headless flow. They do not instruct the agent to read arbitrary local files or harvest unrelated environment variables. Note: the SKILL.md tells the user to install and run the Membrane CLI, which implies Node/npm must be available even though the registry metadata listed no required binaries.
Install Mechanism
This is an instruction-only skill (no install spec), but it instructs the user to run 'npm install -g @membranehq/cli' to get the CLI. Installing a global npm package is a normal approach but pulls code from the public npm registry — you should trust the @membranehq package and prefer installing from official sources or reviewing the package if you have concerns.
Credentials
The skill declares no required environment variables and explicitly advises not to ask users for API keys; authentication is handled by Membrane. There are no unrelated credentials requested in the instructions.
Persistence & Privilege
The skill does not request 'always: true' or other elevated persistence privileges and is user-invocable only. It does not instruct modifying other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to access Shipamax without asking for extra secrets. Before installing, confirm you trust the @membranehq npm package and the Membrane service (review their homepage/repo), ensure you have Node/npm to install the CLI, and prefer running installs in a controlled environment (container or VM) if you are cautious. If you need higher assurance, ask the publisher for a direct link to the exact @membranehq/cli package repository or inspect the package contents on the npm registry before running a global install. Also be aware the skill relies on network access and a Membrane account and that the agent can invoke the skill when asked (autonomous invocation is allowed by default).Like a lobster shell, security has layers — review code before you run it.
latestvk974dfza7bp4ey68dsgdxfzx2584d4sj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.