Qlik Cloud
WarnAudited by ClawScan on May 10, 2026.
Overview
This Qlik integration is purpose-aligned, but it asks for a Qlik API key and points to missing shell scripts that could change or delete tenant resources, so it needs review before use.
Before installing or using this skill, verify the missing scripts from a trusted source, inspect what they do with the Qlik API key, use a least-privileged key, and require explicit approval for any create, delete, reload, automation, or alert-triggering action.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user or agent could try to run unreviewed or nonexistent local code with Qlik credentials.
The skill instructs running local scripts that receive the Qlik API key, but the supplied manifest says this is an instruction-only skill with no code files, so the referenced scripts cannot be reviewed.
All scripts: `QLIK_TENANT="https://..." QLIK_API_KEY="..." bash scripts/<script>.sh [args]`
Do not run the script commands until the scripts are included in the package, reviewed, and tied to a trusted source/version.
A broad Qlik API key could expose tenant, user, license, app, data-file, automation, and business-data access depending on the account permissions.
The skill requests a persistent Qlik API key even though registry metadata declares no primary credential or environment variables, and it does not specify least-privilege scopes for the key.
Add credentials to TOOLS.md: ... `Tenant URL: https://your-tenant.region.qlikcloud.com` ... `API Key: your-api-key-here`
Use a least-privileged Qlik API key, avoid admin-level tokens unless necessary, and require the skill metadata to declare its credential needs clearly.
Mistaken or overbroad use could delete Qlik apps, trigger business automations, or affect analytics operations.
These are high-impact mutation or operational actions in a third-party analytics tenant, but the provided instructions do not show explicit confirmation, dry-run, scoping, or rollback controls.
`qlik-app-delete.sh` | Delete app; `qlik-reload.sh` | Trigger app reload; `qlik-automation-run.sh` | Run automation; `qlik-alert-trigger.sh` | Trigger alert evaluation
Require explicit user confirmation for destructive or operational commands and document safe scopes, dry-run behavior, and recovery steps.
Sensitive business questions or context may be stored in Qlik assistant threads.
Qlik Answers can create or reuse assistant threads, which may retain user questions or business context in the Qlik service.
`qlik-answers-ask.sh` | Ask assistant a question | `<assistant-id> "question" [thread-id]`; `Ask a question (creates thread automatically)`
Avoid submitting secrets or unnecessary sensitive details, and understand the Qlik tenant's retention and access controls for assistant threads.