fabriciq-ontology-consumption-cli

What problem does it solve? Agents need to understand what a Microsoft Fabric IQ Ontology (preview) exposes—entity types, keys, relationships, and data bindings—before querying the underlying Lakehouse or Eventhouse data, and doing this manually via raw REST calls is error-prone. ## Core Features & Use Cases - Read-only ontology enumeration: Fetch and decode the ontology item definition via Get Item Definition (LRO), reconstructing entity types, data bindings, relationships, and contextualizations into an agent-ready grounding JSON. - Query routing: Translate ontology property names into physical source columns via propertyBindings and delegate composed KQL, T-SQL, or Spark SQL queries to eventhouse-consumption-cli, sqldw-consumption-cli, or spark-consumption-cli. - Graph walks: Resolve N-hop neighborhoods from an anchor entity by composing linking-table reads and per-entity source queries without custom scripts. - Use Case: Ask "which aircraft does Airline ZA operate and what are their latest altitude readings" and the skill grounds on the ontology, traverses the Lakehouse linking table, then routes a time-filtered KQL query to the Eventhouse. ## Quick Start Ask the agent to explore the ontology in your Fabric workspace and list its entity types, bindings, and relationships before querying any data.