Statusio
v1.0.0Status.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Status.io data.
⭐ 0· 61·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Status.io integration) aligns with the instructions: all commands interact with Status.io via the Membrane CLI/proxy. Asking users to install the Membrane CLI and create a connector is coherent with the stated purpose.
Instruction Scope
SKILL.md only instructs the agent to run Membrane CLI commands, create/list connections, run actions, or proxy requests through Membrane. It does not instruct reading unrelated files, environment variables, or posting data to third-party endpoints outside Membrane/Status.io.
Install Mechanism
No automated install spec is bundled (instruction-only). The doc tells users to install the Membrane CLI via `npm install -g @membranehq/cli`. This is a standard approach but means a global npm package and a network download are required; that is expected for a CLI-based integration but worth noting for users who audit installed binaries.
Credentials
The skill declares no required env vars, no primary credential, and relies on Membrane to handle auth. There are no disproportionate credential requests or unrelated secrets requested by the instructions.
Persistence & Privilege
Skill is not always-on and does not request persistent system-level changes. It does not modify other skills' configs or require elevated privileges. Autonomous model invocation is allowed (default) but not combined with other concerning factors.
Assessment
This skill is instruction-only and reasonably scoped: it asks you to install and use the Membrane CLI which will manage authentication to Status.io. Before installing, verify you trust the Membrane project (check the package and the repo), and understand that `npm install -g` will add a global binary. When creating a connector you will grant Membrane access to your Status.io account—review connector scopes/permissions in Membrane. If you have strict security policies, consider running the CLI in an isolated environment or reviewing Membrane's privacy/security documentation first.Like a lobster shell, security has layers — review code before you run it.
latestvk971v9qk22xa1mhzfwn1npwzs5845cb3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.