Airops

v1.0.2

AirOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AirOps data.

0· 110·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description: AirOps integration. Requirements and instructions: install Membrane CLI, authenticate, create/connect to an AirOps connector, list and run actions, or proxy API calls via Membrane. All required items align with the stated purpose.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests to AirOps. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints.
Install Mechanism
No automated install spec is included (instruction-only). The doc instructs installing @membranehq/cli via npm (-g). Using npm is expected for a CLI but installing global packages carries the usual supply-chain/trust considerations; the skill itself does not embed or download arbitrary URLs.
Credentials
The skill declares no required env vars or credentials and explicitly recommends letting Membrane handle credentials via browser-based login and connector flows. There are no disproportionate or unrelated credential requests.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent/system-wide privileges or modify other skills' config. Autonomous invocation is allowed by platform default but the skill does not combine this with broad credential access or other red flags.
Assessment
This skill is coherent: it uses the Membrane CLI to access AirOps and asks you to authenticate via Membrane (browser flow). Before installing or running it, verify you trust the @membranehq/cli npm package and the Membrane service (check the package repo, npm page, and the vendor domain). Avoid using this with highly sensitive data unless you trust Membrane's hosting and auth model; consider a least-privilege/test account for initial use. Note that the instructions install a global npm CLI and rely on browser-based authentication, and the Membrane proxy will send requests through Membrane's infrastructure — treat that like sending data to a third-party service.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b9wy49a91gvr3gjwqmrewa18433kv

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments