Ispring Learn
v1.0.2iSpring Learn integration. Manage data, records, and automate workflows. Use when the user wants to interact with iSpring Learn data.
⭐ 0· 56·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 are an iSpring Learn integration and the instructions exclusively describe using the Membrane CLI to connect to and proxy requests to iSpring Learn — this is proportionate and expected.
Instruction Scope
SKILL.md only tells the agent to install and use the Membrane CLI, authenticate via the browser flow, list/connect actions, run actions, or proxy API requests. It does not instruct reading unrelated files, requesting unrelated environment variables, or exfiltrating data outside Membrane/iSpring Learn.
Install Mechanism
The skill is instruction-only and recommends installing @membranehq/cli via 'npm install -g'. That is a reasonable dependency for the described workflow, but global npm installs run third‑party code on your machine — verify package origin and version before installing, or prefer ephemeral (npx) or containerized installs if you are cautious.
Credentials
The skill declares no environment variables or credentials and explicitly instructs not to ask users for API keys, relying on Membrane to manage auth. This is proportionate to the stated integration purpose.
Persistence & Privilege
The skill does not request 'always' presence and contains no instructions to modify other skills or system-wide agent settings. It relies on the CLI and the user's interactive login flow, which is standard for this class of integration.
Assessment
This skill appears coherent: it uses the Membrane CLI to manage iSpring Learn connections and does not request unrelated credentials. Before installing: (1) verify the @membranehq/cli package name, publisher, and version on npm (or use 'npx' to avoid a global install); (2) review Membrane's privacy/security docs to understand what data is proxied to their service (the proxy flow will send request paths and payloads to Membrane); (3) perform installs in a controlled environment (container or VM) if you are concerned about running third‑party CLI code; and (4) confirm the Membrane homepage/repo (getmembrane.com / github.com/membranedev/application-skills) are legitimate and match the package you install.Like a lobster shell, security has layers — review code before you run it.
latestvk977kr53j0zjr3zkbda4gh3v2d842erk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.