exasol-semantic-analyst

Answers business questions through governed Exasol Semantic Views models using structured compilation and semantic SQL.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Business questions often get answered with hand-written SQL that guesses at joins and metric formulas, producing inconsistent results. This Skill routes analytics through a published Exasol Semantic Views model so metrics, dimensions, and compatibility rules come from the governed semantic layer instead of ad-hoc physical-table SQL. ## Core Features & Use Cases - Semantic Discovery: Query role-scoped SEMANTIC_AGENT views to list models, objects, metrics, dimensions, descriptions, and blocking validation errors before compiling anything. - Structured Compilation: Translate natural language questions into JSON requests compiled via COMPILE_REQUEST_JSON, with pre-checked metric/dimension compatibility and structured error or clarification responses. - MCP and Semantic SQL Paths: Execute governed semantic SQL through the official Exasol MCP Server preprocessor when EXECUTE SCRIPT is unavailable, and explain or record feedback on compiled requests using durable handles. - Use Case: An agent asked for "top 10 regions by revenue last quarter" discovers the sales model, verifies metric/dimension compatibility, compiles a structured request, executes the generated SQL under the caller's privileges, and records user feedback on the answer. ## Quick Start Ask the agent to answer a business question such as "show total revenue by customer region for completed orders" using the published Exasol semantic model.

Frequently Asked Questions about exasol-semantic-analyst

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

FAQPage Schema
How do I answer business questions with an Exasol semantic layer?▼

Discover available models and fields through the SEMANTIC_AGENT views, check metric and dimension compatibility in VALID_COMBINATIONS_FOR_AGENT, then compile a structured JSON request with COMPILE_REQUEST_JSON and execute the returned GENERATED_SQL under the caller's privileges.

How do I run semantic SQL through the Exasol MCP Server?▼

Call list_exasol_preprocessors, set SEMANTIC_ADMIN.SEMANTIC_PREPROCESSOR with set_exasol_preprocessor, verify it is current, then execute semantic SQL with execute_exasol_query. Put LIMIT inside the SQL rather than using the MCP row_limit parameter.

Can I use this with only SELECT access and no EXECUTE SCRIPT?▼

Yes, if the official Exasol MCP Server exposes its preprocessor tools, you can use the governed semantic SQL path. Without it, you are limited to discovery through SEMANTIC_AGENT views and should request a semantic adapter for structured compilation.

What happens when a semantic request fails to compile?▼

The compiler returns STATUS ERROR with a stable ERROR_CODE and message, and may include CLARIFICATION_JSON with structured choices for ambiguous fields. You should report the error or present the choices rather than falling back to physical-table SQL.

How do I check which metrics work with which dimensions?▼

Query SEMANTIC_AGENT.VALID_COMBINATIONS_FOR_AGENT for the target model and object, filtering by the metric names you plan to use. Only include a metric and dimension pair in a request when IS_VALID is TRUE.

How do I record feedback on a semantic query result?▼

Call SEMANTIC_ADMIN.RECORD_AGENT_FEEDBACK with the AGENT_REQUEST handle, the request id, a verdict such as ACCEPTED or NEEDS_CHANGE, a comment, and an optional proposed-change JSON. Positive verdicts are recorded as well as negative ones.