Edlink

v1.0.0

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

0· 67·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Edlink integration) match the instructions: the skill consistently instructs the agent to use the Membrane CLI to discover connections, run actions, and proxy requests to Edlink. Required capabilities (network access and a Membrane account) are reasonable and proportional.
Instruction Scope
SKILL.md confines actions to installing/using the Membrane CLI, performing browser-based login, listing/connecting actions, running actions, and proxying requests to Edlink. It does not instruct reading unrelated files, environment variables, or secret exfiltration; it explicitly recommends not asking users for API keys.
Install Mechanism
The install instruction recommends `npm install -g @membranehq/cli`. That's a standard public npm package install (moderate risk): it installs code globally and requires package trust/permission. No opaque downloads or extract steps are used, but installing any global npm package should be reviewed.
Credentials
No environment variables or unrelated credentials are requested. However, the skill relies on Membrane to handle auth and proxies requests through Membrane's servers — users must trust that third party with Edlink/student data and account tokens.
Persistence & Privilege
The skill does not request persistent/system-wide privileges (always:false). It is instruction-only and does not attempt to modify other skills or system configuration beyond recommending a global CLI install.
Assessment
This skill appears to do what it says: it instructs the agent to use the Membrane CLI to talk to Edlink. Before installing, consider: (1) reviewing the @membranehq/cli package source or repository to confirm you trust it (global npm installs run code on your system), (2) understanding that requests and credentials will be proxied through Membrane — confirm this meets your privacy/compliance needs for student data, and (3) optionally using npx (or installing locally) instead of a global install if you want to reduce system-wide changes. If you need higher assurance, ask the publisher for a reproducible release (GitHub release tarball or signed binaries) and review Membrane's privacy/security documentation.

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

latestvk97c94qwrmr7fgf8qek65qrzas843xrg

License

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

Comments