Nylas
v1.0.0Nylas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nylas data.
⭐ 0· 57·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 claim Nylas integration and all instructions exclusively use the Membrane CLI to connect to Nylas and run actions; required network access and a Membrane account are consistent with that purpose.
Instruction Scope
SKILL.md contains concrete CLI commands (install, login, connect, action list/run, request proxy) limited to interacting with Membrane and Nylas. It does not instruct reading unrelated files, environment variables, or system configuration outside the Membrane workflow.
Install Mechanism
There is no formal install spec in the registry (skill is instruction-only) but the README tells users to install @membranehq/cli via npm -g or npx invocation. This is expected for a CLI-based integration but means the security of the skill depends on the upstream Membrane CLI package — users should verify the package source and trustworthiness before installing globally.
Credentials
The skill declares no required env vars or credentials and explicitly recommends letting Membrane handle auth rather than asking for API keys. The auth flow described (browser-based login and connection creation) is proportional to the integration's needs.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and is user-invocable only. It relies on the Membrane CLI storing/handling credentials locally/server-side as expected.
Assessment
This skill is instruction-only and appears coherent: it expects you to use the Membrane CLI to connect to Nylas and does not ask for unrelated credentials. Before installing or running anything, verify the @membranehq/cli npm package and the Membrane service (homepage/repository) are trustworthy, avoid installing global packages as root on shared systems, and be aware that Membrane will act as a proxy (requests go through their servers and they handle auth). If you need higher assurance, review Membrane's privacy/security docs and install the CLI in a controlled environment (container or VM) first.Like a lobster shell, security has layers — review code before you run it.
latestvk97a2v0xhysnsd6zt68p8k67k184ajcj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.