Couchbase
v1.0.0Couchbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Couchbase data.
⭐ 0· 88·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
Name/description match the instructions: the SKILL.md describes using Membrane to connect to Couchbase and manage data. The declared compatibility (network + Membrane account) aligns with the workflow.
Instruction Scope
Runtime instructions are limited to installing/running the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests. The doc does not instruct reading unrelated local files, broad environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no registry-level install spec (skill is instruction-only). The SKILL.md recommends installing @membranehq/cli via npm (-g). Installing a global npm package is a standard but non-trivial action (it fetches code from the public npm registry) — reasonable for this purpose but users should be aware they are installing third-party software.
Credentials
The skill does not declare or request environment variables or credentials. It relies on Membrane-managed auth (browser-based login and server-side token handling), which is proportionate to a connector-style integration.
Persistence & Privilege
Skill is not always-enabled, does not request system-level persistence, and does not instruct modifying other skills or system-wide configs. Autonomous invocation by the agent is allowed (platform default) but is not combined with broad privileges here.
Assessment
This skill is coherent: it expects you to use the Membrane CLI and a Membrane account to access Couchbase. Before installing the CLI, decide whether you trust the Membrane project and review the @membranehq/cli package (source repo, maintainers, recent releases). Installing a global npm package runs third-party code on your machine — if you prefer, run the CLI via npx each time instead of global install. Verify any browser-based login completes with the official Membrane pages and avoid pasting secrets into chat. If you need higher assurance, inspect the CLI source or create a limited Membrane account/connection for testing.Like a lobster shell, security has layers — review code before you run it.
latestvk97acfkk7f7qd6prew4mj9ytp584gh42
License
MIT-0
Free to use, modify, and redistribute. No attribution required.