Proprofs Quiz Maker
v1.0.2ProProfs Quiz Maker integration. Manage data, records, and automate workflows. Use when the user wants to interact with ProProfs Quiz Maker data.
⭐ 0· 64·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
medium confidencePurpose & Capability
The skill claims to integrate with ProProfs and all runtime instructions use the Membrane CLI and proxy to talk to ProProfs. Asking the user to install @membranehq/cli and create a Membrane connection is proportional to the stated purpose.
Instruction Scope
SKILL.md only directs use of the Membrane CLI (login, connect, action list/run, and proxy requests). It does not instruct reading unrelated files, environment variables, or exfiltrating data. The proxy feature allows arbitrary API paths to be forwarded to ProProfs — this is expected for a generic integration but means the agent (or user) can issue arbitrary proxied requests.
Install Mechanism
The skill is instruction-only (no install spec), but it tells users to run a global npm install of @membranehq/cli. That is a third‑party package install triggered by the user (not by the skill). Installing global npm packages has modest operational risk — verify the package source and prefer non-global or sandboxed installs if concerned.
Credentials
The skill requests no local env vars and explicitly recommends letting Membrane manage credentials. This is proportionate to the described behavior, but it requires trusting Membrane as the credential holder/proxy: Membrane will see and be able to act on ProProfs data on behalf of the user.
Persistence & Privilege
The skill does not request persistent privileges (always:false) and does not modify other skills or system-wide configs. Autonomous invocation is allowed (default) — normal for skills — but not combined with elevated privileges here.
Assessment
This skill appears internally coherent, but before installing or following the SKILL.md: 1) Verify the @membranehq/cli npm package and its publisher (npm page, GitHub repo, recent releases) to ensure you trust the CLI. 2) Understand that Membrane will hold and proxy your ProProfs credentials and can access data — review Membrane's privacy/security docs and the ProProfs permissions requested. 3) Prefer installing the CLI in a user/local or sandboxed environment (avoid untrusted global installs on shared systems). 4) If you want tighter control, consider creating a least‑privilege ProProfs account for integrations. 5) If you do not trust delegating credentials to Membrane, do not follow the login/connect flow and instead use official ProProfs API credentials via your own tooling.Like a lobster shell, security has layers — review code before you run it.
latestvk971r8at6zeegfsxj5jxxr226d843c5c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.