Riddle Quiz Maker

v1.0.0

Riddle Quiz Maker integration. Manage Quizs, Users, Categories. Use when the user wants to interact with Riddle Quiz Maker data.

0· 59·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Riddle Quiz Maker integration) match the instructions: installing and using the Membrane CLI to discover connections/actions and proxy API calls to Riddle. No unrelated credentials, binaries, or filesystem paths are requested.
Instruction Scope
Instructions are limited to installing the Membrane CLI, logging in, creating/using a connector, listing and running actions, and proxying API requests. This stays within the integration's scope. Note: proxying allows arbitrary requests to the Riddle API through Membrane, so users should avoid sending sensitive local data via those requests.
Install Mechanism
No install spec in the skill package itself; the doc instructs a global npm install (npm install -g @membranehq/cli). Installing a global npm package is a normal path but does carry standard risks (trusting the package/publisher, global binary in PATH).
Credentials
The skill requests no environment variables or local config paths. Authentication is delegated to Membrane (browser-based login / headless flow), which is proportionate to the stated purpose.
Persistence & Privilege
Skill is instruction-only, not always-enabled, and does not request persistent or elevated platform privileges. It does not modify other skills or system-wide agent settings.
Assessment
This skill is an instruction-only helper that tells you to install and use the Membrane CLI to manage a Riddle Quiz Maker connection. Before following it: 1) Verify you trust the @membranehq/cli package and its publisher (check npm page, GitHub repo, and recent releases) before running npm install -g; global installs add a binary to your PATH. 2) Understand that Membrane will handle credentials server-side and open a browser for authentication — the skill itself does not ask for API keys. 3) Be cautious when using the 'membrane request' proxy: it will send arbitrary API calls through Membrane, so avoid sending sensitive local data or secrets in those requests. 4) If you operate in a high-security environment, review Membrane's privacy/security documentation and consider using an isolated environment for experimentation.

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

latestvk97egehq91cjf9gejv1m6abeph83jbbp

License

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

Comments