Classlink
v1.0.0ClassLink integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClassLink data.
⭐ 0· 51·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (ClassLink integration) match the SKILL.md which documents using the Membrane CLI to connect to ClassLink, run proxy requests, and execute actions. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, authenticating via browser, creating a connection, listing/running actions, and proxying API requests — all relevant to interacting with ClassLink. The instructions do not ask the agent to read arbitrary local files or access unrelated environment variables.
Install Mechanism
The skill is instruction-only (no automated install spec), which is low surface risk. However the SKILL.md tells users to run `npm install -g @membranehq/cli` and suggests `npx @membranehq/cli@latest`; installing or running packages from npm (especially via npx@latest) executes remote code and is a moderate-risk action that users should review before running.
Credentials
No environment variables or external credentials are required by the skill itself; authentication is performed via Membrane's connection flow (browser OAuth). There are no unexplained requests for unrelated secrets.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges. It instructs using the Membrane CLI which will manage its own auth state server-side or in the CLI client; that is expected and proportional.
Assessment
This skill is coherent with its stated purpose, but review the Membrane CLI before installing. Practical precautions: (1) verify the @membranehq package and the getmembrane.com project reputation before running npm install or npx; prefer pinning a specific version rather than `@latest`; (2) inspect OAuth scopes and consent screens when creating the ClassLink connection — this skill deals with K–12 student data, so confirm compliance (FERPA/local rules) before connecting; (3) in headless or shared environments, avoid pasting tokens or running global installs from unverified machines; and (4) remember the registry entry contains only instructions (no packaged code here), so the security posture depends largely on the Membrane CLI and the external service you authorize.Like a lobster shell, security has layers — review code before you run it.
latestvk97f9gazgcgwn31bdwz21kx3wx84fqnw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.