What problem does it solve?
Translating LookML definitions into a semantic layer by hand is error-prone: dimension_group timeframes get mistaken for physical columns, derived tables lose their grain, and enforced filters like sql_always_where get dropped. This Skill provides a deterministic mapping from LookML constructs to ktx semantic layer sources with verification steps that prevent hallucinated column names.
Core Features & Use Cases
- LookML-to-ktx mapping table: Maps views to overlays or standalone sources, measures to measures, explore joins to the join graph, and filters to segments, with a LookML-to-ktx type map.
- Three capture shapes with worked examples: Overlay for thin wrappers over manifest tables, standalone from derived_table, and standalone with sql_always_where folded into the sql clause.
- Identifier verification protocol: Requires sl_discover, entity_details, and sql_execution probes before any write, plus sl_validate after every sl_write_source to catch invented columns via warehouse errors.
- Use Case: While ingesting a Looker project, the agent encounters a view with a derived_table computing biomarker deltas; it writes a standalone ktx source with explicit grain and columns, then validates it against the warehouse before continuing.
Quick Start
Load this skill whenever the turn contains .lkml content and ask the agent to map the LookML views and explores into ktx semantic layer sources with provenance tags.