Instruqt
v1.0.2Instruqt integration. Manage data, records, and automate workflows. Use when the user wants to interact with Instruqt data.
⭐ 0· 70·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 name/description (Instruqt integration) match the instructions (use Membrane CLI to connect to Instruqt, list/run actions, proxy API calls). Required network access and a Membrane account are coherent with the stated purpose.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the Membrane CLI, log in (opens a browser for OIDC-like auth), create/list connections, run actions, and proxy raw requests to the Instruqt API. These steps stay within the integration's scope, but they do instruct installing a global npm package and performing interactive auth flows which will grant Membrane access to downstream services.
Install Mechanism
There is no formal install spec in the skill metadata, but the README directs users to run 'npm install -g @membranehq/cli' and use npx in examples. Installing a global npm CLI is a normal approach but has moderate risk compared to an instruction-only skill because it writes binaries to the system and requires trust in the @membranehq package.
Credentials
The skill does not request any environment variables, credentials, or config paths. The instructions explicitly say not to ask users for API keys and to let Membrane manage credentials server-side, which is proportionate to the purpose.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. It is user-invocable and would rely on runtime invocation of Membrane CLI commands; no elevated platform privileges are requested.
Assessment
This skill is coherent: it delegates auth and API calls to the Membrane CLI rather than asking for local secrets. Before installing/using it: 1) confirm the CLI package scope (@membranehq) is the official publisher and review the npm package page; 2) understand that logging in grants Membrane access to Instruqt on your behalf — review what scopes/permissions you approve during the browser auth flow; 3) installing a global npm package modifies your system PATH and requires appropriate privileges — install only if you trust the publisher; 4) the agent will run membrane commands (including proxy requests) that may transmit Instruqt data to Membrane, so verify Membrane's privacy/security practices. If you want lower friction, you can run the membrane CLI yourself rather than giving the agent autonomous access to it.Like a lobster shell, security has layers — review code before you run it.
latestvk979mb0f30d296j57m5zs4pq11842e61
License
MIT-0
Free to use, modify, and redistribute. No attribution required.