cube-semantic-layer

Guide Cube semantic layer development with model discovery and API validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/floe-runtime --skill cube-semantic-layer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cube-semantic-layer
Source: https://github.com/Obsidian-Owl/floe-runtime/tree/main/.claude/skills/cube-skill
Command: npx skills add https://github.com/Obsidian-Owl/floe-runtime --skill cube-semantic-layer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides research guidance for building a Cube semantic layer, covering how to discover models, validate Cube capabilities, and align with REST/GraphQL/SQL APIs and dbt integration.

Core Features & Use Cases

  • Research Cube version and capabilities
  • Discover existing Cube models and dbt integrations
  • Validate implementations against Cube docs
  • Verify integration with consumption applications

Quick Start

Run Cube availability checks: cube --version and a local API readiness check, then begin a mapping of existing Cube models to consumption endpoints.

Frequently Asked Questions about cube-semantic-layer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a semantic layer with Cube and dbt?▼

A semantic layer with Cube organizes metrics and dimensions from dbt models into a centralized API. Start by verifying your Cube version and dbt integration, then discover existing models and map them to REST or GraphQL consumption endpoints for downstream applications.

Can I validate my Cube implementation against REST and GraphQL APIs?▼

Yes. This Skill guides validation of Cube implementations by checking version capabilities, verifying API pattern alignment with REST and GraphQL specs, and confirming integration with consumption applications through runtime environment checks.

What's the best way to discover and map existing Cube models?▼

Run Cube availability checks and local API readiness verification, then systematically map discovered models to their corresponding consumption endpoints. This ensures your semantic layer properly exposes metrics and dimensions to all dependent applications.

How do I integrate Cube with my dbt workflow?▼

Verify dbt integration validation within Cube, discover existing dbt models, and propagate governance metadata across the semantic layer. This aligns your transformation logic with Cube's metrics layer and ensures consistent data governance.

Does Cube work with both REST and GraphQL APIs?▼

Yes. Cube supports multiple consumption APIs—REST, GraphQL, and SQL. This Skill validates API pattern alignment for each type and helps you choose the right endpoint for your consumption applications and use cases.

What should I verify before deploying a Cube semantic layer?▼

Before deployment, validate Cube version capabilities, confirm dbt integration, verify API endpoint patterns, test psycopg2 connections and MEASURE() syntax correctness, and ensure governance metadata propagates through the entire layer.