Edusign
v1.0.0Edusign integration. Manage Documents, Templates, Users, Groups. Use when the user wants to interact with Edusign data.
⭐ 0· 61·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's name/description (Edusign integration) match the actions described: listing/creating Edusign entities via Membrane. Requiring the Membrane CLI and a Membrane account is coherent for this purpose. Minor mismatch: SKILL metadata did not declare that npm/node or the membrane binary are required, though the instructions require them.
Instruction Scope
SKILL.md confines the agent to using Membrane CLI commands (login, connect, action list/run, request proxy). It does not instruct reading unrelated files or environment variables. Note: the instructions assume npm/node availability for installing the CLI and rely on browser-based auth (or headless URL flow).
Install Mechanism
There is no formal install spec in the registry; the README instructs running 'npm install -g @membranehq/cli'. Installing a public npm package is a normal, moderate-risk step. The package is under the @membranehq scope and repository/homepage links are provided, which reduces but does not eliminate supply-chain risk — you should verify the package and publisher.
Credentials
The skill declares no required env vars or secrets and explicitly instructs not to ask users for API keys. Authentication is delegated to Membrane (server-side). Keep in mind that proxied requests and any data sent will transit through Membrane's service, so that service will have access to the exchanged data.
Persistence & Privilege
The skill is instruction-only, does not request 'always: true', and does not modify other skills or system-wide settings. It does not request persistent privileges or hidden autonomous presence beyond the platform defaults.
Assessment
This skill looks consistent with its stated purpose, but take the following precautions before installing: (1) Verify the @membranehq npm package and its publisher (check the linked GitHub repo and package maintainer). (2) Understand that Membrane acts as a proxy — your Edusign requests and data will transit Membrane's servers, so confirm you trust that service and its privacy terms. (3) Ensure you install npm packages from a trusted environment (or inspect the package source) and that you are comfortable using browser-based OAuth flows the CLI triggers. (4) If you need stronger assurance, review the Membrane CLI source code or run the CLI in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97fffnzby6j8b0640e15dzeps83km35
License
MIT-0
Free to use, modify, and redistribute. No attribution required.