By Pupfish-LLC
A multi-agent development pipeline for Qlik Sense. 9-phase workflow from requirements through documentation. You provide source materials and requirements; the pipeline produces production-grade load scripts, expressions, visualization specs, QA reports, and documentation. Most Qlik developers will prefer qlik-toolkit for ad-hoc work.
Designs complete data architecture including app architecture strategy, star schema, ETL pipeline with layer boundaries, QVD layer strategy, cross-layer field mapping, and source architecture consumption patterns. Invoke when the project specification is approved and source profiling is complete. Use after Phase 1 gate passes and Phase 2 source profiling is available.
Generates complete project documentation from all pipeline artifacts. Produces nine documents (README, data dictionary, technical specification, expression catalog, visualization guide, deployment runbook, user guide, change log, dependency tracker). Invoke after all Critical QA findings are resolved (Phase 7 gate passed). Ensures technical accuracy, audience calibration, and cross-document consistency.
Authors all Qlik Sense expressions including master measures, master dimensions, calculated dimensions, set analysis expressions, variable expressions, and complex aggregations. Produces expression catalog reference and runnable expression-variables.qvs file. Invoke after Phase 4 scripts complete. Resume when viz-architect reports expression gaps or execution validation reveals expression issues.
Project manager for the Qlik development pipeline. Coordinates seven specialized subagents across nine phases (platform context, requirements, source profiling, data architecture, script development, expressions, visualization, QA, documentation). Manages quality gates, execution validation, rework loops, and dependency tracking. Use this agent to run a complete Qlik Sense development project or resume an in-progress pipeline.
Reviews all Qlik development artifacts against best practices, naming conventions, script quality, expression correctness, security, and cross-artifact consistency. Performs data quality validation when available. Invoked multiple times during pipeline for lightweight (Phase 3), script (Phase 4), expression (Phase 5), and comprehensive (Phase 7) reviews. Resume to verify fixes.
Post-load data quality validation patterns for Qlik development. Provides query templates for null rate analysis, referential integrity checks, value distribution analysis, row count validation, orphaned record detection, sparse field identification, and duplicate detection. Usable by the qa-reviewer when MCP or post-load data access is available. Also provides patterns for embedding validation checks directly into load scripts. Load when performing data quality validation or writing diagnostic scripts.
Captures existing platform patterns for brownfield Qlik projects. Provides structured templates for documenting existing app inventory, shared subroutine catalogs, naming convention maps, data connection standards, QVD storage conventions, and organizational coding standards. Used by requirements-analyst during Phase 0 context ingestion and by script-developer during Phase 4 for platform compatibility. Load when ingesting platform context or writing scripts that must integrate with existing platform conventions.
Capability registry for the Qlik Cloud MCP server. Maps MCP tools to pipeline phases, provides MCP detection patterns, documents behavioral gotchas not covered by tool definitions, and defines multi-step workflows for expression validation, reference app analysis, visualization scaffolding, and data quality checks. Load whenever an agent needs to interact with a live Qlik Cloud tenant. The tool definitions themselves document parameters, response structures, and basic usage -- this skill covers framework integration, sequencing, and pitfalls discovered through live testing.
Star schema patterns, key resolution strategies, synthetic key prevention, QVD layer design, multi-app architecture patterns, source architecture consumption strategies, and associative engine behavior for Qlik Sense data modeling. Load when designing or reviewing data models.
Deployment procedures for Qlik Sense Cloud and client-managed environments. Covers app import, data connection setup, task scheduling, security configuration, environment promotion (dev/test/prod), QVD storage setup, and post-deployment validation. Invoke manually with /qlik-deploy when preparing deployment artifacts or writing operational runbooks.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
[!NOTE] For a less regimented Qlik development workflow, see qlik-toolkit. Install it to make Claude Code fluent in Qlik Sense for ad-hoc help and single-task delegation. No fixed pipeline, no approval gates, no commitment to a structured artifact set. Reach for
qlik-agents(this plugin) when you specifically want the 9-phase pipeline from requirements through documentation.
A Claude Code plugin that runs a multi-agent development pipeline for Qlik Sense. You provide source materials and requirements. The pipeline produces production-grade load scripts, expressions, visualization specifications, QA reports, and documentation through a structured 9-phase workflow.
The pipeline produces artifacts organized by phase, written to an artifacts/ directory in your project:
Pupfish-LLC/claude-plugins, then click Sync./plugin marketplace add Pupfish-LLC/claude-plugins
/plugin install qlik-agents@pupfish
Create a project directory and open it in Claude Code.
Run the scaffold command to set up the directory structure:
/qlik-agents:qlik-project-scaffold
This creates inputs/ subdirectories for your source materials and artifacts/ directories where the pipeline writes its output.
Place your source materials in the appropriate inputs/ subdirectories:
inputs/source-documentation/: connection specs, data dictionaries, platform docsinputs/existing-apps/: QVF exports, load scripts from brownfield appsinputs/platform-libraries/: shared includes, naming conventions, reference implementationsinputs/upstream-architecture/: ER diagrams, data lineage, ETL architectureStart the pipeline. The orchestrator picks up from wherever you left off, or begins at Phase 0 for new projects.
The pipeline runs nine phases sequentially. You don't need to manage agents or phases manually. The orchestrator handles routing, context passing, and handoffs. Your role is to provide input, approve key decisions, and run execution validation when prompted.
| Phase | What Happens |
|---|---|
| 0 | Captures your existing platform conventions, naming patterns, and reusable components |
| 1 | Builds a project specification through conversation with you |
| 2 | Profiles source system schemas, data types, and volumes |
| 3 | Designs the star schema data model, QVD layers, and field mappings |
| 4 | Generates production load scripts with incremental logic and diagnostics |
| 5 | Authors set analysis expressions, aggregations, and variable definitions |
| 6 | Designs sheet layouts, chart specifications, and master item definitions |
| 7 | Runs comprehensive QA across all artifacts |
| 8 | Produces documentation (data dictionary, tech spec, user guide, runbook) |
The pipeline pauses at specific points and asks for your input. This is by design.
Approval gates require your sign-off before the pipeline advances:
npx claudepluginhub pupfish-llc/claude-plugins --plugin qlik-agentsMake Claude Code fluent in Qlik Sense. 12 skills across the Qlik development lifecycle: data modeling, load scripts, expressions, performance, visualization, naming, QA, platform discovery, source profiling, and Cloud MCP integration. 7 specialist agents (data architect, script developer, expression developer, viz architect, requirements analyst, QA reviewer, doc writer) for ad-hoc invocation. No rigid workflow. Invoke skills and agents as needed.
Spec-Driven Development framework for Data Engineering — 58 agents, 24 KB domains, 5-phase SDD workflow, 31 commands
Connect to Looker and interact with your data using LookML.
The most comprehensive SAP Datasphere plugin for Claude. 18 specialized skills covering exploration, data modeling, integration, BW Bridge migration, security architecture, CLI automation, business content activation, catalog governance, performance optimization, and troubleshooting — all through natural language. Powered by 45 MCP tools with enterprise-grade security.
Quick insights from dlt pipeline data. Connect to a pipeline, profile tables, plan charts, and assemble marimo dashboards.
Write SQL, explore datasets, and generate insights faster. Build visualizations and dashboards, and turn raw data into clear stories for stakeholders.
Skills and tools powered by the Honeydew MCP that help coding agents query data and build semantic models