| name | looker-studio-bigquery |
| description | Route BigQuery-backed Looker Studio work into one stakeholder-reporting packet: dashboard-spec, slow-dashboard triage, refresh-shape choice, audience split, or exec-handoff. Use when the user needs KPI boards, PM/ops reviews, marketing / GTM reporting, product funnel summaries, or game/live-ops telemetry dashboards on top of curated BigQuery data. Route KPI explanation to `data-analysis`, repeated anomaly hunting to `pattern-detection`, telemetry/alerting coverage to `monitoring-observability`, and semantic-platform choice to `survey`.
|
| allowed-tools | Read Write Edit Glob Grep |
| compatibility | Best when the workspace can inspect SQL, reporting specs, and repo files tied to dashboard delivery. Assumes BigQuery already exists or can be reasoned about; this is not a full GCP bootstrap skill.
|
| license | MIT |
| metadata | {"tags":"looker-studio, data-studio, bigquery, dashboard, kpi, analytics, reporting, marketing, pm-ops, live-ops, bi-engine","platforms":"Claude, ChatGPT, Gemini, Codex","version":"2.1.0","modernization":"2026-04-15T00:00:00.000Z","structural_hardening":"2026-04-19T00:00:00.000Z"} |
Looker Studio + BigQuery
Use this skill when the real deliverable is one trustworthy stakeholder-reporting packet on top of BigQuery.
looker-studio-bigquery owns the reporting layer for:
- PM / ops KPI review boards
- product funnel, retention, and rollout dashboards already modeled in BigQuery
- marketing / GTM channel and revenue reporting
- game / live-ops / business telemetry review boards
- refresh, cost, audience, and export-handoff decisions for Looker Studio on curated data
Read these support docs first when needed:
When to use this skill
- The user explicitly wants Looker Studio / Data Studio + BigQuery help.
- The data already lives in BigQuery, or the dashboard clearly sits on curated BigQuery tables/views.
- The main job is dashboard structure, refresh/cost shape, audience-specific delivery, or export-ready reporting.
- The request is about KPI boards, PM/ops reviews, marketing/GTM reporting, product summary dashboards, or game/business telemetry dashboards.
- The real risk is dashboard trust, refresh design, or mixed-audience sprawl rather than raw SQL interpretation alone.
When not to use this skill
- The main job is explaining why a KPI moved or what the dataset means → use
data-analysis
- The main job is repeated anomaly hunting or reusable rule scans across metrics/events → use
pattern-detection
- The main job is telemetry reliability, alerting, or instrumentation coverage → use
monitoring-observability
- The main job is choosing a full BI / semantic platform → use
survey
- The main job is broad GCP/bootstrap/deploy work → route to the relevant infrastructure skill first
Instructions
Step 1: Pick one primary packet before talking about charts
Normalize the request into one packet.
looker_studio_bigquery_packet:
