LookML field curation (lookml-field-curation)

Scope and Medallion refinement boundary

Base Bronze views (bronze/:table.view.lkml) are autogenerated 1:1 from database tables by generate-view-from-table with generate_descriptions=True and add_autogenerated_header=True (# AUTOGENERATED). That generation step pulls existing database INFORMATION_SCHEMA column comments directly into bronze/:table.view.lkml. Never hand-edit bronze/:table.view.lkml.

Run lookml-field-curation only on demand when asked to curate, refine, or enrich LookML field descriptions, field visibility (hidden:), or filter autocomplete suggestions (suggestable:) for self-service BI exploration or Conversational Analytics and Gemini in Looker semantic modeling. Do not run this skill automatically as part of agentic-lookml-workflow.

Place single-table field curations (hidden:, suggestable:, description:, primary_key: yes, and single-table calculated dimensions and measures) in bronze/:table.refinement.lkml (or bronze/:schema/:table.refinement.lkml when schema collision routing applies), starting with include: ":table.view.lkml" on line 1 and view: +:table { ... }. Place cross-view calculated dimensions and measures in silver/:view_a_:view_b_fields.view.lkml or Silver and Gold derived views.

Why hidden and suggestable matter

Setting hidden: yes removes a field from the Explore field picker and excludes it from the Explore schema fetched by Conversational Analytics and Gemini in Looker at query time. The field remains available for LookML ${field_name} substitution, sql_on: joins, measure definitions, and derived tables. Hiding surrogate keys, foreign keys, intermediate calculation helpers, raw JSON payloads, and ETL audit columns cuts LLM context noise and stops users or agents from grouping by internal keys. Because hidden: yes only controls presentation and schema context, use required_access_grants when a column requires access control.

By default (suggestable: yes), opening a filter dropdown on a type: string dimension or running Conversational Analytics value sampling triggers an autocomplete query against the warehouse: