agentleFS
NVIDIAKnown publisherNVIDIA/xr-ai/skills/setup/SKILL.md

setup

Skill103 starsChanged 12 days agoApache-2.0View on GitHub

Prepare an NVIDIA xr-ai checkout and prerequisites. Use for initial installation, cloning, or development setup, not routine work in a prepared checkout. Use run-demo for a running browser demo.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use choices the user already supplied, ask for any missing choice, then tailor the pointers below to the answers.

    line 19
  2. Very specific:

    Before giving setup steps, require a copy of this skill from <ref>.

    line 24
  3. Very specific:

    Local: read the matching version of the requirements page at https://nvidia.github.io/xr-ai/<ref>/getting_started/requirements.html, …

    line 36
  4. Distinctive:

    Remote/hosted: read the same versioned requirements page: the hub still needs an NVIDIA GPU with NVENC and NVDEC, even when inference is …

    line 40
  5. Distinctive:

    Working contract: read AGENTS.md for shared engineering guidance, workflow routing, and canonical references.

    line 56
  6. Very specific:

    Prerequisites: check the selected environment against docs/source/getting_started/requirements.md and report missing requirements.

    line 68
  7. Very specific:

    Ask before privileged host changes, system package installation, daemon restarts, or reboots.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “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 -->

Set up an XR AI checkout

Prepare a checkout and its prerequisites for development. The linked docs hold the procedures. Paths are relative to the repo root, so clone before following them.

First: two setup questions

Use choices the user already supplied, ask for any missing choice, then tailor the pointers below to the answers.

  1. Release or main? Build against the latest release tag (default) or main. This selects <ref> for the skill, checkout, and documentation. Before giving setup steps, require a copy of this skill from <ref>. If this copy's source ref differs or is unknown, retrieve it from https://raw.githubusercontent.com/NVIDIA/xr-ai/<ref>/skills/setup/SKILL.md and continue with that copy. If the file is absent at a release tag, explain that setup is unavailable at that release and ask before using main for the skill, checkout, and docs. For other retrieval failures, stop and ask whether to retry. Use https://nvidia.github.io/xr-ai/main/ for main, or replace main with the selected release tag. https://nvidia.github.io/xr-ai/ opens the newest complete documentation set and can fall back to main when the release lacks current entry points.
  2. Local or remote GPU? Models on the local GPU, or a hosted/remote endpoint?
    • Local: read the matching version of the requirements page at https://nvidia.github.io/xr-ai/<ref>/getting_started/requirements.html, including the VRAM table. Replace <ref> with main or the selected release tag.
    • Remote/hosted: read the same versioned requirements page: the hub still needs an NVIDIA GPU with NVENC and NVDEC, even when inference is remote. Follow docs/source/guides/deploying-with-nim.md to configure and validate the application's required endpoints, including remote speech when selected. Read docs/source/getting_started/credentials.md for credential sources.

Where everything is

  • Repo: git clone https://github.com/NVIDIA/xr-ai.git, then check out the ref chosen above (latest release tag, run in the clone: git tag --list 'v*' | python3 .github/scripts/select_latest_docs_release.py; it prefers stable releases over prereleases). Use the selected tag in documentation URLs; the site landing page can fall back to main. If the selector prints no tag, remain on main and tell the user that no release tag was found.
  • Working contract: read AGENTS.md for shared engineering guidance, workflow routing, and canonical references.
  • Docs: docs/source/; published versioned site at https://nvidia.github.io/xr-ai/.
  • Reference sample: agent-samples/conversation-example/, the one to study and copy for new voice-and-vision applications. The separate run-demo workflow still uses the deprecated Simple VLM browser demo.
  • Building your application: docs/source/guides/building-your-app.md, the consumer path for choosing SDK layers, copying the reference, and verifying without hardware.
  • Preparing an upstream sample: docs/source/guides/adding-a-sample.md, full repository boilerplate templates.
  • Prerequisites: check the selected environment against docs/source/getting_started/requirements.md and report missing requirements. Ask before privileged host changes, system package installation, daemon restarts, or reboots. Configure credentials using docs/source/getting_started/credentials.md. Use existing credential sources without printing secrets.
  • Running a sample: the quickstart document is at https://nvidia.github.io/xr-ai/<ref>/getting_started/quickstart.html, with <ref> replaced as above.

Setup complete

Return the checkout path and ref, selected model environment, and any remaining prerequisite or credential blockers. Do not launch model servers or the sample.

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.