Qntrl
v1.0.2Qntrl integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Qntrl data.
⭐ 0· 99·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
medium confidencePurpose & Capability
The name/description (Qntrl integration) match the runtime instructions: all actions are performed via the Membrane CLI or the Membrane proxy to Qntrl APIs. There are no unrelated credentials, binaries, or requests present that don't belong to a Qntrl integration.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in, creating/listing connections, running predefined actions, and proxying raw requests to Qntrl — all within the stated purpose. The instructions do not request reading local files or unrelated environment variables.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli` manually; that's reasonable for a CLI-based integration but means the skill depends on installing a third-party npm package and a global binary. The skill itself does not provide an automated installer.
Credentials
No environment variables or local secrets are requested by the skill, which is appropriate. However, the skill delegates authentication and credential storage to the Membrane service — so the user must entrust that external service with access to Qntrl credentials and requests.
Persistence & Privilege
The skill does not request always:true or any elevated platform persistence. Autonomous invocation is allowed by default (normal for skills) and there is no instruction to modify other skills or system-wide configs.
Assessment
This skill is coherent for talking to Qntrl via Membrane, but before installing consider: 1) you will need to install the @membranehq/cli npm package globally — ensure you trust that package and its source; 2) Membrane will act as a proxy and manage/store your Qntrl credentials/server-side, so review Membrane's privacy/security policy and trustworthiness before delegating credentials; 3) the proxy can forward arbitrary API requests to Qntrl, so avoid running destructive commands unless you understand the connection's permissions; 4) if you need higher assurance, verify the Membrane CLI package checksum or source repository and test the workflow in a sandbox account first.Like a lobster shell, security has layers — review code before you run it.
latestvk979fr7atg8pd107t6mrqm05gn8423xm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.