Nyckel
v1.0.0Nyckel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nyckel data.
⭐ 0· 94·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 skill declares it integrates with Nyckel and all runtime instructions use the Membrane CLI as a proxy to Nyckel. Requesting the Membrane CLI (or using npx) and a Membrane account is consistent with that stated purpose; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
SKILL.md instructs the agent/user to install and use the Membrane CLI, log in, create connections, list actions, run actions, and proxy requests — all within the domain of interacting with Nyckel via Membrane. The instructions do not ask the agent to read arbitrary files, environment variables, or post data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the skill bundle (instruction-only), but the runtime instructions recommend installing the Membrane CLI via npm -g or using npx. Installing a global npm CLI has moderate system impact (writes to disk / changes PATH); this is expected for a CLI-based integration but worth noting. The guidance to use npx mitigates global install risk.
Credentials
The skill declares no required environment variables or credentials and explicitly recommends letting Membrane handle credentials server-side rather than requesting API keys locally. That is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always: true and has no install that makes it persist in the agent bundle. It relies on user-installed CLI tooling; it does not ask to modify other skills or system-wide agent settings.
Assessment
This skill is coherent: it uses Membrane as a proxy to Nyckel and asks you to install/use the Membrane CLI. Before installing or using it, confirm you trust Membrane (https://getmembrane.com) and review its privacy/permission model because connections will authorize access to your Nyckel account. Prefer running commands with npx rather than a global npm -g install if you want to avoid changing system state. When connecting, review the scopes/permissions requested by the connector and avoid completing authentication on shared or untrusted machines. If you need higher assurance, verify the referenced repository and Membrane CLI release on the official project pages and inspect the CLI’s behavior (what endpoints it calls, where it stores tokens) before providing access.Like a lobster shell, security has layers — review code before you run it.
latestvk97e1v1twrm24b128vkhs0yg2984hcg6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
