Statuspage
v1.0.2Statuspage integration. Manage Incidents, Metrics, Pages, ScheduledMaintenances. Use when the user wants to interact with Statuspage data.
⭐ 0· 89·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 are a Statuspage integration and the SKILL.md exclusively describes using the Membrane CLI to discover and run Statuspage-related actions and proxy requests. Required credentials, files, and binaries are not requested by the skill itself, which matches its stated purpose.
Instruction Scope
Instructions focus on installing and using the Membrane CLI (login, connect, action list/run, proxy requests). They do not ask to read unrelated files or environment variables. Note: the workflow requires interactive browser-based auth or a headless code-complete flow, which is expected but involves the user completing auth in their browser.
Install Mechanism
No install spec in the skill bundle (instruction-only). SKILL.md recommends installing @membranehq/cli via 'npm install -g' and also shows using 'npx' in examples — both are reasonable for a CLI, but installing global npm packages carries normal supply-chain/privilege risks. This is proportionate to the task but the user should trust the Membrane package and source.
Credentials
The skill declares no environment variables, no credentials, and no config paths. It explicitly instructs not to ask users for API keys and to let Membrane handle credentials, which is consistent and minimal for this integration.
Persistence & Privilege
always:false and the skill is user-invocable with normal autonomous invocation allowed. It does not request persistent system-wide config changes or elevated privileges. This level of presence is appropriate for an integration that uses an external CLI.
Assessment
This skill delegates all auth and API calls to the Membrane CLI. That design is internally consistent, but before installing or running commands: 1) verify you trust the Membrane project/vendor (review the GitHub repo and the npm package if you plan to install globally); 2) prefer using 'npx @membranehq/cli@latest ...' for one-off runs instead of a global 'npm install -g' to reduce supply-chain/permission risk; 3) be prepared to complete browser-based authentication (or use the headless code flow) and avoid pasting your own API keys into agent prompts; 4) confirm your organization is comfortable with Membrane acting as the proxy for Statuspage requests, since it will handle and store auth on your behalf. If you need higher assurance, review Membrane's docs/privacy and audit the CLI source before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97bhzq2vgvw2nzbc549gtqsyn843g5t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.