Clientary
v1.0.2Clientary integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clientary data.
⭐ 0· 87·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
medium confidencePurpose & Capability
The skill is explicitly a Clientary integration and all runtime instructions use the Membrane CLI to operate on Clientary — this is coherent. However, the registry metadata lists no required binaries while the SKILL.md requires npm/node (to install the Membrane CLI) and the presence of the 'membrane' CLI at runtime; the missing declaration is an inconsistency to be aware of.
Instruction Scope
SKILL.md confines actions to installing/using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests to Clientary. It does not instruct reading unrelated files or exfiltrating environment variables. It does require network access and a Membrane account — meaning you will delegate auth to Membrane.
Install Mechanism
There is no automated install spec in the skill bundle; the instructions tell users to run 'npm install -g @membranehq/cli'. That is an npm registry install (traceable) — a moderate-risk, common mechanism. The SKILL.md assumes npm/node are available but the skill metadata did not declare those binaries.
Credentials
The skill requests no environment variables or local credentials and explicitly tells implementers not to ask users for API keys, relying on Membrane for server-side auth. This is proportionate, but it means you must trust Membrane with access and credential management for your Clientary account.
Persistence & Privilege
The skill does not request permanent/always-on presence (always: false) and does not modify other skills or system-wide settings. Autonomous invocation is allowed (default) but that is normal and expected.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to talk to Clientary. Before installing: (1) confirm you have Node/npm or are willing to install them (SKILL.md assumes this but metadata omitted it); (2) verify the @membranehq/cli package and getmembrane.com are trustworthy for your environment; (3) be aware that using the skill delegates auth to Membrane — you will be granting a third-party service access to your Clientary data, so review their privacy/security posture and OAuth scopes during the connect flow; (4) check the Membrane CLI's permissions and the exact connector scopes when you authenticate. If you require stricter data control, prefer direct Clientary API credentials and verify whether Membrane's proxy behavior meets your security requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk97bxv5n9y90vx3jc1kd3d7ymn8426mc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.