Stackify
v1.0.2Stackify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stackify data.
⭐ 0· 91·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 (Stackify integration) matches the instructions: all commands target Membrane to create a Stackify connection, list actions, run actions, or proxy Stackify API calls. Nothing in the skill asks for unrelated cloud credentials or access.
Instruction Scope
SKILL.md confines itself to installing and using the Membrane CLI, creating connections, listing and running actions, and proxying API calls through Membrane. The instructions do not ask the agent to read unrelated files, environment variables, or system-level configurations.
Install Mechanism
There is no formal install spec in the skill bundle (it's instruction-only). The doc recommends installing @membranehq/cli via npm -g (a well-known registry). This is expected but does require the user to run a global npm install (may need elevated permissions); the skill itself does not automatically install anything.
Credentials
The skill requests no environment variables or credentials. It relies on Membrane to manage auth and tells users not to provide API keys locally; delegating auth to Membrane is coherent with the described integration. Users should still review what permissions the Membrane connector requests when authenticating.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent agent presence or attempt to modify other skills or global agent settings. The only persistence implied is the normal Membrane CLI login flow (browser auth tokens), which is standard for CLI tools.
Assessment
This skill is an instructions-only integration that tells you to install and use the Membrane CLI to talk to Stackify. Before installing/running anything: 1) Confirm you trust Membrane (https://getmembrane.com) because connectors delegate authentication to their service and will handle your Stackify tokens; 2) Be aware the doc recommends npm -g @membranehq/cli (global install may require elevated permissions)—you run that yourself; 3) When you create the connector, review the OAuth/scopes and any permissions requested; 4) The Membrane proxy can perform arbitrary Stackify API calls for the connected account, so only connect accounts you are comfortable delegating to the service. If you need more assurance, verify the npm package and repository contents before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk975km1xwvn0za5t16nry6wdq9843hcp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.