Embrace
v1.0.2Embrace integration. Manage data, records, and automate workflows. Use when the user wants to interact with Embrace data.
⭐ 0· 80·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 (Embrace integration) matches the instructions: the SKILL.md explains how to install and use the Membrane CLI to connect to Embrace and run/query actions. No unrelated services, env vars, or binaries are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests. Note: proxied requests and auth are handled by Membrane’s servers, so using this skill sends Embrace traffic and metadata to the Membrane service (this is expected but important for user privacy/trust).
Install Mechanism
This is an instruction-only skill with no install spec; it tells the user to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a normal approach but does execute third-party code from the npm registry — users should ensure they trust the package and understand global installs modify the system environment.
Credentials
The skill declares no required env vars, no config paths, and no credentials. The SKILL.md explicitly says to let Membrane handle credentials rather than asking for API keys locally, which is consistent and proportionate.
Persistence & Privilege
The skill does not request always-on presence or elevated privileges. It is user-invocable and relies on the Membrane CLI at runtime; nothing in the skill attempts to modify other skills or system-wide agent settings.
Assessment
This skill appears coherent and does what it says: use the Membrane CLI to access Embrace. Before installing, confirm you trust the Membrane project (@membranehq on npm and https://getmembrane.com) because the CLI will run on your machine and proxy requests (including auth tokens) through Membrane’s servers. Prefer installing the CLI in a controlled environment, review its npm package page/repo, and, if concerned about data exposure, test with a limited Embrace account/permissions. If you need to avoid third-party proxies, consider using Embrace’s API directly (which would require different credentials and code).Like a lobster shell, security has layers — review code before you run it.
latestvk97f7a2ryyc98sh2qtyxkq3h89843yqq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.