Nvidia Ontology Management
NVIDIAOfficialCreated by NVIDIA
- Skill
- Workflow
- Data and AI
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow for modeling, inspecting, and publishing semantic definitions in Auto Ontology. It emphasizes maintaining a rigorous semantic layer by separating routine metadata edits from complex modeling tasks and governed publication. The skill guides users through discovering current meanings, defining concepts and relationships, validating SQL attributes, and performing controlled model imports or exports. It is designed for environments where semantic accuracy and durable, governed changes are critical, ensuring that all modifications are backed by evidence and verified through exact readback procedures.
What it does
- Inspects and edits semantic metadata like terms, relationships, and measures.
- Validates SQL attributes and semantic definitions before application.
- Manages bulk model imports and exports for catalog and semantic layer updates.
- Enforces publication gates to ensure changes are durable and verified.
- Provides workflows for modeling concepts, relationships, and reusable measures.
- Facilitates verification of persisted changes through exact readback and comparison.
When to use it
- When you need to define or update business concepts, relationships, or measures in Auto Ontology.
- When performing bulk updates to the semantic model via import/export.
- When you need to ensure a semantic change is governed, validated, and durable.
- When troubleshooting semantic model inconsistencies or validation failures.
Advantages
- Ensures semantic consistency through rigorous modeling and validation workflows.
- Provides a clear path for governed publication and rollback of semantic models.
- Reduces risk by requiring verification of persisted changes rather than relying on API success.
- Supports complex semantic structures like derived SQL attributes and relationship paths.
Usage examples
- “Define a new run-grain measure for revenue in Auto Ontology.”
- The agent will guide you through the modeling.md workflow, requiring you to define the expression, grain, units, and additive dimensions before applying the change.
- “Promote a revised semantic model to production.”
- The agent will initiate the publication.md workflow, including backing up the current state, applying the change in isolation, and performing an exact readback comparison.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/nvidia-ontology-management/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip nvidia-ontology-management.zip -d .agents/skills
Documentation by NVIDIA
<!-- 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.
Choose the focused workflow before acting:
routine inspection or metadata edits: continue below and use write-api.md;
concepts, relationships, measures, units, grain, or policies: use modeling.md;
model promotion or reusable analytical results: use 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.
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. 403 means the owner's role
lacks that permission, not that the path is wrong.
Instructions
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).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.
State the proposed change to the user (term rename, new SQL attribute, import, and so on). Do not silently rewrite the glossary.
Validate SQL before create/update:
POST /api/sql-attributes/validate. A parse failure is HTTP 422, notvalid: false.Apply the smallest write that matches the request (see write-api.md).
Compilation is not a hidden side effect. Check
GET /api/semantic-compilation/status. Do not callPOST /api/semantic-compilation/resetas cleanup — it is an asynchronous, destructive rebuild of every database's compiled layer, returns 202, and requiressemanticCompilation:manage.Verify the persisted change, not merely request success. Model imports require a scoped backup and exact re-export comparison; see publication.md. Then use MCP
check_answerable/ask_question(or RESTPOST /api/question-entity-coverageandPOST /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_columnsorGET /api/terms/{term_id}/column-attributesTerm → derived SQL: MCP
get_term_sql_attributesTable → terms and SQL attributes: MCP
describe_tableorGET /api/exploration/tables/{table_id}/detailsSemantic 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. PermissionmodelInterchange:export. Body may set catalog database IDs indatabases(empty = all) andformat(auto_ontologyorossie).POST /api/model/import— multipart YAML; native Auto Ontology (data_layer/semantic_layer) or Apache Ossie (version,name,datasetsat the root). Queryreplace(default true) andembed(default true). PermissionmodelInterchange:import. Can replace existing data — confirm with the user beforereplace=true, apply first in isolation, and use the exact readback workflow in publication.md.
Examples
To define a run-grain measure, follow the evidence and counterexample workflow in modeling.md.
To revise and promote a model, back up the exact scope and follow the staged readback workflow in 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
nvidia-ontology-query— how to call Auto Ontology and validate query resultsnvidia-ontology-setup— deployment not readymcp/auto_ontology_mcp/tools.py— live read-tool allow-list
Files
- ATTRIBUTION.mdAdded by AutoGineer936 B
- BENCHMARK.md9.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md6.2 KiB
- assets/runtime-contract.yaml2.4 KiB
- evals/evals.json10.4 KiB
- references/modeling.md3.8 KiB
- references/publication.md4.7 KiB
- references/write-api.md5.4 KiB
- skill-card.md4.6 KiB
- skill.oms.sig5.4 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/nvidia-ontology-management · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nvidia-ontology-management.zip