Qualys
v1.0.2Qualys integration. Manage data, records, and automate workflows. Use when the user wants to interact with Qualys data.
⭐ 0· 106·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
Name/description state a Qualys integration and the SKILL.md exclusively instructs use of the Membrane CLI and Membrane-managed Qualys connectors — the requested capabilities match the stated purpose.
Instruction Scope
Runtime instructions stay within scope: they tell the agent/operator to install the Membrane CLI, authenticate, create or locate a Qualys connection, list/run actions, or proxy requests to Qualys via Membrane. There are no instructions to read unrelated system files, request unrelated credentials, or exfiltrate data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no automatic installer), but it directs the user to install @membranehq/cli from npm (global npm install or npx). Installing an npm CLI is a reasonable approach for this integration, but it carries the usual trust considerations for third-party packages (verify publisher, check package integrity and version).
Credentials
The skill declares no required environment variables or local config paths. The documentation explicitly delegates auth to Membrane and advises not to request API keys from users, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request permanent (always:true) presence, does not modify other skills or system settings, and only describes CLI-driven interactions. Autonomous invocation defaults are unchanged but are not combined with other red flags.
Assessment
This skill appears coherent: it delegates Qualys access to the Membrane service and instructs use of the @membranehq/cli. Before installing or using it, verify you trust the Membrane provider and the npm package (@membranehq/cli) — check the publisher, GitHub repo, and recent release history. Be aware that using Membrane means you are granting it an authenticated connection to your Qualys tenant: prefer creating least-privilege connections/accounts for automation rather than using an admin account. If you have policies about installing global npm packages, consider using npx or a controlled environment (container or VM) to run the CLI. If you need higher assurance, ask the skill author for a rationale for any scopes/permissions the connection requests and confirm Membrane's data handling/privacy practices.Like a lobster shell, security has layers — review code before you run it.
latestvk975r2hr2539n71epfv0f97vh9843azw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.