Splynx
v1.0.2Splynx integration. Manage data, records, and automate workflows. Use when the user wants to interact with Splynx data.
⭐ 0· 92·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 declares Splynx integration and all runtime instructions center on using the Membrane CLI to connect to Splynx, discover actions, and proxy API requests — which is consistent with the described purpose.
Instruction Scope
SKILL.md stays on-topic: it tells the agent/operator to install and use the Membrane CLI, authenticate via browser, list/connect actions, run actions, and proxy API calls. It does not instruct reading unrelated files, environment variables, or posting data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no install spec), but it instructs the user to install @membranehq/cli via npm (global install). That is expected for this integration. Reminder: npm package installation runs code on install — choose trusted registries and consider using npx or local installs if you prefer lower-risk deployment.
Credentials
The skill requests no environment variables or local credentials, and explicitly tells users not to provide API keys. However, it routes Splynx authentication and proxied requests through Membrane's service/CLI, meaning Membrane (and its hosted service) will see and manage Splynx credentials and proxied data — this is proportionate to the integration but requires trust in Membrane.
Persistence & Privilege
The skill does not request always:true, does not request system paths or cross-skill config changes, and is user-invocable. It does not ask for persistent privileges beyond installing a standard CLI.
Assessment
This skill is coherent for integrating with Splynx via Membrane. Before installing: confirm you trust Membrane as a third party (they will handle and see Splynx credentials and proxied data); review Membrane's privacy/security docs and the @membranehq/cli package source if that matters; prefer npx or a local install instead of a global npm install if you want less system-wide change; test with non-sensitive data first; and be aware that commands open a browser-based auth flow (headless flows require careful handling of codes). If you need your Splynx data never to leave your infrastructure, do not use a hosted proxy service.Like a lobster shell, security has layers — review code before you run it.
latestvk9747gshp0rvz567etm80t3br9843qn8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.