Build a governed semantic/metrics layer: define each metric once as metrics-as-code (dbt Semantic Layer/MetricFlow) with explicit grain and filters, model entities/dimensions to prevent fan-out, and expose one contract every BI tool consumes — ending metric drift.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill semantic-metrics-layer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Semantic Metrics Layer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-semantic-metrics-layer)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: semantic-metrics-layer
description: "Build a governed semantic/metrics layer: define each metric once as metrics-as-code (dbt Semantic Layer/MetricFlow) with explicit grain and filters, model entities/dimensions to prevent fan-out, and expose one contract every BI tool consumes — ending metric drift."
---
# Semantic / Metrics Layer
## One definition per metric
Revenue, active user, churn, MRR — defined **once** as metrics-as-code, versioned, PR-reviewed. Two dashboards with two 'revenue's = trust gone.
## Explicit grain + filters
A metric needs its **grain** (per what?) and **filters** (which segment?) stated. Otherwise it's uninterpretable.
## Entities & dimensions
Model joins/grains in the layer so consumers can't fan-out or double-count.
## One contract
All BI tools query the same metrics — the semantic layer is the contract, not each tool's hidden calc. Significance -> `applied-statistics`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
