Robomq

v1.0.0

RoboMQ integration. Manage data, records, and automate workflows. Use when the user wants to interact with RoboMQ data.

0· 55·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 match the instructions: the skill explains how to access RoboMQ via the Membrane CLI. Required capabilities (network access, Membrane account, Membrane CLI) are appropriate for this purpose.
Instruction Scope
Instructions stay within integration scope (install Membrane CLI, run membrane login, connect, list actions, proxy requests). One important operational detail: the instructions route API calls through Membrane's proxy, so request and authentication data will transit Membrane's service — this is expected for this integration but is a privacy/third-party-transit consideration the user should understand.
Install Mechanism
No platform install spec is present (instruction-only). The SKILL.md recommends installing @membranehq/cli via npm (-g or npx usage). This is a standard public-registry approach (moderate risk because it alters the user's environment), not a download from an untrusted host. Users should verify the npm package and be comfortable installing global npm packages.
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to ask users for API keys. Authentication is performed via Membrane's login flow (browser-based or headless code flow). This is proportionate, though it means credentials are managed server-side by Membrane, which the user must trust.
Persistence & Privilege
The skill does not request always: true and makes no persistent system-wide changes itself (it only instructs the user to install a CLI). Autonomous invocation is allowed by default, which is normal; there are no requests to modify other skills or system configs.
Assessment
This skill appears coherent and uses the Membrane CLI as intended for a RoboMQ integration. Before installing, verify the @membranehq/cli npm package (publisher, npm page, and repository), confirm you trust Membrane to handle your RoboMQ credentials and proxy API traffic, and be aware that npm -g will add a global binary on your system. If you need to avoid routing data through a third party, consider using RoboMQ's APIs directly (which would require different credentials and commands).

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

latestvk978f0m65gy22gmt78dtgrpse184866r

License

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

Comments