How do I install the Usd Identifiers And Names skill?

Run npx skillmds@latest add nvidia-omniverse/usd-identifiers-and-names in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Usd Identifiers And Names skill do?

Use this skill when implementing or verifying USD identifier and name handling. It is listed under Coding & Dev Tools on SkillMD.

Is Usd Identifiers And Names safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Usd Identifiers And Names?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Usd Identifiers And Names free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Usd Identifiers And Names?

NVIDIA-Omniverse (@nvidia-omniverse) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Usd Identifiers And Names by nvidia-omniverse

Name: Usd Identifiers And Names
Author: NVIDIA-Omniverse

File contents

usd-identifiers-and-names

Use this skill when implementing or verifying USD identifier and name handling.

Spec Sources

specification/document_data_model/README.md sections Specs > Names and Metadata Fields > Allowed Names
specification/file_formats/README.md sections Keywords and Identifiers

Pinned tag / commit: v1.0.1

Provides

Field names
Prim names
Variant set names
Variant names
Property names
Namespaced property names
ASCII prim type names
Keywordless USDA identifiers
Embedded-grammar identifier scanner capability

Contract

Identifiers are UTF-8 / Unicode code point sequences constrained by the spec's XID start/continue rules. ASCII-only shortcuts may be used only where the spec requires ASCII, such as USDA prim type names.

Property names may contain namespace separators (:). Attribute and relationship specs sharing a parent may not have the same property name.

This skill owns the reusable identifier scanner capability described by contracts/capabilities/identifier-scanner.json. Dependent parsers should be able to ask this skill to consume one identifier, one identifier-continuation code point, or one namespaced property name from an offset in caller-owned text. The scanner may return spans, offsets, views, or target-native name values; it does not need to allocate strings.

The scanner capability owns UTF-8 decoding validity, XID start/continue policy, keywordless identifier policy when requested, and namespaced-name component validity. Callers own their surrounding grammar delimiters and diagnostics.

Boundary Guards

Defer path parsing to usd-paths.

Defer USDA tokenization details such as comments, strings, numbers, and asset refs to usda-lexical-format.

Do not silently accept reserved USDA keywords where the grammar requires a keywordless identifier.

Test Obligations

Valid ASCII and Unicode identifiers
Embedded UTF-8 identifier scanner spans
Namespaced properties
Keyword rejection in keywordless identifier contexts
ASCII-only prim type names
Scanner behavior for embedded identifiers, including returned end offsets and failures without consuming caller grammar delimiters
all cases in goldens/unit/usd-identifiers/identifier-scanner.json

---name: usd-identifiers-and-namesdescription: Use this skill when implementing or verifying USD identifier and name handling.---# usd-identifiers-and-namesUse this skill when implementing or verifying USD identifier and name handling.## Spec Sources- `specification/document_data_model/README.md` sections `Specs > Names` and `Metadata Fields > Allowed Names`- `specification/file_formats/README.md` sections `Keywords` and `Identifiers`Pinned tag / commit: `v1.0.1`## Provides- Field names- Prim names- Variant set names- Variant names- Property names- Namespaced property names- ASCII prim type names- Keywordless USDA identifiers- Embedded-grammar identifier scanner capability## ContractIdentifiers are UTF-8 / Unicode code point sequences constrained by the spec'sXID start/continue rules. ASCII-only shortcuts may be used only where the specrequires ASCII, such as USDA prim type names.Property names may contain namespace separators (`:`). Attribute andrelationship specs sharing a parent may not have the same property name.This skill owns the reusable identifier scanner capability described by`contracts/capabilities/identifier-scanner.json`. Dependent parsers should beable to ask this skill to consume one identifier, one identifier-continuationcode point, or one namespaced property name from an offset in caller-owned text.The scanner may return spans, offsets, views, or target-native name values; itdoes not need to allocate strings.The scanner capability owns UTF-8 decoding validity, XID start/continue policy,keywordless identifier policy when requested, and namespaced-name componentvalidity. Callers own their surrounding grammar delimiters and diagnostics.## Boundary GuardsDefer path parsing to `usd-paths`.Defer USDA tokenization details such as comments, strings, numbers, and assetrefs to `usda-lexical-format`.Do not silently accept reserved USDA keywords where the grammar requires akeywordless identifier.## Test Obligations- Valid ASCII and Unicode identifiers- Embedded UTF-8 identifier scanner spans- Namespaced properties- Keyword rejection in keywordless identifier contexts- ASCII-only prim type names- Scanner behavior for embedded identifiers, including returned end offsets and failures without consuming caller grammar delimiters- all cases in `goldens/unit/usd-identifiers/identifier-scanner.json`

Frequently asked questions

Usd Identifiers And Names