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
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
- steerlabs/opensteertheir own version, first seen Nov 8, 2026
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- anombyte93/prd-taskmastertheir own version, first seen Nov 8, 2026
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.
juancruzmunozalbeloSkilladd-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
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
juancruzmunozalbeloSkilladd-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
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/knowledge-work-plugins★ 35ksame name
- garrytan/gbrain★ 32ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.3ksame name
- pytorch/executorch★ 5.2ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- aws/agent-toolkit-for-aws★ 3.4ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- draft-guideSkill
- evaluate-guideSkill
- guide-generation-skillsSkill
- build-your-appSkill
- gh-manage-xr-ai-reviewsSkill
- gh-review-xr-aiSkill
- run-demoSkill
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
- Distinctive: line 19
Use choices the user already supplied, ask for any missing choice, then tailor the pointers below to the answers.
- Very specific: line 24
Before giving setup steps, require a copy of this skill from <ref>.
- Very specific: line 36
Local: read the matching version of the requirements page at https://nvidia.github.io/xr-ai/<ref>/getting_started/requirements.html, …
- Distinctive: line 40
Remote/hosted: read the same versioned requirements page: the hub still needs an NVIDIA GPU with NVENC and NVDEC, even when inference is …
- Distinctive: line 56
Working contract: read AGENTS.md for shared engineering guidance, workflow routing, and canonical references.
- Very specific: line 68
Prerequisites: check the selected environment against docs/source/getting_started/requirements.md and report missing requirements.
- Very specific: line 70
Ask before privileged host changes, system package installation, daemon restarts, or reboots.
“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.
Files
<!--
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.
- 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 fromhttps://raw.githubusercontent.com/NVIDIA/xr-ai/<ref>/skills/setup/SKILL.mdand continue with that copy. If the file is absent at a release tag, explain thatsetupis unavailable at that release and ask before usingmainfor the skill, checkout, and docs. For other retrieval failures, stop and ask whether to retry. Usehttps://nvidia.github.io/xr-ai/main/formain, or replacemainwith the selected release tag. https://nvidia.github.io/xr-ai/ opens the newest complete documentation set and can fall back tomainwhen the release lacks current entry points. - 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>withmainor 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.mdto configure and validate the application's required endpoints, including remote speech when selected. Readdocs/source/getting_started/credentials.mdfor credential sources.
- Local: read the matching version of the requirements page at
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 tomain. If the selector prints no tag, remain onmainand tell the user that no release tag was found. - Working contract: read
AGENTS.mdfor 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 separaterun-demoworkflow 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.mdand report missing requirements. Ask before privileged host changes, system package installation, daemon restarts, or reboots. Configure credentials usingdocs/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.
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
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.

