D2L Brightspace

v1.0.2

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

0· 93·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description align with the instructions: the skill is an integration helper that uses the Membrane CLI to talk to D2L Brightspace. It does not request unrelated credentials, binaries, or system-level access.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, creating connections, listing/ running actions, and proxying requests via Membrane. It does not instruct reading local files, environment variables, or unrelated system state.
Install Mechanism
The skill recommends installing @membranehq/cli via npm (-g). This is a standard approach but carries the usual npm/global-install considerations (package trust, permissions). No opaque download URLs or archive extraction are used.
Credentials
No environment variables or local credentials are requested by the skill. Auth is delegated to Membrane (browser-based login), which is proportionate to the stated purpose.
Persistence & Privilege
Skill is instruction-only, has no install manifest, and does not request persistent or elevated platform privileges. always is false and autonomous invocation is the platform default.
Assessment
This skill is coherent but depends on the third-party service 'Membrane' and an npm package. Before installing or using it: 1) Verify the @membranehq/cli npm package and the Membrane project (npm page, GitHub repo, maintainer) to ensure you're installing the genuine package. 2) Understand that Membrane acts as a proxy and will handle your D2L credentials and request payloads — if you will be sending student or sensitive data, confirm Membrane's privacy, security, and compliance posture (FERPA/GDPR) and review their terms. 3) Prefer using least-privilege accounts or sandbox/test instances for initial use. 4) Be aware that installing global npm packages requires elevated permissions on some machines; consider npx or scoped installs if you want to avoid a global install. If you need more confidence, ask the skill author/maintainer for the exact connector implementation and a link to the official npm/GitHub release used.

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

latestvk979a7f6yck636k8wkfgy7913x843f3n

License

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

Comments