Stackstate
v1.0.0StackState integration. Manage data, records, and automate workflows. Use when the user wants to interact with StackState data.
⭐ 0· 53·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
The name and description (StackState integration) match the instructions which exclusively describe using Membrane to connect to StackState, discover actions, run them, and proxy API requests. Required capabilities (network access, a Membrane account) are appropriate for the stated purpose.
Instruction Scope
All instructions confine themselves to installing and using the Membrane CLI and to creating/using a connection to StackState. The skill advises the agent to proxy arbitrary StackState API requests through Membrane — this gives broad power to call any StackState endpoint, which is coherent with integration use but means the agent could make arbitrary API calls within the connected StackState account.
Install Mechanism
The skill is instruction-only (no install spec). It tells users to install @membranehq/cli via npm -g or use npx. This is an expected mechanism but does require installing a third-party global CLI package; legitimacy of that package and its supply chain should be verified by the user before installing.
Credentials
The skill requests no environment variables or local secrets and explicitly instructs not to ask users for API keys, relying on Membrane to handle auth. Requiring a Membrane account and connection is proportional to the integration purpose.
Persistence & Privilege
The skill is not marked always:true and does not request elevated or persistent system privileges. The agent may invoke it autonomously (platform default), which is normal; nothing in the skill attempts to modify other skills or global agent config.
Assessment
This skill delegates all access to StackState through the Membrane CLI. Before installing or using it: (1) verify the authenticity of the @membranehq/cli package (review the npm package page and the GitHub repo linked in the skill), (2) prefer using npx or a scoped/local install rather than a global -g install if you want to avoid modifying system-wide binaries, (3) be aware that once you create a Membrane connection the agent (or anyone with access to that connection) can make arbitrary API requests to your StackState instance via the proxy — limit the account/permissions used for the connection and audit Membrane activity if possible, and (4) if you do not want the agent to call this skill autonomously, keep it disabled or restrict model-invocation settings. Overall the skill appears consistent with its description, but exercise normal operational caution around installing third-party CLIs and granting API access.Like a lobster shell, security has layers — review code before you run it.
latestvk972abknq6mdmvavm536q4ebjs8492wx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.