Nabla
v1.0.0Nabla integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nabla data.
⭐ 0· 49·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 (manage Nabla data/workflows) matches the runtime instructions: it directs the agent/user to install and use the Membrane CLI to create connections, list/run actions, and proxy API requests to Nabla. No unrelated services, env vars, or binaries are requested.
Instruction Scope
SKILL.md strictly instructs installing membrane CLI, logging in via browser, creating/listing connections, running actions, and proxying requests. It does not instruct reading unrelated files, asking for secrets in-chat, or sending data to unexpected endpoints. All actions align with interacting with Nabla through Membrane.
Install Mechanism
There is no registry install spec; the SKILL.md tells the user to run `npm install -g @membranehq/cli`. Installing a CLI from the public npm registry is a common pattern but carries the usual moderate risk of installing global packages—verify the package, publisher, and version before running, and avoid unnecessary elevated privileges.
Credentials
The skill declares no required env vars or local credentials and relies on Membrane's browser-based login and server-side credential management, which is proportionate. However, the integration grants access to potentially sensitive health records via your Membrane/Nabla account—ensure the account used has appropriate permissions and that you understand Membrane/Nabla data handling policies.
Persistence & Privilege
The skill does not request always:true, does not include install-time auto-install behavior, and does not modify other skills or system-wide configuration. Model invocation is allowed (platform default) but that is expected for skills.
Assessment
This skill is instruction-only and coherent: it asks you to install and use the official Membrane CLI to access Nabla. Before proceeding: (1) verify the npm package (@membranehq/cli) and its publisher/repo and avoid running installs with unnecessary privileges; (2) use a Membrane/Nabla account with least privilege because this integration can access sensitive health data; (3) never paste API keys, tokens, or patient data into chat — use the browser-based login as instructed; (4) review Membrane and Nabla privacy/security docs and your organizational policies for handling PHI; (5) when testing, prefer a non-production account and confirm actions the CLI will perform (list/run/request) before executing them.Like a lobster shell, security has layers — review code before you run it.
latestvk9754px4dnpb0jhgd0m79x355d84epzw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.