Treezor
v1.0.0Treezor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Treezor data.
⭐ 0· 62·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 skill describes integrating with Treezor and instructs the agent to use the Membrane CLI to create connections, list actions, and proxy API requests. Requiring a Membrane account and CLI is coherent with the declared purpose; no unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md stays on-topic: it tells the agent to install/use the Membrane CLI, login, create or find a Treezor connection, list actions, run actions, and proxy requests. It does not instruct reading arbitrary host files, harvesting environment variables, or exfiltrating data to third-party endpoints outside Membrane/Treezor.
Install Mechanism
There is no automated install spec, but the instructions recommend a global npm install (npm install -g @membranehq/cli) and occasional npx usage. Installing an npm package is a normal step for a CLI, but it involves pulling code from the public npm registry — a moderate-risk action that users should perform knowingly (verify package identity, consider using npx or a scoped/containerized environment to avoid global installs).
Credentials
The skill does not declare or require any environment variables or credentials; it instructs use of Membrane-managed connections so the skill itself does not ask for API keys or unrelated secrets. This is proportionate to the task of integrating with Treezor via Membrane.
Persistence & Privilege
The skill is user-invocable and allows normal autonomous invocation (disable-model-invocation is false), which is standard. Notably, once the Membrane connection exists the agent (if permitted to run CLI commands) could execute actions that interact with financial data via Treezor — users should be aware of that operational capability before allowing autonomous runs.
Assessment
This skill appears internally consistent: it uses the Membrane CLI to proxy requests to Treezor and does not ask for unrelated credentials. Before installing or running it, verify the @membranehq/cli package source (or prefer npx to avoid a global install), confirm you trust the Membrane service and its authorization scopes, and be mindful that once a connection is created the agent (if allowed to execute CLI commands) can perform actions against your Treezor account (including write actions like transfers/payouts). If you need stricter controls, restrict agent autonomy or test in an isolated environment/account first.Like a lobster shell, security has layers — review code before you run it.
latestvk973vqn97qmr6dtf1e3khj1a49844jyp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.