Statuspage Io
v1.0.2Statuspage.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Statuspage.io data.
⭐ 0· 61·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
medium confidencePurpose & Capability
The name/description and runtime instructions align: the skill is an instruction-only integration that uses Membrane to call Statuspage.io. However, SKILL.md expects you to install the @membranehq/cli via npm and to have a Membrane account, but the registry metadata declares no required binaries or tools — a minor inconsistency (it should declare node/npm and the CLI requirement).
Instruction Scope
Instructions stay within the stated purpose (discover actions, run actions, or proxy requests to Statuspage.io). Important operational detail: Membrane acts as a proxy and will receive/handle authentication and proxied requests — this means Statuspage data and auth flows go through Membrane's service (getmembrane.com). That is expected for this design but is a privacy/trust consideration.
Install Mechanism
There is no install spec in the registry, but SKILL.md tells users to run `npm install -g @membranehq/cli` (and uses npx). Installing a public npm CLI is a normal pattern but introduces the usual supply-chain and privilege concerns (global npm install). The SKILL.md uses well-known package coordinates (@membranehq/cli) rather than arbitrary URLs, which lowers risk.
Credentials
The skill declares no required environment variables and instructs users to use Membrane connections rather than provide API keys locally. That is proportionate to the stated purpose. Be aware the Membrane account and connection created via the CLI will be used to store/obtain Statuspage credentials server-side.
Persistence & Privilege
The skill does not request always=true, does not require system-wide config changes in the manifest, and is instruction-only. The only persistence is the normal Membrane CLI login and connection objects created in the user's Membrane account — expected for this workflow.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Statuspage.io. Before installing/use, consider the following: (1) you'll need node/npm and will be asked to install a global npm package (@membranehq/cli) — verify the package and avoid installing global packages on sensitive or shared systems; (2) Membrane (getmembrane.com) will act as a proxy and handle your Statuspage credentials and requests — review Membrane's security/privacy policy and decide whether you trust that third party with your Statuspage data; (3) the registry metadata does not declare node/npm as required even though SKILL.md expects them — expect to install prerequisites manually; (4) if you prefer not to route credentials through a third party, consider building a direct integration that stores API keys where you control them. If these tradeoffs are acceptable, the skill is coherent and follows its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk976tq5t7vgabmam107vny8pa98425je
License
MIT-0
Free to use, modify, and redistribute. No attribution required.