Lyanthe

v1.0.0

Lyanthe integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lyanthe data.

0· 31·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the SKILL.md consistently instructs the agent to use the Membrane CLI to manage Lyanthe data. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions stay within the stated purpose (install Membrane CLI, login, create connections, list/run actions, proxy requests). Important: proxying and actions route requests through Membrane's servers — any request payloads and responses will traverse a third-party service, which may expose data to Membrane.
Install Mechanism
No install spec in the registry, but SKILL.md recommends installing @membranehq/cli via npm (npm install -g or npx). Using npm is a common, traceable install method. User should still verify the package source before global installation.
Credentials
The skill requests no environment variables, no local config paths, and no credentials. It purposely delegates auth to Membrane (documented). This is proportionate for a connector that relies on a hosted proxy service.
Persistence & Privilege
Skill is instruction-only, always:false, and does not request persistent agent-wide privileges or modify other skills. It will not be force-included in every agent run.
Assessment
This skill appears coherent and implements Lyanthe access by directing you to install and use the official Membrane CLI. Before installing/using it: (1) Verify you trust Membrane/getmembrane.com and the @membranehq/cli NPM package (review the package and repository), since API calls and payloads will be proxied through Membrane’s servers; avoid sending highly sensitive data unless you accept that. (2) Global npm installs require elevated permissions on some systems—consider using npx or a controlled environment. (3) The skill does not ask for local secrets, but it does rely on browser-based authentication; follow your organization’s policy for third‑party integrations. If you need tighter control over data flow, consider a direct Lyanthe integration instead of a proxying service.

Like a lobster shell, security has layers — review code before you run it.

latestvk976dmdmx953je7jfbmcd24gqs847yy9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments