qlik-naming-conventions
Field naming with entity-prefix dot notation, table naming, variable naming (v prefix), expression naming, file naming (.qvs, QVD), key field conventions (% prefix, HideSuffix), cross-layer field mapping from source through extract/transform/model to UI, field rename layer using Mapping RENAME, variable-to-field-name alignment, and naming anti-patterns. Load when naming, renaming, prefixing, aliasing, or mapping fields, tables, variables, or expressions in Qlik Sense.
Install
With your agent
Install OMGSkills skill "pupfish-llc/qlik-agents:skills/qlik-naming-conventions" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Pupfish-LLC/qlik-agents /tmp/qlik-agents && ln -s /tmp/qlik-agents/skills/qlik-naming-conventions ~/.claude/skills/qlik-naming-conventionsFrom README
Qlik Sense Naming Conventions Naming in Qlik Sense is not cosmetic. The associative engine links tables through identically-named fields. Every field name is a potential association. An unprefixed Status field in two tables silently links them, producing synthetic keys or incorrect aggregations with no error message. Naming IS data modeling. The single most important rule: prefix every non-key field with its entity name using dot notation (Product.Category, Order.Status). This one convention prevents the majority of accidental associations, makes fields self-documenting in filter panes, and eliminates the need for QUALIFY on pre-prefixed fields. This skill covers field naming, key field naming, table naming, variable naming, expression naming, file naming, and the cross-layer naming strategy that traces a field from source system through every ETL layer to the UI.