skills.rest
paulasilvatech
paulasilvatechOFFICIAL
Explore all skills by this author →
GitHub

fabriciq-ontology-cli

Author and explore Microsoft Fabric IQ Ontology items via the Fabric control-plane REST API.

Updated Aug 19, 2026
Search Tags:#ontology#fabric#az rest#entity types#data bindings#graph walk#microsoft fabric iq
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill fabriciq-ontology-cli-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fabriciq-ontology-cli
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/fabriciq-ontology-cli
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill fabriciq-ontology-cli-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating and exploring Fabric IQ Ontology items requires composing complex base64-encoded definition envelopes, managing long-running operations, and correctly mapping entity types, data bindings, and relationship types against lakehouse and eventhouse sources, which is error-prone when done by hand. ## Core Features & Use Cases - Ontology Authoring: Create Ontology items, add entity and relationship types, and bind them to lakehouse or eventhouse tables through a preview-and-confirm flow before any write is persisted. - Ontology Consumption: Enumerate entity types, bindings, lineage, and relationships, extract grounding context JSON, and perform graph walks over an existing ontology in read-only mode. - Query Routing: Translate ontology property names into physical source columns and delegate data queries to the matching per-datasource skill (SQL endpoint, Spark, or Eventhouse KQL). - Use Case: A data engineer asks to create an ontology with Customer and Order entity types bound to a lakehouse; the skill resolves workspace and item IDs, composes the definition parts, previews the change set, and persists it via updateDefinition after confirmation. ## Quick Start Ask the assistant to list the entity types and their data bindings in a named Fabric ontology, or to create a new ontology item with specified entity types bound to a lakehouse table.

Frequently Asked Questions about fabriciq-ontology-cli

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

FAQPage Schema
How do I create a Fabric IQ Ontology item with the CLI?▼

Create the item with POST /v1/workspaces/{ws}/items using type Ontology and a definition envelope containing .platform and an empty definition.json, then poll the x-ms-operation-id operation until it succeeds. Entity types and bindings are added afterward via updateDefinition.

How do I bind an entity type to a lakehouse or eventhouse table?▼

Add a DataBindings part under the entity type with dataBindingType NonTimeSeries for a lakehouse static binding or TimeSeries for lakehouse or eventhouse sources. Eventhouse KustoTable bindings are TimeSeries-only and require the Eventhouse item ID, clusterUri, and databaseName.

Can I query ontology data directly with this skill?▼

No, the consumption mode is read-only over the ontology definition and delegates actual data reads to per-datasource skills such as sqldw-cli, spark-cli, or eventhouse-cli. It composes the query using the binding's propertyBindings column mappings before handing off.

Why does polling the Location header fail after createItem or updateDefinition?▼

In the Ontology preview the Location header redirects to an analysis.windows.net host, which fails authentication with a Fabric-audience token. Capture the x-ms-operation-id header and poll https://api.fabric.microsoft.com/v1/operations/{operationId} instead.

What are the limitations of Fabric Ontology data bindings?▼

Each entity type supports at most one NonTimeSeries binding, which must exist before any TimeSeries binding. Sources must be managed lakehouse tables; external tables, OneLake security, and delta column mapping are not supported, and Eventhouse sources are TimeSeries-only.

When should I use fabriciq-ontology-cli versus the fabriciq skill?▼

Use fabriciq-ontology-cli for work on the Ontology item itself, including entity types, bindings, definitions, lineage, and graph walks. Natural-language questions over Power BI reports and dashboards belong to the fabriciq skill, and DAX queries go to semantic-model-cli.

Related Skills

Explore More Data & Analytics Skills→
9vantage9vantage

fabriciq-ontology-consumption-cli

Explore Fabric IQ Ontology definitions and route entity queries to per-datasource consumption skills.

Community
Advanced
zenbuappszenbuapps

ant-design-pro-v2

Provide API references for Ant Design Pro Components with prop tables and valueType mappings.

Official
Advanced
rritecrritec
3

fabriciq

Answer natural-language questions about Power BI report data by querying semantic models.

Community
Advanced
datheredathere
3.7k

csv-query

Query CSV, TSV, and Excel files with SQL via the Polars-powered sqlp command.

Official
Intermediate