Claude Code for Lightdash: Open Source BI on dbt Models — Claude Skills 360 Blog
Blog / AI / Claude Code for Lightdash: Open Source BI on dbt Models
AI

Claude Code for Lightdash: Open Source BI on dbt Models

Published: August 24, 2027
Read time: 5 min read
By: Claude Skills 360

Lightdash is open-source BI built on top of dbt — metrics live in schema.yml alongside your dbt models. meta: { label: "Orders", joins: ["users"] } in the dbt model’s YAML config. Dimensions: - name: status, meta: { label: "Status", type: string }. Metrics: - name: revenue, meta: { label: "Revenue", type: number, sql: "SUM(${TABLE}.amount_usd)", format: { type: currency } }, - name: order_count, meta: { label: "Orders", type: count }. Custom dimensions: sql: "DATE_TRUNC('week', ${TABLE}.created_at)", type: date. Filters on metrics: meta: { sql: "SUM(CASE WHEN ${TABLE}.status = 'completed' THEN ${TABLE}.amount_usd ELSE 0 END)" }. lightdash validate checks metric definitions against your dbt project. lightdash deploy syncs dbt project to Lightdash Cloud. Lightdash REST API: GET /api/v1/projects/{projectId}/charts lists charts, POST /api/v1/projects/{projectId}/explores/{exploreName}/runQuery runs a query. Chart embedding: GET /api/v1/embed/{embedId}/token returns a short-lived JWT, use as ?token=JWT query param on the embed URL. Self-hosted: docker run -p 8080:8080 --env-file .env lightdash/lightdash. Spaces: organize dashboards and charts into shared or private spaces. Scheduler: built-in Slack/email notifications when dashboard conditions are met. lightdash preview spins up a branch-scoped Lightdash instance for PR previews. Claude Code generates Lightdash metric YAML, REST API clients, embed integrations, and Docker deployment configurations.

CLAUDE.md for Lightdash

## Lightdash Stack
- Metrics defined in dbt schema.yml — meta.label, meta.type, meta.sql for columns
- Deploy: lightdash deploy --project myproject (Cloud) or lightdash preview (PR preview)
- REST API: /api/v1 — GET /projects, POST /explores/{name}/runQuery
- Auth: Bearer {LIGHTDASH_API_KEY} header — generate in Lightdash Settings → API Tokens
- Embed: /api/v1/embed/{embedId}/token → get JWT → iframe URL with ?token=JWT
- Self-hosted: docker compose up — lightdash + postgres + redis services

dbt Schema YAML with Lightdash Metrics

# models/marts/schema.yml — dbt schema with Lightdash metric definitions
version: 2

models:
  - name: orders_daily
    description: "Daily order records with user enrichment"
    meta:
      label: "Orders"
      joins:
        - join: users
          sql_on: "${orders_daily}.user_id = ${users}.id"

    columns:
      - name: order_id
        description: "Unique order identifier"
        meta:
          label: "Order ID"
          type: string
          primary_key: true

      - name: user_id
        description: "FK to users"
        meta:
          label: "User ID"
          type: string
          hidden: true

      - name: amount_usd
        description: "Order amount in USD"
        meta:
          label: "Amount (USD)"
          type: number
          format: { type: currency, currency: USD, round: 2 }
          metrics:
            - name: revenue
              type: sum
              label: "Total Revenue"
              description: "Sum of all order amounts"
              format: { type: currency, currency: USD }

            - name: avg_order_value
              type: average
              label: "Average Order Value"
              format: { type: currency, currency: USD, round: 2 }

            - name: completed_revenue
              type: sum
              label: "Completed Revenue"
              description: "Revenue from completed orders only"
              filters:
                - target: { fieldRef: status }
                  operator: equals
                  values: ["completed"]

      - name: status
        meta:
          label: "Status"
          type: string

      - name: created_at
        meta:
          label: "Order Date"
          type: timestamp

      - name: created_date
        meta:
          label: "Order Date (Day)"
          type: date
          hidden: false

      - name: user_plan
        meta:
          label: "User Plan"
          type: string

      - name: user_country
        meta:
          label: "User Country"
          type: string

    # Custom dimensions not in source data
    meta:
      additional_dimensions:
        - name: order_size_bucket
          label: "Order Size"
          type: string
          sql: >
            CASE
              WHEN ${amount_usd} < 25   THEN 'Small (<$25)'
              WHEN ${amount_usd} < 100  THEN 'Medium ($25-$100)'
              WHEN ${amount_usd} < 500  THEN 'Large ($100-$500)'
              ELSE 'Enterprise (>$500)'
            END

        - name: days_to_first_order
          label: "Days to First Order"
          type: number
          sql: "DATEDIFF('day', ${users.created_at}, ${orders_daily.created_at})"

  - name: users
    meta:
      label: "Users"

    columns:
      - name: id
        meta: { label: "User ID", type: string, primary_key: true }

      - name: email
        meta: { label: "Email", type: string }

      - name: plan
        meta: { label: "Plan", type: string }

      - name: country
        meta: { label: "Country", type: string }

      - name: created_at
        meta:
          label: "Signup Date"
          type: timestamp
          metrics:
            - name: new_users
              type: count_distinct
              label: "New Users"
              description: "Distinct users by signup date"

Lightdash REST API Client

// lib/lightdash/client.ts — Lightdash REST API client
const LIGHTDASH_URL     = process.env.LIGHTDASH_URL ?? "https://app.lightdash.cloud"
const LIGHTDASH_API_KEY = process.env.LIGHTDASH_API_KEY!
const LIGHTDASH_PROJECT = process.env.LIGHTDASH_PROJECT_ID!

async function lightdashFetch<T>(path: string, options: RequestInit = {}): Promise<T> {
  const res = await fetch(`${LIGHTDASH_URL}/api/v1${path}`, {
    ...options,
    headers: {
      "Content-Type":  "application/json",
      "Authorization": `ApiKey ${LIGHTDASH_API_KEY}`,
      ...((options.headers as Record<string, string>) ?? {}),
    },
  })

  const body = await res.json()
  if (!res.ok) throw new Error(`Lightdash API error ${res.status}: ${JSON.stringify(body)}`)
  return body.results as T
}

export type ExploreQuery = {
  exploreName:    string
  dimensions:     string[]   // e.g. ["orders_daily_status", "orders_daily_created_date_day"]
  metrics:        string[]   // e.g. ["orders_daily_revenue", "orders_daily_order_count"]
  filters?:       Record<string, unknown>
  limit?:         number
  sorts?:         Array<{ fieldId: string; descending: boolean }>
}

export async function runExploreQuery(query: ExploreQuery): Promise<{
  rows:    Array<Record<string, { value: { raw: unknown; formatted: string } }>>
  fields:  Record<string, { label: string; type: string }>
}> {
  return lightdashFetch(`/projects/${LIGHTDASH_PROJECT}/explores/${query.exploreName}/runQuery`, {
    method: "POST",
    body:   JSON.stringify({
      dimensions: query.dimensions,
      metrics:    query.metrics,
      filters:    query.filters ?? { dimensions: {}, metrics: {} },
      limit:      query.limit ?? 500,
      sorts:      query.sorts ?? [],
      tableCalculations: [],
    }),
  })
}

export async function listDashboards(): Promise<Array<{
  uuid:        string
  name:        string
  description: string
  updatedAt:   string
}>> {
  return lightdashFetch(`/projects/${LIGHTDASH_PROJECT}/dashboards`)
}

export async function getEmbedToken(embedId: string): Promise<{ token: string; expiresIn: number }> {
  return lightdashFetch(`/embed/${embedId}/token`, { method: "GET" })
}

Embed Integration (Next.js)

// app/api/lightdash-embed/route.ts — SSO embed token for users
import { NextResponse } from "next/server"
import { auth }         from "@/lib/auth"

const LIGHTDASH_URL     = process.env.LIGHTDASH_URL!
const LIGHTDASH_API_KEY = process.env.LIGHTDASH_API_KEY!

export async function GET(req: Request) {
  const session = await auth()
  if (!session) return NextResponse.json({ error: "Unauthorized" }, { status: 401 })

  const url    = new URL(req.url)
  const embedId = url.searchParams.get("embedId")
  if (!embedId) return NextResponse.json({ error: "Missing embedId" }, { status: 400 })

  // Fetch short-lived token from Lightdash
  const tokenRes = await fetch(`${LIGHTDASH_URL}/api/v1/embed/${embedId}/token`, {
    headers: { Authorization: `ApiKey ${LIGHTDASH_API_KEY}` },
  })

  const { results } = await tokenRes.json()
  return NextResponse.json({ token: results.token, expiresIn: results.expiresIn })
}

// components/LightdashEmbed.tsx — iFrame embed component
"use client"
import { useEffect, useState } from "react"

export function LightdashEmbed({
  embedId,
  height = 600,
}: {
  embedId: string
  height?:  number
}) {
  const [embedUrl, setEmbedUrl] = useState<string | null>(null)

  useEffect(() => {
    fetch(`/api/lightdash-embed?embedId=${embedId}`)
      .then((r) => r.json())
      .then(({ token }) => {
        const base = process.env.NEXT_PUBLIC_LIGHTDASH_URL
        setEmbedUrl(`${base}/embed/${embedId}?token=${token}`)
      })
  }, [embedId])

  if (!embedUrl) return <div className="animate-pulse bg-gray-100 rounded-lg" style={{ height }} />

  return (
    <iframe
      src={embedUrl}
      width="100%"
      height={height}
      className="rounded-xl border border-gray-200"
      title="Analytics Dashboard"
    />
  )
}

For the Metabase alternative when needing a BI tool designed for non-technical users who want to build their own charts without writing SQL or YAML — Metabase provides drag-and-drop chart builders and natural language questions while Lightdash is targeted at data teams who already use dbt and want metrics defined as code alongside their dbt models. For the Cube alternative when needing a standalone semantic layer that works without dbt — Cube has its own YAML/JavaScript data model language and can connect to any database without a dbt project while Lightdash is specifically designed to work on top of an existing dbt project and won’t add value without one. The Claude Skills 360 bundle includes Lightdash skill sets covering dbt metric YAML, REST API clients, and embed integrations. Start with the free tier to try open source BI generation.

Keep Reading

AI

Claude Code for email.contentmanager: Python Email Content Accessors

Read and write EmailMessage body content with Python's email.contentmanager module and Claude Code — email contentmanager ContentManager for the class that maps content types to get and set handler functions allowing EmailMessage to support get_content and set_content with type-specific behaviour, email contentmanager raw_data_manager for the ContentManager instance that handles raw bytes and str payloads without any conversion, email contentmanager content_manager for the standard ContentManager instance used by email.policy.default that intelligently handles text plain text html multipart and binary content types, email contentmanager get_content_text for the handler that returns the decoded text payload of a text-star message part as a str, email contentmanager get_content_binary for the handler that returns the raw decoded bytes payload of a non-text message part, email contentmanager get_data_manager for the get-handler lookup used by EmailMessage get_content to find the right reader function for the content type, email contentmanager set_content text for the handler that creates and sets a text part correctly choosing charset and transfer encoding, email contentmanager set_content bytes for the handler that creates and sets a binary part with base64 encoding and optional filename Content-Disposition, email contentmanager EmailMessage get_content for the method that reads the message body using the registered content manager handlers, email contentmanager EmailMessage set_content for the method that sets the message body and MIME headers in one call, email contentmanager EmailMessage make_alternative make_mixed make_related for the methods that convert a simple message into a multipart container, email contentmanager EmailMessage add_attachment for the method that attaches a file or bytes to a multipart message, and email contentmanager integration with email.message and email.policy and email.mime and io for building high-level email readers attachment extractors text body accessors HTML readers and policy-aware MIME construction pipelines.

5 min read Feb 12, 2029
AI

Claude Code for email.charset: Python Email Charset Encoding

Control header and body encoding for international email with Python's email.charset module and Claude Code — email charset Charset for the class that wraps a character set name with the encoding rules for header encoding and body encoding describing how to encode text for that charset in email messages, email charset Charset header_encoding for the attribute specifying whether headers using this charset should use QP quoted-printable encoding BASE64 encoding or no encoding, email charset Charset body_encoding for the attribute specifying the Content-Transfer-Encoding to use for message bodies in this charset such as QP or BASE64, email charset Charset output_codec for the attribute giving the Python codec name used to encode the string to bytes for the wire format, email charset Charset input_codec for the attribute giving the Python codec name used to decode incoming bytes to str, email charset Charset get_output_charset for returning the output charset name, email charset Charset header_encode for encoding a header string using the charset's header_encoding method, email charset Charset body_encode for encoding body content using the charset's body_encoding, email charset Charset convert for converting a string from the input_codec to the output_codec, email charset add_charset for registering a new charset with custom encoding rules in the global charset registry, email charset add_alias for adding an alias name that maps to an existing registered charset, email charset add_codec for registering a codec name mapping for use by the charset machinery, and email charset integration with email.message and email.mime and email.policy and email.encoders for building international email senders non-ASCII header encoders Content-Transfer-Encoding selectors charset-aware message constructors and MIME encoding pipelines.

5 min read Feb 11, 2029
AI

Claude Code for email.utils: Python Email Address and Header Utilities

Parse and format RFC 2822 email addresses and dates with Python's email.utils module and Claude Code — email utils parseaddr for splitting a display-name plus angle-bracket address string into a realname and email address tuple, email utils formataddr for combining a realname and address string into a properly quoted RFC 2822 address with angle brackets, email utils getaddresses for parsing a list of raw address header strings each potentially containing multiple comma-separated addresses into a list of realname address tuples, email utils parsedate for parsing an RFC 2822 date string into a nine-tuple compatible with time.mktime, email utils parsedate_tz for parsing an RFC 2822 date string into a ten-tuple that includes the UTC offset timezone in seconds, email utils parsedate_to_datetime for parsing an RFC 2822 date string into an aware datetime object with timezone, email utils formatdate for formatting a POSIX timestamp or the current time as an RFC 2822 date string with optional usegmt and localtime flags, email utils format_datetime for formatting a datetime object as an RFC 2822 date string, email utils make_msgid for generating a globally unique Message-ID string with optional idstring and domain components, email utils decode_rfc2231 for decoding an RFC 2231 encoded parameter value into a tuple of charset language and value, email utils encode_rfc2231 for encoding a string as an RFC 2231 encoded parameter value, email utils collapse_rfc2231_value for collapsing a decoded RFC 2231 tuple to a Unicode string, and email utils integration with email.message and email.headerregistry and datetime and time for building address parsers date formatters message-id generators header extractors and RFC-compliant email construction utilities.

5 min read Feb 10, 2029

Put these ideas into practice

Claude Skills 360 gives you production-ready skills for everything in this article — and 2,350+ more. Start free or go all-in.

Back to Blog

Get 360 skills free