Statuspage

Statuspage integration. Manage Incidents, Metrics, Pages, ScheduledMaintenances. Use when the user wants to interact with Statuspage data.

This skill appears coherent for managing Statuspage via the Membrane service, but before installing/using it: 1) Understand and accept that Membrane (a third party) will mediate authentication and have access to your Statuspage data—review its privacy/security docs and OAuth scopes. 2) Prefer running commands with npx (npx @membranehq/cli@latest ...) to avoid a global npm install, or inspect the package source on the Membrane GitHub and the published npm package before installing. 3) When authenticating, verify the URLs and redirect targets the login flow uses and only complete auth in trusted browsers/sessions. 4) If you need higher assurance, audit the Membrane CLI repo and published package (checksums/signatures) or configure Statuspage API keys with minimal scopes and audit tokens after use.

Type: OpenClaw Skill Name: statuspage Version: 1.0.3 The skill facilitates Statuspage management by instructing the agent to install and use a third-party CLI tool (`@membranehq/cli`). It requires high-risk operations including global NPM package installation, shell-based authentication, and the dynamic creation of remote actions via the Membrane platform (`membrane action create`). While these capabilities are aligned with the stated purpose of the integration, the requirement for global system changes and reliance on external binary execution for logic orchestration meets the criteria for a suspicious classification. (IOCs: getmembrane.com, @membranehq/cli)