Disqo
v1.0.0Disqo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Disqo data.
⭐ 0· 54·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
high confidencePurpose & Capability
The name/description (Disqo integration) matches the instructions: all commands and examples target Disqo via the Membrane CLI. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md directs the agent/user to install and use the Membrane CLI and to create a Membrane connection that proxies requests to Disqo. This stays within the stated purpose but grants Membrane (a third party) visibility and control over requests/responses; the doc also suggests using raw proxy requests when built-in actions are insufficient, which could allow broad access to Disqo data through the connection.
Install Mechanism
There is no formal install spec in the skill bundle (instruction-only), but the runtime instructions instruct users/agents to run `npm install -g @membranehq/cli` or `npx @membranehq/cli@latest`. That is a reasonable mechanism for this integration but does write a CLI to the host if executed and relies on the npm package source (@membranehq/cli).
Credentials
The skill requests no environment variables or credentials and relies on Membrane's browser-based OAuth/connection flow for auth. Requested access is proportional to the stated function. Note: using Membrane means you are delegating credential handling to that service.
Persistence & Privilege
The skill is not marked always:true and does not claim to persist or modify other skills or global agent settings. It is user-invocable and can be invoked autonomously (platform default), which is expected.
Assessment
This skill is coherent: it uses the Membrane CLI to access Disqo and doesn't ask for unrelated secrets. Before installing or running commands: 1) Understand that installing the CLI (`npm install -g @membranehq/cli`) will add software to your system—only run it if you trust the package and its publisher. 2) Membrane acts as a proxy and will see requests/responses and hold connection credentials — review Membrane's privacy/security docs if you have concerns about third-party access to your Disqo data. 3) The skill's proxy feature allows arbitrary API calls to Disqo through Membrane, so limit use to the minimum necessary operations. 4) If you prefer not to use a third-party proxy, consider using Disqo's official API directly instead. If you want additional assurance, provide the Membrane CLI package source (npm package page or repo SHA) and a description of how Membrane stores/handles credentials; with that info I can reassess confidence or call out further risks.Like a lobster shell, security has layers — review code before you run it.
latestvk97bkqp6yz3asjca91ba71khrh8494ah
License
MIT-0
Free to use, modify, and redistribute. No attribution required.