lookml-explore
Instructions
1. Core Standards
- Naming Convention:
snake_casefor the Explore name. - Required Parameters:
description: 100% Coverage. Every Explore MUST have a description.label: A user-friendly name for the Explore in the UI.view_name: Defaults to explore name, but explicit definition is safer.
- Joins:
relationship: Required (one_to_one, many_to_one).sql_on: Required. Use${left.id} = ${right.id}syntax.type: defaults toleft_outer. Useinnerorfull_outerexplicitly if needed.
- Formatting:
- Do NOT use
fromto rename views just for aesthetics. Useview_labelinstead. - Exception: Polymorphic joins, Self-joins, Rescoping extensions.
- Do NOT use
2. Advanced Configuration
More from lkrdev/lookml_skills
lookml-view
Use this skill to create or modify LookML Views. Covers basic view definitions, sql_table_name, file organization, and patterns.
25lookml-model
Use this skill when you need to create or modify a LookML Model file (.model.lkml). This includes defining connections, includes, and configuring model-level settings.
24lookml-refinements
Deep dive into LookML includes, refinements (layering), and project structure best practices. Essential for mastering Looker's object-oriented capabilities.
23lookml-fields
Overview of LookML field types (Dimension, Measure, Filter, Parameter) and the role of the `sql` parameter in each. Use this skill to choose the right field type for your data modeling needs.
22lookml-sets
Guide to using LookML sets for grouping fields, controlling visibility, and managing drill paths.
21lookml-liquid
Use this skill to use Liquid variables in LookML for dynamic SQL, HTML, and Links, including advanced patterns for query optimization.
21