Stacks
v1.0.2Stacks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stacks data.
⭐ 0· 78·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/description (Stacks integration) align with the instructions (use Membrane CLI to discover connections, run actions, or proxy requests to the Stacks API). Required access (network + Membrane account) is expected for this purpose.
Instruction Scope
SKILL.md stays within scope: it instructs installing and using the Membrane CLI, logging in, connecting to Stacks, listing actions, running actions, and issuing proxied API requests. One thing to note: the 'membrane request' command lets callers issue arbitrary proxied HTTP requests through Membrane, so an agent with this skill can make arbitrary API calls to the connected Stacks endpoint — this is expected for an integration but worth being aware of.
Install Mechanism
This is an instruction-only skill (no automated install spec). The doc recommends installing @membranehq/cli via npm (-g) or using npx. The npm package is a public registry package (moderate risk compared to vetted system packages). Because the skill does not auto-install, the user keeps control over whether/where to install the CLI.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The SKILL.md explicitly advises against asking the user for API keys and relies on Membrane to manage auth, which matches the declared requirements.
Persistence & Privilege
always is false and the skill does not request permanent system presence or modify other skills' configs. Normal autonomous invocation is allowed (default), which is expected for a skill of this type.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Stacks. Before installing or using it, confirm you trust Membrane (getmembrane.com/@membranehq/@membranehq/cli) because authorizing via the CLI grants Membrane access to your Stacks data. Prefer using npx or a non-global install if you want to avoid a global npm install. Review the @membranehq/cli package and its GitHub repo, and be aware that the skill enables issuing arbitrary proxied API requests through your connection (expected for integrations but a capability worth consenting to).Like a lobster shell, security has layers — review code before you run it.
latestvk97d538cybfzx8yckagjdmhned843zc2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.