CtrlK
BlogDocsLog inGet started
Tessl Logo

omniverse-realtime-viewer

Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/nvidia/skills/omniverse-realtime-viewer/SKILL.md

The canonical home for this skill is omniverse-realtime-viewer in NVIDIA/skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured orchestrator: it routes to a verified set of one-level-deep references, states concrete non-negotiable rules, and embeds a validation checkpoint and checklist. The main weakness is structural redundancy between the Read Order and Build Workflow sections.

Suggestions

Consolidate the overlapping 'Read Order' and 'Build Workflow' sequences, which both walk classify-select-references-implement-render-first-validate; merge them or have one cross-reference the other to remove the redundancy.

Trim or fold the brief 'Examples' section into the Read Order, since reference selection per delivery path is already covered there and in 'Focused Reference Families'.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic concept explanations) and the reference catalogue is purposeful, but the 'Read Order' and 'Build Workflow' sections repeat the same classify-select-render-first-validate pattern and could be tightened, matching the score-2 anchor 'Mostly efficient but ... could be tightened.'

2 / 3

Actionability

As an instruction-only orchestrator it gives concrete, specific directives — exact read order, hard rules ('Use ovrtx', 'Do not substitute WebGL, Three.js, Babylon.js...', 'Keep one owner for renderer.step()') — and a checklist, which is actionable guidance rather than vague direction.

3 / 3

Workflow Clarity

Numbered 'Read Order' and 'Build Workflow' sequences give a clear build order, and an explicit validation checkpoint ('Capture validation evidence before calling the viewer ready') plus a 'Completion Checklist' satisfy the validation requirement rather than capping at 2.

3 / 3

Progressive Disclosure

SKILL.md is a lean overview pointing to one-level-deep references (references/*/README.md), categorized into families with a read order; all 51 referenced paths were verified to exist, giving clear navigation with no deep nesting.

3 / 3

Total

11

/

12

Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific to a clear niche and answers both what and when, but it is terse and leans on abstract/internal phrasing ('top-level router', 'focused viewer reference documents') rather than concrete actions and natural user trigger variations.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger variations users would say, e.g. 'Use when the user requests an Omniverse or OpenUSD realtime viewer app, a streaming or local USD viewer, or viewer UI/UX behavior.'

Name the concrete routing actions the skill performs (classify the delivery path, select recipe plus focused references, enforce ovrtx renderer and ownership conventions) instead of the abstract 'top-level router' label.

DimensionReasoningScore

Specificity

Names the domain ('Omniverse Realtime Viewer USD app') and one abstract action ('top-level router'), but does not list multiple concrete routing actions, matching the score-2 anchor 'Names domain and some actions, but not comprehensive.'

2 / 3

Completeness

'Use as the top-level router for ... USD app requests' provides equivalent explicit trigger guidance stating both what it does and when to use it, so it is not capped at 2 and clearly answers what AND when.

3 / 3

Trigger Term Quality

'Omniverse Realtime Viewer USD app requests' gives some natural domain keywords but is narrow and mixes in internal jargon ('focused viewer reference documents'), missing common variations like 'USD viewer' or 'streaming/local viewer'.

2 / 3

Distinctiveness Conflict Risk

'Omniverse Realtime Viewer USD app' is a narrow, clearly delineated niche with distinct triggers, making accidental triggering of unrelated skills unlikely.

3 / 3

Total

10

/

12

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 57 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.