Icinga
v1.0.0Icinga integration. Manage data, records, and automate workflows. Use when the user wants to interact with Icinga data.
⭐ 0· 59·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
Name/description match the runtime instructions: all actions are performed via the Membrane CLI and the skill is explicitly for interacting with Icinga. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md confines itself to using membrane CLI commands (login, connect, action list/run, request proxy). It does not instruct reading arbitrary local files, harvesting unrelated environment variables, or sending data to third-party endpoints other than Membrane (which is the intended proxy).
Install Mechanism
The instructions recommend installing @membranehq/cli globally via npm (npm install -g). This is an ordinary installation method for a CLI, but it does execute code from the public npm registry — users should verify the package source/repository and be comfortable installing global npm packages.
Credentials
The skill requests no local credentials or environment variables. Instead it relies on a Membrane account and browser-based login; that centralizes Icinga credentials on Membrane's service. This is proportionate to the stated purpose but requires trusting Membrane with access to your Icinga data.
Persistence & Privilege
The skill does not request permanent/autonomous platform privileges (always is false). There is no install spec in the registry and no modification of other skills or system-wide agent settings.
Assessment
This skill is coherent: it uses the Membrane CLI to proxy requests to Icinga rather than asking for API keys locally. Before installing or using it, verify you trust the Membrane service and the @membranehq/cli package (review the npm package and the GitHub repo referenced). Installing a global npm CLI runs code on your machine — if you prefer, run it in a sandboxed environment or container. Understand that Membrane will hold and use credentials to access your Icinga instance (server-side credential handling); if you need stricter control over secrets, consider connecting directly to Icinga using your own tooling or reviewing Membrane's security/privacy docs first.Like a lobster shell, security has layers — review code before you run it.
latestvk974w22zzt341xenzb6c6cf3dh84bj99
License
MIT-0
Free to use, modify, and redistribute. No attribution required.