CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omniverse-realtime-viewer

Use as the top-level router for Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering, and focused viewer reference documents.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/omniverse-realtime-viewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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-executed orchestrator document: lean, directive, sequenced, with explicit validation and failure-routing steps and a clean one-level reference structure whose cited files all exist. Its main limitation is that it contains no inline executable examples, deferring all commands and code to the referenced files, which is defensible for a router skill but leaves minor gaps.

DimensionReasoningScore

Conciseness

The body is lean and directive ("Use OVRTX for USD/3D rendering... A missing GPU means rendering is unverified, not a reason to substitute a browser 3D renderer") with no explanations of concepts Claude already knows. It falls short of 5 only through minor repetition, such as the USD BRep routing via references/dependencies/README.md being restated in two separate sections.

4 / 5

Actionability

Guidance is concrete and specific for an orchestrator skill: named files per decision point ("select its recipe through `references/routing.md`", "Resolve the selected libraries through `references/dependencies/README.md`") plus actionable rules ("A browser screenshot does not validate a native window or a different transport"). It is not 5 because all executable detail (commands, code) is delegated to references rather than present even as minimal inline examples.

4 / 5

Workflow Clarity

"Start With The App" gives a clear 5-step numbered sequence with an explicit validation checkpoint (step 5: "Validate the actual delivery path with references/validation.md") and error-recovery routing ("When a runtime failure needs diagnosis, use references/troubleshooting/README.md... before changing the architecture"). It is not 5 because validation and feedback loops are named/delegated to reference files rather than expressed as inline checkpoints.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview with well-signaled, one-level-deep references (references/<topic>/README.md) covering routing, dependencies, conventions, validation, and each capability area; all 22 referenced paths were verified to exist in the bundle, and references/routing.md serves as an index over the ~80-entry reference tree. This matches the anchor 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

17

/

20

Passed

Description

52%Weight 40%Scale 1-5

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 highly distinctive and domain-specific but functionally thin: it says the skill is a 'top-level router' without stating any concrete capability or explicit use-when triggers. Adding what the skill actually helps build and when to invoke it would materially improve it.

Suggestions

State 2-3 concrete capabilities instead of only the routing role, e.g. 'Build responsive USD viewers with OVRTX rendering, local or streamed (ovstream) delivery, and XR shells' so the 'what' is actionable.

Add an explicit trigger clause, e.g. 'Use when the user asks for a USD/3D viewer, Omniverse rendering, XR/spatial viewer, streaming delivery, or stylized (toon/X-Ray) rendering.'

Include missing natural synonyms such as 'OpenUSD', 'streaming', '3D viewer', and 'simulation' to broaden trigger coverage for users who don't use NVIDIA product names.

DimensionReasoningScore

Specificity

The description names many domains ("Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering") but the only action offered is the generic "Use as the top-level router", matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete capability verb (build, render, stream, integrate) is stated, and not a 1 because the domain is richly and specifically named.

2 / 5

Completeness

A 'what' is present (a top-level router over the listed viewer topic areas) but 'when' is only weakly implied by "Use as..."; there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because the 'what' is clear, but below anchor 4 because usage triggers are not explicit.

3 / 5

Trigger Term Quality

Terms like "USD apps", "XR delivery", "Omniverse", "GPU processing", and "stylized rendering" are natural for this niche, but common variations and synonyms are missing ("OpenUSD", "streaming", "3D viewer", and "simulation" despite simulation being a major body section). This fits 'Some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Omniverse Realtime Viewer USD apps, XR delivery, SPG GPU processing, stylized rendering" carves out a clear niche with distinct, branded trigger terms (Omniverse, USD, XR, SPG) and minimal risk of triggering for unrelated skills.

5 / 5

Total

13

/

20

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.

Validation — 12 / 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: 21 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

NVIDIA/skills

Path

skills/omniverse-realtime-viewer/SKILL.md

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.