CtrlK
BlogDocsLog inGet started
Tessl Logo

qlik

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/qlik/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete CLI commands and a well-structured connection workflow including feedback loops. Weaknesses are mild over-explanation, an undefined 'Step 2' reference, and the absence of validation guidance before running potentially destructive Qlik actions.

Suggestions

Trim background sentences (e.g. the 'Qlik is a business intelligence...' opener and 'so you can focus on the integration logic') to assume Claude's competence.

Define the referenced 'Step 2' (e.g. add a '### Step 2 — Discover and run actions' heading) or remove the dangling reference.

Add a validation/verification checkpoint before running data-mutating actions (e.g. dry-run or confirm with the user for write/delete operations) to lift workflow clarity above the destructive-operation cap.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes unnecessary explanation such as 'Qlik is a business intelligence and data visualization platform...' and 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.

3 / 5

Actionability

Provides many concrete, copy-paste-ready commands (install, login, connection ensure/get, action list/run, request) plus a full proxy-flag table; minor gaps are the templated CONNECTION_ID/actionId placeholders and reliance on discovery for Qlik-specific actions.

4 / 5

Workflow Clarity

The connection setup has clear state-based checkpoints and a CLIENT_ACTION_REQUIRED feedback loop, but running actions on data has no validation/verification step (destructive/batch cap applies) and 'Step 2' is referenced but never defined.

3 / 5

Progressive Disclosure

No bundle files exist; content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with a useful flags table, though it is a single monolithic file with no external reference split.

4 / 5

Total

14

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a distinct platform and includes an explicit Use-when trigger, satisfying the core what/when requirements. Its weakness is generic, non-Qlik-specific action language and limited trigger-term variety.

Suggestions

Replace generic actions with Qlik-specific capabilities, e.g. 'Create and edit Qlik apps, sheets, and bookmarks; run data loads and automate reload workflows.'

Expand the trigger clause to natural user phrases: 'Use when the user wants to work with Qlik dashboards, sheets, apps, or Qlik Sense data.'

Mention key synonyms/extensions such as 'Qlik Sense' and 'Qlik apps' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Qlik domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not tied to Qlik's actual capabilities like dashboards, sheets, or bookmarks.

3 / 5

Completeness

Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Qlik data' trigger, though the 'what' is generic and the 'when' could name concrete use cases.

4 / 5

Trigger Term Quality

'Qlik' and 'Qlik data' are relevant keywords, but common natural variations users say (dashboards, sheets, Qlik Sense, reports) are missing.

3 / 5

Distinctiveness Conflict Risk

'Qlik' is a specific named platform giving it a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' portion could overlap with other data skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.