Harperdb
v1.0.0HarperDB integration. Manage data, records, and automate workflows. Use when the user wants to interact with HarperDB data.
⭐ 0· 54·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
The skill description (HarperDB integration) matches the runtime instructions: it uses the Membrane CLI to discover connectors, create a connection, run actions, and proxy API requests to HarperDB. The operations requested (queries, update, delete, proxying) are expected for a DB integration.
Instruction Scope
Instructions direct the agent/operator to install and use the Membrane CLI, log in via a browser flow, list connections/actions, run actions, and proxy arbitrary HarperDB API calls through Membrane. This is within scope for the advertised purpose, but proxying arbitrary endpoints means data and request payloads will be routed through Membrane's servers—users should expect that Membrane will observe proxied requests and any data sent.
Install Mechanism
There is no formal install spec in the registry metadata (instruction-only), but SKILL.md tells users to install @membranehq/cli via npm (global install or npx). That's a standard, low-risk recommendation. It would be clearer if required binaries field listed the CLI. Verify the npm package identity and source before installing in sensitive environments.
Credentials
The skill declares no required environment variables or credentials and does not ask for local API keys; instead it relies on Membrane-managed connections and an interactive login. That is proportionate to the stated functionality. Note: using Membrane delegates auth/credentials to a third party.
Persistence & Privilege
The skill is instruction-only, does not request persistent presence (always: false), and does not modify other skills or system-wide settings. It relies on user-driven CLI login and connections, which is normal.
Assessment
This skill is internally consistent: it expects you to install and use the Membrane CLI and to authenticate to Membrane, which will then proxy requests to your HarperDB instance. Before installing or using it: 1) Confirm you trust Membrane (getmembrane.com) because proxied requests and credentials are handled server-side and Membrane will see request payloads; avoid sending highly sensitive data unless you accept that. 2) Verify the npm package @membranehq/cli on the npm registry (publisher, homepage, integrity) before a global install or use npx for one-off runs. 3) Expect interactive browser-based login flows; the skill does not request local secrets, so do not provide HarperDB credentials into the skill itself. If you need offline or self-hosted operation or must keep data entirely within your environment, consider alternatives that connect directly to HarperDB without a third-party proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk97ekysv16p65df12nt8fy3kq9844yz9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.