exasol-semantic-reviewer

Review Exasol semantic models and produce approval-ready handoff bundles for engineers and domain owners.

3|Updated May 14, 2026
One-click install
npx skills add https://github.com/exasol-labs/exasol-semantic-views --skill exasol-semantic-reviewer-exasol-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exasol-semantic-reviewer
Source: https://github.com/exasol-labs/exasol-semantic-views/tree/main/skills/exasol-semantic-reviewer
Command: npx skills add https://github.com/exasol-labs/exasol-semantic-views --skill exasol-semantic-reviewer-exasol-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Semantic models often reach production without structured review of grain, relationships, metrics, and business meaning, leading to broken dashboards and mistrusted metrics. This Skill enforces a human-approved release process for Exasol Semantic Views models, turning ad-hoc review into an auditable, gate-driven workflow. ## Core Features & Use Cases - Phased Review Workflow: Classifies each review as DISCOVERY, TECHNICAL_REVIEW, SEMANTIC_REVIEW, RELEASE_REVIEW, or POST_RELEASE_REVIEW, with explicit decision owners and blocked questions. - Evidence and Validation: Builds an evidence map from source comments, constraints, profiles, and samples; queries CURRENT_VALIDATION_ISSUES and requires a clean VALIDATE_MODEL result. - Approval Gates and Handoff Bundle: Enforces SCOPE, TECHNICAL, SEMANTIC, and RELEASE approvals, then produces a complete review bundle with metric cards, semantic diff, acceptance tests, and feedback backlog. - Use Case: Before publishing a new revenue metrics model, run this Skill to verify grain and join correctness, reconcile metrics against trusted SQL, collect domain-owner sign-off, and deliver a READY or NOT_READY decision package to the data engineer. ## Quick Start Use $exasol-semantic-reviewer to review the candidate semantic model 'sales_analytics', identify unresolved technical and semantic risks, and produce an approval-ready handoff for the data engineer.

Frequently Asked Questions about exasol-semantic-reviewer

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

FAQPage Schema
How do I review an Exasol semantic model before publication?▼

Run a phased review: confirm scope and owners, build an evidence map from source metadata, verify grain and relationships, review metric definitions, test business behavior, and produce a semantic diff. Finish with explicit approval gates and a review bundle before publication.

What approval gates are required for semantic model release?▼

Four explicit gates are required: SCOPE_APPROVED and TECHNICALLY_APPROVED by the data engineer, SEMANTICALLY_APPROVED by the domain owner, and RELEASE_APPROVED by the release owner. Missing approvals result in a NOT_READY decision.

How do I check validation issues in an Exasol semantic model?▼

Query SEMANTIC_CATALOG.CURRENT_VALIDATION_ISSUES filtered by model name to list severity, object, rule code, and message. A clean VALIDATE_MODEL result is required, though it proves structural consistency rather than business correctness.

Can the reviewer approve or publish a semantic model automatically?▼

No. The Skill never publishes, certifies, or marks approvals on behalf of humans, and never converts feedback into catalog mutations. It only inspects, tests, recommends, and assembles evidence for human decision-makers.

What is a semantic diff and when is it needed?▼

A semantic diff compares a candidate model against the currently approved version, highlighting additions, removals, formula, grain, relationship, and visibility changes. Each change is classified as BREAKING, BEHAVIORAL, METADATA, or NONE to guide impact review.