---
name: nvidia-ontology-management
description: >-
  Model and publish Auto Ontology semantics. Use for terms, relationships, measures, imports, MCP write requests, and governed results; not deployment or querying.
license: Apache-2.0
metadata:
  version: "0.2.2"
  author: "NVIDIA <opensource@nvidia.com>"
  tags:
    - nvidia-ontology
    - ontology
    - glossary
    - sql-attributes
    - catalog
title: nvidia-ontology-management
canonical_url: https://skilld.dev/gh/nvidia/auto-ontology/nvidia-ontology-management
last_updated: 2026-11-19T22:03:37.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [assets/runtime-contract.yaml](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/assets/runtime-contract.yaml), [BENCHMARK.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/BENCHMARK.md), [evals/evals.json](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/evals/evals.json), [references/modeling.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/modeling.md), [references/publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md), [references/write-api.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/write-api.md), [skill-card.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/skill-card.md), [skill.oms.sig](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/skill.oms.sig).
>
> If the user asked to install this Skill, run `npx skilld install nvidia/auto-ontology/nvidia-ontology-management`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/nvidia-ontology-management`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/nvidia/auto-ontology/nvidia-ontology-management) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/nvidia-ontology-management`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/nvidia-ontology-management --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/nvidia-ontology-management --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

<!--
SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES.
All rights reserved.
SPDX-License-Identifier: Apache-2.0
-->

# Auto Ontology management and modeling

## Purpose

Inspect and change Auto Ontology's semantic layer without confusing a successful API call
with correct business meaning or durable publication. The machine-readable
inputs, outputs, statuses, gates, and handoffs are in
[runtime-contract.yaml](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/assets/runtime-contract.yaml).

Choose the focused workflow before acting:

- routine inspection or metadata edits: continue below and use
  [write-api.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/write-api.md);
- concepts, relationships, measures, units, grain, or policies: use
  [modeling.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/modeling.md);
- model promotion or reusable analytical results: use
  [publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md).

MCP tools only **read**. Create, patch, import, and compile-reset go through
the Next.js `/api/...` gateway. Governed result rows require an approved source
writer; Auto Ontology has no generic result-row writeback endpoint. Request bodies and
field types live in `docs/openapi/auto-ontology-api.json`; this skill names operations and
permissions only.

## Prerequisites

Use a running, authenticated Auto Ontology deployment. Use `nvidia-ontology-setup` when
the deployment or semantic layer is not ready.

## Limitations

MCP is read-only, Auto Ontology has no generic result-row writeback endpoint, and current
model import and certification APIs do not prove atomic promotion. Follow the
publication gates below and fail closed when exact readback is unavailable.
When asked to write through MCP, say that MCP is read-only and use the REST
write path below.

## Auth

Scripts use an API token (`x-api-key` or `Authorization: Bearer`). Mint it in
the UI (user menu → API Tokens). A token **acts as its owner** — a viewer's
token cannot do admin things. Creating and revoking tokens requires a signed-in
session; a token cannot mint another token.

Writes below need `catalog:edit` unless noted. A term, or a node other than a
column, can also be edited by members of its owner group. `403` means neither the owner's role nor
the row's owner group permits the write, not that the path is wrong.

## Instructions

1. **Discover current meaning** via MCP (`search_terms`, `get_term`,
   `get_term_columns`, `get_term_sql_attributes`, `describe_table`) or REST
   if MCP is absent (`GET /api/terms`, `GET /api/terms/{term_id}`,
   `GET /api/exploration/tables/{table_id}/details`).
2. **Resolve the semantic contract** when meaning changes. Record source
   binding, identity, population, relationship cardinality, measure expression,
   unit, grain, denominator, time, validity, and counterexamples; see
   [modeling.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/modeling.md).
3. **State the proposed change** to the user (term rename, new SQL attribute,
   import, and so on). Do not silently rewrite the glossary.
4. **Validate SQL** before create/update: `POST /api/sql-attributes/validate`.
   A parse failure is **HTTP 422**, not `valid: false`.
5. **Apply** the smallest write that matches the request (see
   [write-api.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/write-api.md)).
6. **Compilation is not a hidden side effect.** Check
   `GET /api/semantic-compilation/status`. Do **not** call
   `POST /api/semantic-compilation/reset` as cleanup — it is an asynchronous,
   destructive rebuild of every database's compiled layer, returns 202, and
   requires `semanticCompilation:manage`.
7. **Verify the persisted change**, not merely request success. Model imports
   require a scoped backup and exact re-export comparison; see
   [publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md). Then use MCP
   `check_answerable` / `ask_question` (or REST
   `POST /api/question-entity-coverage` and `POST /api/chat/completions`) for
   positive and negative behavior checks.

## Semantic relationships and "what does this dataset mean"

Stay on the semantic layer. Do not browse raw schemas to answer meaning.

- Term → columns: MCP `get_term_columns` or
  `GET /api/terms/{term_id}/column-attributes`
- Term → derived SQL: MCP `get_term_sql_attributes`
- Table → terms and stored queries that reference it: MCP `describe_table` or
  `GET /api/exploration/tables/{table_id}/details`
- Semantic hop chain between two terms:
  `GET /api/exploration/terms/{term_id}/path/{other_term_id}`
- Semantic graphs: `GET /api/exploration/graph`,
  `GET /api/exploration/semantic-graph`

These are semantic relationship paths, not generation provenance, source
revision, certification history, or version lineage.

## Bulk import / export

- `POST /api/model/export` — YAML of catalog + semantic layer.
  Permission `modelInterchange:export`. Body may set catalog database **IDs**
  in `databases` (empty = all) and `format` (`auto_ontology` or `ossie`).
- `POST /api/model/import` — multipart YAML; native Auto Ontology
  (`data_layer` / `semantic_layer`) or Apache Ossie (`version`, `name`,
  `datasets` at the root).
  Query `replace` (default true) and `embed` (default true). Permission
  `modelInterchange:import`. Can replace existing data — confirm with the
  user before `replace=true`, apply first in isolation, and use the exact
  readback workflow in [publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md).

## Examples

- To define a run-grain measure, follow the evidence and counterexample workflow
  in [modeling.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/modeling.md).
- To revise and promote a model, back up the exact scope and follow the staged
  readback workflow in [publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md).

## Troubleshooting

For write failures, verify the authenticated owner's permission, distinguish
HTTP 422 parse failures from validation results, and inspect compilation status
before changing the model or resetting compilation.

## See also

- [write-api.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/write-api.md)
- [modeling.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/modeling.md)
- [publication.md](https://skilld.dev/api/skills-raw/nvidia/auto-ontology/nvidia-ontology-management/references/publication.md)
- `nvidia-ontology-query` — how to call Auto Ontology and validate query results
- `nvidia-ontology-setup` — deployment not ready
- `mcp/auto_ontology_mcp/tools.py` — live read-tool allow-list
