Educateme
v1.0.2EducateMe integration. Manage Courses, Users, Enrollments, Categories, Reviews. Use when the user wants to interact with EducateMe data.
⭐ 0· 89·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 claims to integrate with EducateMe and the SKILL.md consistently instructs the agent and user to use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests. There are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, logging in, creating a connection, running actions, and proxying requests. This is in-scope, but the doc relies on Membrane's cloud service to perform auth and proxy API calls — that means API traffic and potentially sensitive data will flow through Membrane servers (not stated in detail).
Install Mechanism
Install uses npm install -g @membranehq/cli (a public npm package). This is an expected install method but carries the usual npm-global risks: executing third-party code with global permissions. No direct downloads or obscure URLs are used.
Credentials
No environment variables, secrets, or config paths are required by the skill. The SKILL.md explicitly advises letting Membrane handle credentials rather than asking for API keys, which matches the declared requirements.
Persistence & Privilege
The skill is instruction-only, has no install spec, and is not forced always-on. It does not request persistent system privileges or modify other skills' configs.
Assessment
This skill appears to do what it says: it instructs you to install the official-looking Membrane CLI and use Membrane connectors to talk to EducateMe. Before installing: (1) verify the npm package and maintainer (@membranehq/cli) on the npm registry and the linked GitHub repo to ensure authenticity; (2) be aware that using Membrane means API calls, auth flows, and any proxied request payloads will be routed through Membrane's servers — review their privacy, data retention, and security policies (especially if handling student or sensitive data); (3) install the CLI on a non-critical/test environment first and avoid installing global packages on shared systems without approval; (4) use least-privileged/test accounts for connector auth and confirm what data the connector will access. If you need guarantees about data residency or logging, contact Membrane or prefer a direct integration that you control.Like a lobster shell, security has layers — review code before you run it.
latestvk97153sykm5h3zaqcx4fzjrv8n842fjd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.