Nordic Api Gateway
v1.0.0Nordic API Gateway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nordic API Gateway data.
⭐ 0· 13·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe a Nordic API Gateway integration and all instructions revolve around using the Membrane CLI to discover connectors, create connections, list actions, run actions, and proxy requests; requiring network access and a Membrane account is consistent with that purpose.
Instruction Scope
SKILL.md only instructs the agent/user to install and run the Membrane CLI, perform login flows, list/connect actions, run actions, and proxy requests. It does not ask the agent to read arbitrary local files, request unrelated credentials, or send data to endpoints outside Membrane's API proxy.
Install Mechanism
No install spec in the manifest (instruction-only skill). SKILL.md advises installing @membranehq/cli via npm (global install or npx). This is a standard public registry install; it's expected but users should treat any global npm install as a trust decision (verify package source/maintainer).
Credentials
The skill declares no required env vars or credentials and explicitly recommends letting Membrane handle auth rather than asking for API keys. That is proportionate to its role as a proxy/connector client.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges or modify other skills. It is instruction-only; any code written/executed would come from the user's explicit npm install of the Membrane CLI.
Assessment
This skill is coherent: it tells you to use the Membrane CLI to connect to Nordic API Gateway and does not request unrelated credentials. Before installing: 1) Verify the @membranehq/cli package on the npm registry and the linked GitHub repo (to ensure you trust the maintainer). 2) When completing the browser login, verify the domain shown in the auth URL is the official Membrane domain to avoid phishing. 3) Be aware that Membrane will be the party holding connector credentials and proxying requests — confirm that their security/compliance posture meets your requirements for financial data. 4) Prefer using npx (one-off) instead of a global npm install if you want to minimize persistent system changes. If you need a higher-assurance decision, provide the exact npm package URL/version and the Membrane account/tenant domain so those artifacts can be inspected.Like a lobster shell, security has layers — review code before you run it.
latestvk976az6pc13nbqwqhgv5yqxgb984gcyf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.