Stein
v1.0.2Stein integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stein data.
⭐ 0· 70·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
Name/description (Stein integration) match the runtime instructions: install/use the Membrane CLI to connect to Stein, list/run actions, and proxy requests. Nothing requested or referenced appears unrelated to the stated purpose.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI and running membrane commands (login, connect, action list/run, request). It does not ask the agent to read system files, arbitrary env vars, or exfiltrate data outside the Membrane/Stein flow.
Install Mechanism
Skill asks users to install @membranehq/cli via 'npm install -g'. That is a normal way to obtain a CLI but carries the usual npm/global install risks (code runs with installer privileges). This is proportionate to the skill's functionality but the user should verify the package's authenticity and consider using npx or a local install if preferred.
Credentials
No environment variables, secrets, or unrelated credentials are requested. The skill explicitly directs users to create connections via Membrane so the platform manages credentials server-side, which aligns with the stated purpose.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges or modification of other skills/config. It is user-invocable and uses the CLI the user installs.
Assessment
This skill is internally consistent, but before installing/run the Membrane CLI: (1) verify the npm package @membranehq/cli is the official package and review its publisher and recent versions; (2) prefer 'npx @membranehq/cli' or a local install if you want to avoid a global install; (3) when you run 'membrane login' inspect the OAuth scopes the provider asks for and confirm you're comfortable with Membrane holding the connection; and (4) only use this skill if you trust the Membrane proxying behavior—requests to Stein will be proxied through Membrane's service, so review its privacy/security docs if handling sensitive data.Like a lobster shell, security has layers — review code before you run it.
latestvk97brvm836angcg9p9f2s50xbx843e3j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
