qlik-platform-discovery

Name: qlik-platform-discovery
Availability: InStock
Author: Pupfish

Automate brownfield Qlik platform discovery from existing .qvs scripts.

Updated May 18, 2026

Search Tags:#naming conventions #brownfield #qlik #platform discovery #qvs script analysis

Ready to run

npx skills add https://github.com/Pupfish-LLC/qlik-toolkit --skill qlik-platform-discovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qlik-platform-discovery
Source: https://github.com/Pupfish-LLC/qlik-toolkit/tree/main/skills/qlik-platform-discovery
Command: npx skills add https://github.com/Pupfish-LLC/qlik-toolkit --skill qlik-platform-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the discovery of brownfield Qlik platforms, identifying naming conventions, connection patterns, QVD storage, architecture, and incremental load patterns from existing .qvs scripts.

Core Features & Use Cases

Brownfield Discovery: Identify naming conventions, connection patterns, QVD storage, and architecture from .qvs scripts.
Incremental Load Detection: Detect incremental load patterns in existing scripts.
Convention Conflicts: Surface naming and storage convention conflicts with framework defaults.
Use Case: For a Qlik environment with legacy applications, this Skill can be used to analyze existing scripts and documentation to understand the platform's conventions and patterns.

Quick Start

Run the qlik-platform-discovery skill in your Qlik environment to identify and analyze the platform's brownfield configurations.

Frequently Asked Questions about qlik-platform-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I discover naming conventions in a brownfield Qlik environment?▼

To discover naming conventions in a brownfield Qlik environment, analyze existing .qvs scripts to identify established patterns and surface conflicts with framework defaults.

Can I detect incremental load patterns from existing Qlik scripts?▼

Yes, you can detect incremental load patterns by analyzing existing .qvs scripts to identify how incremental data loading is implemented and configured in legacy applications.

How do I identify QVD storage and connection patterns in legacy Qlik apps?▼

Identify QVD storage and connection patterns by parsing existing .qvs scripts to extract architecture details and data connection configurations from the legacy applications.

Does Qlik platform discovery work for environments without documentation?▼

Yes, Qlik platform discovery works for environments without documentation by directly analyzing existing .qvs scripts to reverse-engineer architecture and platform conventions.

What is the best way to analyze a legacy Qlik platform's architecture?▼

The best way to analyze a legacy Qlik platform's architecture is automating .qvs script analysis to extract QVD storage, connections, and incremental load patterns.

When should I not use automated QVS script analysis for platform discovery?▼

Avoid automated QVS script analysis when your environment lacks legacy .qvs scripts or when applications use newer Qlik development methods that do not rely on script-based loading.