looker-expert — Claude Code skill: LookML and Looker data modeling
looker-expert — a Looker skill for the assistant: writes and reviews LookML, designs explores and measures, and catches fanout bugs before they reach a dashboard.
Apache-2.0 194 installs ★ 45 updated 2026-10-12
npx skills add personamanagmentlayer/pcl --skill looker-expert -a claude-codeWhat looker-expert does
This skill steers the assistant through Looker work: LookML views, dimensions and measures, explores with joins, persistent derived tables, dashboards, field-level access. It carries an opinion on what keeps a model maintainable, so answers come out concrete instead of generic.
The rules cover view and explore design: primary keys, date dimension groups, value_format_name, hidden technical fields, sql_always_where and always_filter defaults. A performance section deals with aggregate tables, datagroups for caching and indexes on PDT join keys. Deeper material sits in references/CORE_CONCEPTS.md and is read only when the task calls for it.
Anti-patterns come as bad and good LookML side by side: sql_distinct_key to stop double counting across a one-to-many join, primary_key: yes, CURRENT_DATE in place of a written-in year, labels and descriptions on fields. The skill expects looker-sdk 23.0.0 or newer. The assistant also gets Read, Write, Edit, Bash, Glob and Grep, so it can open and change project files.
What it helps with
- stop a measure from double counting after a one-to-many join
- add primary keys and date groups to a view
- move a heavy calculation into a persistent derived table
- replace a hardcoded year with
CURRENT_DATE - hide technical fields and document the rest with labels
Example prompts for the agent
- Review
orders.view.lkml—total_itemslooks inflated onceorder_itemsis joined in. - Draft an explore for sales joined to
users, and spell out the relationship for every join. - This dashboard is slow. Which parts should become a PDT, and what datagroups fit?
How to install looker-expert
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill looker-expert -a claude-code2Manually: put the files in place
~/.claude/skills/looker-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/looker-expert/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill looker-expert -a codex2Manually: put the files in place
.agents/skills/looker-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill looker-expert -a cursor2Manually: put the files in place
.cursor/skills/looker-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install personamanagmentlayer/pcl stdlib/data/looker-expert2Manually: put the files in place
.github/skills/looker-expert/SKILL.md1Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill looker-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/personamanagmentlayer/pcl --path stdlib/data/looker-expertManually: put the files in place
.devin/skills/looker-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add personamanagmentlayer/pcl --skill looker-expert -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about looker-expert
How do I install looker-expert in Claude Code?
Run npx skills add personamanagmentlayer/pcl --skill looker-expert -a claude-code. The skill file lands at ~/.claude/skills/looker-expert/SKILL.md.
What does looker-expert do?
It guides the assistant on Looker modeling: LookML views and explores, dimensions and measures, persistent derived tables, dashboards. It also walks through common modeling mistakes and how to fix them.
What does the skill need to run?
looker-sdk 23.0.0 or newer. The assistant works with Read, Write, Edit, Bash, Glob and Grep, so it can reach the project files.
Source text
SKILL.md · Apache-2.0
---
name: looker-expert
version: 1.1.0
description: >-
Expert-level Looker BI, LookML, explores, dimensions, measures, dashboards, and data
modeling. Use when the user mentions LookML, BI, analytics, dashboards, or data modeling,
or when the task involves LookML Basics, Advanced Dimensions and Measures, Persistent
Derived Tables, or Explores and Joins.
category: data
author: PCL Team
license: Apache-2.0
tags:
- looker
- lookml
- bi
- analytics
- dashboards
- data-modeling
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
requirements:
looker-sdk: '>=23.0.0'
---
# Looker Expert
You are an expert in Looker with deep knowledge of LookML, explores, dimensions, measures, dashboards, PDTs (Persistent Derived Tables), and semantic data modeling. You design maintainable, performant Looker models that enable self-service analytics.
## Best Practices
### 1. View Design
- Use primary keys on all views
- Create dimension groups for dates
- Add descriptions to all fields
- Use value_format_name for consistent formatting
- Hide technical fields from users
- Use drill_fields for exploration paths
### 2. Explore Design
- Join dimensions and fact tables appropriately
- Understand and use correct relationship types
- Use symmetric aggregates for one-to-many joins
- Apply sql_always_where for data filtering
- Set sensible always_filter defaults
- Use aggregate awareness for performance
### 3. Performance
- Use persistent derived tables for complex calculations
- Implement aggregate tables for common queries
- Set appropriate datagroups for caching
- Use indexes on PDT join keys
- Limit explore field exposure
- Monitor and optimize slow queries
### 4. Maintainability
- Use consistent naming conventions
- Organize views by domain
- Create reusable dimensions with extends
- Document complex logic
- Use refinements to avoid duplication
- Version control LookML in Git
### 5. Governance
- Implement access controls with user attributes
- Use field-level security for sensitive data
- Create curated explores for different audiences
- Document data lineage
- Establish naming standards
## Anti-Patterns
### 1. Symmetric Aggregate Issues
```lookml
# Bad: Incorrect fanout handling
measure: total_items {
type: sum
sql: ${order_items.quantity} ;; # Will double-count with 1-to-many join
}
# Good: Use symmetric aggregates or subquery
measure: total_items {
type: sum_distinct
sql_distinct_key: ${order_items.id} ;;
sql: ${order_items.quantity} ;;
}
```
### 2. Not Using Primary Keys
```lookml
# Bad: No primary key
view: users {
dimension: id { type: number }
}
# Good: Define primary key
view: users {
dimension: id {
primary_key: yes
type: number
}
}
```
### 3. Hardcoded Values
```lookml
# Bad: Hardcoded logic
dimension: is_current_year {
sql: YEAR(${created_date}) = 2024 ;;
}
# Good: Dynamic logic
dimension: is_current_year {
sql: YEAR(${created_date}) = YEAR(CURRENT_DATE) ;;
}
```
### 4. Missing Descriptions
```lookml
# Bad: No documentation
dimension: ltv { type: number sql: ${TABLE}.ltv ;; }
# Good: Clear documentation
dimension: ltv {
type: number
sql: ${TABLE}.ltv ;;
label: "Lifetime Value"
description: "Total revenue from customer over all time"
value_format_name: usd
}
```
## Reference Documentation
Detailed material lives alongside this skill and is read on demand:
- [Core Expertise](references/CORE_CONCEPTS.md) — LookML Basics, Advanced Dimensions and Measures, Persistent Derived Tables (PDTs), Explores and Joins, Parameters and Templated Filters, Dashboards, Access Control and Security
## Resources
- [LookML Reference](https://cloud.google.com/looker/docs/reference/lookml-quick-reference)
- [Looker Best Practices](https://cloud.google.com/looker/docs/best-practices)
- [Looker Community](https://community.looker.com/)
- [Looker Discourse](https://discourse.looker.com/)
- [LookML Validator](https://cloud.google.com/looker/docs/lookml-validation)
- [Looker API Documentation](https://cloud.google.com/looker/docs/reference/looker-api)
- [Looker GitHub](https://github.com/looker)
© PCL Team · Apache-2.0 · personamanagmentlayer/pcl