Request access as a SimReady Central contributor
This repository is publicly accessible, but you have to accept the conditions to access its files and content.
Access is for onboarded contributors. After requesting access, open a discussion titled Collaborator request: <organization>, as Get started as a contributor on this page describes. A request without that discussion is not reviewed.
Log in or Sign Up to review the conditions and access this dataset content.
Welcome to SimReady Central
SimReady Central is in Alpha. We are accepting contributors through the Community tab.
SimReady Central connects creators and users of simulation-ready digital twins for Physical AI. It helps robotics researchers, simulation engineers, and application developers discover assets for training, testing, and industrial planning.
Contributors host and version their asset packages in their own Hugging Face
datasets. SimReady Central provides a shared index of reviewed contributions:
a contributor submits the exact package versions for NVIDIA's review by pull
request on this dataset, nvidia/simready-central-library. You retain
ownership of your assets and control their releases and licenses.
SimReady assets combine OpenUSD content with simulation metadata and validation evidence for a defined use case.
Read the SimReady Central documentation for the full workflow, requirements, and resources.
Get started as a contributor
The files of this dataset are open to onboarded contributors only. To be onboarded:
- Use your company's Hugging Face organization. Your packages are published under it, and your account is a member of it. NVIDIA looks at whether Hugging Face has verified the organization: an administrator sets its e-mail domain in its settings, under Organization Domain name, and its page shows the Verified badge once Hugging Face has confirmed it. See Organization domain name.
- Request access with the form at the top of this page.
- Open a discussion in the
Community tab,
titled
Collaborator request: <organization>, with the template below filled in. - Wait for the automatic check. It answers in the discussion within a minute.
- Confirm by e-mail. An NVIDIA reviewer writes to the e-mail address of your Hugging Face account. Reply from your company account.
- Wait for NVIDIA's answer in the discussion. Once your access request is approved, continue with Submit assets below. You can begin preparing and validating assets while your request is being reviewed.
Collaborator request template
Organization:
Namespace: <your organization's name on Hugging Face>
Intended dataset URL (or planned namespace/dataset name):
Asset types and brief description:
Intended simulation use case:
Collaborator approval starts onboarding. Individual asset acceptance and inclusion in NVIDIA discovery services require separate review and depend on applicable licensing and indexing requirements.
Find and use assets
Visit the SimReady Central Hugging Face Space to find assets for your simulation workflow. Review each asset's license, target profile, and validation evidence before use, and use the registered revision when you need a reproducible asset version.
The lists of reviewed package versions are also on GitHub,
NVIDIA-Omniverse/simready-central,
a read-only mirror of this dataset's submissions/ that needs no access
request. It carries what a reader needs to browse a list locally, and
nothing is contributed there.
Submit assets
The recommended way to submit assets is with an agent. Log in with the
onboarded account (hf auth login), and tell your agent:
Download the submission skill with
hf download nvidia/simready-central-library .agents/skills/submit-simready-assets/SKILL.md --repo-type dataset --local-dir <folder>
then read and follow it, and help me submit the assets in
<asset-source-folder> to NVIDIA SimReady Central.
The agent will inspect the local environment, identify any missing inputs, and
guide the submission through simready-manage submit β which validates,
packages, and uploads each asset β and then through creation of the pull
request on the SimReady Central dataset. It will ask for confirmation before
modifying source assets or making remote changes, and it stops after opening or
updating the pull request. NVIDIA then reviews the submission and manages the
remaining catalog process.
Users who want to inspect the underlying requirements and commands can refer to the detailed OEM asset submission guide, and every check it must pass in Acceptance criteria.
What the dataset holds
nvidia/simready-central-library
βββ README.md
βββ AGENTS.md # Which skill an agent loads before touching what
βββ CLAUDE.md # Includes AGENTS.md
βββ CONTRIBUTING.md # The sign-off every commit needs
βββ LICENSE
βββ .agents/
β βββ skills/
β βββ index-to-library/
β β βββ SKILL.md # Agent entry point for browsing a submission's assets locally
β βββ submit-simready-assets/
β βββ SKILL.md # Agent entry point for OEM submissions
βββ docs/
β βββ onboarding.md
β βββ acceptance-criteria.md # Every check, its id, and what it means
β βββ oem-asset-submission-guide.md
β βββ index-to-library-guide.md # Pull a submission's packages and browse them locally
β βββ examples/
β β βββ index_to_library.py # Reads the pulled packages into library.json
β β βββ library_page.py # Renders library.json as a local web page
β βββ foundations-spec.md
βββ submissions/
βββ <Hugging Face namespace>/
βββ <dataset name> # Text file containing package-definition URLs
The checks run on NVIDIA's side when a pull request is opened or pushed to, and report on the pull request as comments.
Each dataset entry under submissions/ is a text file, not a directory or a
copy of the dataset. It contains the complete, authoritative package list for
that Hugging Face dataset. For example, packages stored in
nvidia/simready-assets are submitted in:
submissions/nvidia/simready-assets
Each non-empty line is an immutable URL to a package definition:
https://huggingface.co/datasets/<namespace>/<dataset>/resolve/<40-character-commit>/<logical-asset-name>/com.nvidia.simready.packaging.json
To add or update packages, edit the same dataset file and submit the complete new list. To remove package versions, remove their URL lines but retain every other version that should remain available. Changes take effect only after the pull request is reviewed and merged.
Browsing a submission locally
A submission file is an index: each line pins one package to the Hugging Face commit it was reviewed at. To see what those packages contain, whether it is your own submission or one that is already merged, pull them to your machine and browse them as a local library. Tell your agent:
Download the skill with
hf download nvidia/simready-central-library .agents/skills/index-to-library/SKILL.md --repo-type dataset --local-dir <folder>
then read and follow it, and build a local library of the assets in
submissions/<namespace>/<dataset>.
The agent downloads the listed packages into a directory of your choosing,
reads each one into library.json, one record per asset with its source URL,
owner, version, license, validation and benchmark results, and renders
library.html, a page that filters and groups the assets by those fields.
Nothing is uploaded or modified. The agent stops once the page is rendered and
reports what the packages carry, including what they lack.
The index-to-library guide has the commands
behind the skill and traces every field of the library to the file in the
package and the tool that reads it, so the same reads can go into your own
pipeline. The two scripts it runs are in docs/examples/. It needs the
.venv-submit environment from the submission guide's one-time setup and read
access to the dataset.
Additional references
- Downloads last month
- 977