Airship
v1.0.0Airship integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airship data.
⭐ 0· 52·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 name and description match the SKILL.md: it integrates with Airship via the Membrane platform. Requested actions (connect, list actions, proxy requests) are coherent for this purpose. One minor mismatch: the registry metadata lists no required binaries, but the runtime instructions explicitly require installing the `membrane` CLI (npm global package).
Instruction Scope
Instructions stay within the stated purpose: they direct the agent to install and use the Membrane CLI, perform connector discovery, run actions, and proxy API requests through Membrane. They do not instruct reading local unrelated files or asking for unrelated credentials. Important operational note: using the proxy sends request data through Membrane servers (including headers/body) and the CLI will perform browser-based auth and persist credentials locally — a privacy/trust consideration rather than a technical inconsistency.
Install Mechanism
This is an instruction-only skill; it suggests installing @membranehq/cli via npm (a standard public registry install). There is no hidden download URL or extract step. The registry metadata did not declare the `membrane` binary as required, which is a small documentation gap.
Credentials
No environment variables or external credentials are requested by the skill; instead it relies on Membrane to manage credentials. This is proportional. Users should note that the Membrane account used will be able to access connected integrations (Airship and potentially others) and that the CLI stores tokens locally.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request elevated platform privileges. Autonomous model invocation is allowed (platform default) — that would permit the agent to call Membrane actions if invoked, but this is expected behavior for a connector skill.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to access Airship and routes requests through Membrane. Before installing, consider: (1) You will be asked to install @membranehq/cli globally (npm install -g) — this writes a binary to your environment and may require elevated permissions. (2) The CLI opens a browser for auth and stores tokens locally; anything the CLI proxies (request bodies, headers) will transit and be visible to Membrane — use an account you trust and review Membrane's privacy/security docs. (3) The registry metadata omitted the required binary (membrane); that's a documentation gap but not malicious by itself. If you need tighter isolation, create a dedicated Membrane account for this integration or run the CLI in a controlled environment (container or VM).Like a lobster shell, security has layers — review code before you run it.
latestvk97cr0nsj8ma9afmw7n8dw931h84cwaz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.