agentleFS
NVIDIAKnown publisherNVIDIA/xr-ai/skills/build-your-app/SKILL.md

build-your-app

Skill103 starsChanged 12 days agoApache-2.0View on GitHub

Build, adapt, run, or verify a custom application on NVIDIA xr-ai, whether or not the repository has been cloned. Use run-demo to try the Simple VLM browser demo.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the release and model environment already selected during setup.

    line 14
  2. Distinctive:

    Follow the guide's selected model-environment path and verification steps.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Build your XR AI application

Use the release and model environment already selected during setup. Ask for any missing choice: latest stable release (the default, with the latest prerelease as a fallback when no stable release exists) or main, and local model services or hosted endpoints. Then follow the build-your-application guide that matches that ref. Before a checkout exists, use https://nvidia.github.io/xr-ai/<ref>/guides/building-your-app.html, replacing <ref> with the selected release tag or main. The /latest/ alias can fall back to main when a release lacks current entry points, so do not assume it matches a release checkout. Once the guide creates the checkout, confirm that skills/build-your-app/SKILL.md and docs/source/guides/building-your-app.md exist at the selected ref. If either is absent, ask the user before using main for the skill, guide, and checkout. Then read AGENTS.md for shared engineering guidance and workflow routing. Continue with the guide from the checkout as a reference workflow adapted to the application's needs. Follow the guide's selected model-environment path and verification steps. Report which requirements passed and which remain unverified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.