Uchat
v1.0.0Uchat integration. Manage data, records, and automate workflows. Use when the user wants to interact with Uchat data.
⭐ 0· 59·0 current·0 all-time
byMembrane Dev@membranedev
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 (Uchat integration for data/workflows) match the instructions, which use the Membrane CLI to create a connector, list/run actions, and proxy requests to Uchat. No unrelated credentials, binaries, or paths are requested.
Instruction Scope
SKILL.md confines the agent to installing and using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests via Membrane. It does not instruct reading arbitrary local files, accessing unrelated environment variables, or sending data to unknown endpoints outside Membrane/Uchat.
Install Mechanism
The skill is instruction-only (no install spec). It recommends installing @membranehq/cli via npm -g, which is a normal but potentially sensitive step because global npm installs execute third-party code. No automated downloads or obscure URLs are present in the skill itself.
Credentials
No environment variables or credentials are required by the skill. It explicitly delegates auth to Membrane and advises against asking users for API keys, which is proportionate for this integration.
Persistence & Privilege
The skill does not request always:true, does not alter other skills or system-wide configs, and is user-invocable. Autonomous invocation is allowed by default but not combined with other concerning privileges.
Assessment
This skill appears coherent and uses the Membrane CLI to access Uchat. Before installing or running commands: 1) Confirm you trust getmembrane.com and @membranehq/cli (review the npm package and the GitHub repo). 2) Remember a global npm install runs third-party code—install in a controlled environment if concerned. 3) When you run membrane login/connect, pay attention to the browser consent screens and the scopes requested by the connector so you know what data Membrane will access. 4) Do not provide unrelated credentials; follow the skill's advice to let Membrane manage auth. If you need higher assurance, audit the Membrane CLI code or run it on an isolated machine or container.Like a lobster shell, security has layers — review code before you run it.
latestvk97b0zhm09zjktvs6s6bch4rjx84b672
License
MIT-0
Free to use, modify, and redistribute. No attribution required.