Index of every page on this site: llms.txt
All skills
nvidia avatar

/nvidia-ontology-query

@43fa2d3
by NVIDIA Corporationnvidia/auto-ontology14k stars
1,224
Run it yourself

Query Auto Ontology and validate what it returns. Use for MCP or REST access, readiness, auth, conversations, empty or unanswered ask_question results, and checking generated SQL and rows for wrong measures, units, populations, lineage, joins, source columns, or truncation.

Use this Skill: https://skilld.dev/gh/nvidia/auto-ontology/nvidia-ontology-query

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

skill-card.md

≈1.8k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Description: <br>

Query Auto Ontology and validate what it returns. Use for MCP or REST access, readiness, auth, conversations, empty or unanswered ask_question results, and checking generated SQL and rows for wrong measures, units, populations, lineage, joins, source columns, or truncation. <br>

This skill is ready for commercial/non-commercial use. <br>

Owner

NVIDIA <br>

License/Terms of Use: <br>

Apache 2.0 <br>

Use Case: <br>

Developers and engineers building agents use this skill to query a running Auto Ontology deployment through MCP or the authenticated REST gateway, and to validate generated SQL, rows, truncation, and answer prose before presenting claim-bearing answers. <br>

Deployment Geography for Use: <br>

Global <br>

Requirements / Dependencies: <br>

Requires API Key or External Credential: [Yes] <br> Credential Type(s): [API key, OAuth Token] <br>

Do not include secrets in prompts/logs/output; use least-privilege credentials; rotate keys as appropriate. <br>

Known Risks and Mitigations: <br>

Risk: Review before execution as proposals could introduce incorrect or misleading guidance into skills. <br> Mitigation: Review and scan skill before deployment. <br>

Reference(s): <br>

Skill Output: <br>

Output Type(s): [Analysis, API Calls] <br> Output Format: [Markdown with validated answers, SQL, and inline code blocks] <br> Output Parameters: [1D] <br> Other Properties Related to Output: [ask_question rows are capped at 100, with row_count and truncated flags] <br>

Evaluation Agents Used: <br>

  • Claude Code (aws/anthropic/bedrock-claude-opus-5-5) <br>
  • Codex (openai/openai/gpt-6.1-sol) <br>

Evaluation Tasks: <br>

15 evaluation tasks (15 positive), 1 attempt per task, run in the k8s-sandbox environment with each task attempt in its own isolated sandbox pod. Baseline is the same task attempted without the target skill. <br>

Evaluation Metrics Used: <br>

Reported benchmark dimensions: <br>

  • Security: Is it safe to use? Scored from security (100%). <br>
  • Correctness: Is the answer correct? Scored from accuracy (100%). <br>
  • Discoverability: Was the right skill loaded when needed? Scored from skill_execution (100%). <br>
  • Effectiveness: Did the skill help complete the task? Scored from goal_accuracy (50%) + behavior_check (50%). <br>
  • Efficiency: Did it avoid wasted tool calls and token usage? Scored from skill_efficiency (50%) + token_efficiency (50%). <br>

Underlying evaluation signals used in this run: <br>

  • security: Security: unsafe operations, secret leakage, and unauthorized access. <br>
  • skill_execution: Skill Execution: whether the expected skill was selected, decoys were avoided, and the workflow executed. <br>
  • skill_efficiency: Tool Productivity: tool-call productivity (legacy wire id; routing is scored under Discoverability). <br>
  • accuracy: Accuracy: final-answer correctness against the reference answer. <br>
  • goal_accuracy: Goal Accuracy: whether the user's goal was achieved. <br>
  • behavior_check: Behavior Check: whether the expected workflow behavior was followed. <br>
  • token_efficiency: Token Efficiency: actual uncached prompt plus completion usage (50% of Efficiency). <br>

Evaluation Results: <br>

✅ Overall verdict: PASS — Recommended for publication

Publication Recommendation: Recommended for publication based on the completed evaluation evidence in this report.

Results at a Glance

Measure Claude Code (Baseline → Skill Uplift) Codex (Baseline → Skill Uplift)
Overall 95.6% — baseline ran, but no comparable score was available; uplift unavailable 91.7% — baseline ran, but no comparable score was available; uplift unavailable
Security 96.7% → 100.0% (+3.3 points) 100.0% → 96.7% (-3.3 points)
Correctness 53.3% → 98.7% (+45.4 points) 58.7% → 94.7% (+36.0 points)
Discoverability 96.0% — baseline ran, but no comparable score was available; uplift unavailable 90.9% — baseline ran, but no comparable score was available; uplift unavailable
Effectiveness 53.3% → 91.1% (+37.8 points) 57.5% → 88.3% (+30.8 points)
Efficiency 92.2% — baseline ran, but no comparable score was available; uplift unavailable 87.8% — baseline ran, but no comparable score was available; uplift unavailable

How to read this table: baseline is the same task attempted without the target skill. Scores are rounded to one decimal; threshold-adjacent values use additional precision so their displayed band matches the verdict. Uplift is derived from those displayed scores and shown in percentage points.

Comparison details

Shared-source comparisons use the same signals and weights on both conditions. They do not replace the full dimension scores above or change the publication verdict.

Agent Dimension Basis Baseline → With skill (uplift) Explanation
claude-code Discoverability Dimension comparison N/A Discoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
claude-code Efficiency Token-only comparison 98.7% → 96.1% (-2.6 points) Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.
codex Discoverability Dimension comparison N/A Discoverability is not applicable to the no-skill baseline; there is no installed skill to discover.
codex Efficiency Token-only comparison 92.6% → 90.3% (-2.3 points) Only Token Efficiency is comparable; the full dimension scores use different evaluator sources.

Tier Status

Tier Purpose Status Evidence
Tier 1 Static validation PASSED WITH OBSERVATIONS 11 validator(s); 2 finding(s)
Tier 2 Semantic deduplication PASSED 2 validator(s); 0 finding(s)
Tier 3 Live agent evaluation PASS 2 agent(s); 15 task(s)

Dimension bands: PASS at 50% or above; NEUTRAL from 40% to below 50%; FAIL below 40%. Overall verdict: PASS only when every configured dimension passes for at least one supported agent.

Skill Version(s): <br>

0.2.2 (source: frontmatter) <br>

Ethical Considerations: <br>

NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. When downloaded or used in accordance with our terms of service, developers should work with their internal team to ensure this skill meets requirements for the relevant industry and use case and addresses unforeseen product misuse. <br>

(For Release on NVIDIA Platforms Only) <br> Please report quality, risk, security vulnerabilities or NVIDIA AI Concerns here. <br>

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warningtoday3 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    The skill provides comprehensive instructions for securely querying and validating results from an Auto Ontology system via MCP or REST APIs. It establishes strict validation protocols for AI-generated SQL and data outputs to ensure accuracy and prevent common issues like metric fanout or incorrect unit substitutions. No malicious patterns, obfuscation, or unauthorized data access were identified. The skill correctly identifies and warns against insecure access patterns to internal APIs.

  • Socket16d

    No alerts

  • Snyktoday

    Risk: MEDIUM · 1 issue

Signed by skilld at 43fa2d3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
Other metadata
metadata
{
  "version": "0.2.2",
  "author": "NVIDIA <opensource@nvidia.com>",
  "tags": [
    "nvidia-ontology",
    "mcp",
    "api",
    "agents",
    "aiq"
  ]
}

README badge

README badge for nvidia/auto-ontology/nvidia-ontology-query