ontology-cli

1> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
2> `x-ms-fabric-skill: ontology-cli` (`az rest`: `--headers "x-ms-fabric-skill=ontology-cli"`),
3> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
4 
5> **CRITICAL NOTES**
6> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
7> 2. To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
8> 3. **Skill disambiguation**: use `ontology-cli` for operations on an Ontology item and questions grounded in that Ontology. Natural-language data questions over existing Power BI reports/models are `fabriciq`; report creation, editing, publishing, or rebinding is `powerbi-report-cli`; semantic-model or DAX authoring is `semantic-model-authoring`. Naming an Ontology as a report's data source does not move report authoring into this skill.
9> 4. **Consumption runs through the Ontology Agent MCP server, never around it.** Do not decode an ontology definition to hand-compose KQL / T-SQL / Spark SQL, and do not delegate ontology data questions to `eventhouse-cli` / `sqldw-cli` / `spark-cli`. That path loses the agent's grounding and validation and is not metered.
10…