Chatbase
v1.0.0Chatbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatbase data.
⭐ 0· 28·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 README describes Chatbase integration and all runtime actions (connector discovery, action execution, proxying requests) are performed via the Membrane CLI, which matches the stated purpose. Minor metadata mismatch: the skill metadata lists no required binaries even though the instructions require npm and the @membranehq/cli executable.
Instruction Scope
SKILL.md stays on-scope: it tells the agent how to install and use Membrane to connect to Chatbase, discover actions, run them, and proxy raw API calls. It requires network access and browser-based authentication, but does not instruct reading unrelated files or exfiltrating other system data.
Install Mechanism
No automated install spec is provided (instruction-only), which limits risk from hidden installers. However the skill instructs the user to run `npm install -g @membranehq/cli` (a public npm package). Installing a global CLI is a normal step but you should verify the package and publisher before installing.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The instructions explicitly delegate auth to Membrane and advise not to collect API keys locally, which is proportionate for this integration. Note: using Membrane means you trust their service to hold Chatbase credentials.
Persistence & Privilege
The skill is not always-on, does not request elevated persistence, and does not modify other skills or system-wide settings. It relies on user-run CLI commands and browser-based authentication only.
Assessment
This skill is coherent: it delegates Chatbase access to the Membrane CLI rather than asking for local API keys. Before installing: (1) verify the @membranehq/cli package and its publisher on npm/GitHub, (2) be aware that installing a global npm package requires permissions and adds a binary to your system PATH, and (3) understand that by using Membrane you are trusting a third party to hold and refresh your Chatbase credentials and to proxy API requests. If you prefer not to trust an external proxy, use direct Chatbase authentication instead. Reject or investigate further if you cannot verify the Membrane publisher or if your organization forbids third-party credential brokers.Like a lobster shell, security has layers — review code before you run it.
latestvk971ywep80egd5ncdpm31dmmcx844ys0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.