Skip to content
Back to skills

Nerfstudio

ASecurity

"Routes Nerfstudio NeRF, Gaussian Splatting, camera-pose, dataset

  • 247 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
datapythonshellapi

Works with

  • cli
  • api

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 20 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill nerfstudio --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nerfstudio?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Nerfstudio
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-nerfstudio/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-nerfstudio)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: nerfstudio
description: "Routes Nerfstudio NeRF, Gaussian Splatting, camera-pose, dataset
  conversion, training, viewer, evaluation, rendering, export, and
  plugin-extension tasks using its typed CLI and Python APIs."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# Nerfstudio

Use this skill when a task involves the `nerfstudio` package, `ns-*` commands,
NeRF or Gaussian Splatting training, camera-pose conversion, `transforms.json`,
viewer/render/export workflows, or custom Nerfstudio methods and dataparsers.
This is a router: read only the focused route and references needed for the task.

## First checks

- Prefer Python 3.8-3.10 for this 1.1.x-era package and install the public package with `python -m pip install nerfstudio` or an editable install when developing a package.
- Production training/rendering expects a compatible NVIDIA CUDA/PyTorch environment. A CPU path is useful for parser/config/plugin checks and reduced tests, not for claiming GPU throughput.
- Run the bundled read-only diagnostic when the environment is unclear: [`scripts/check_environment.py`](scripts/check_environment.py). Use `--require-cuda` only when the requested workflow truly needs CUDA and `--check-cli` to validate installed entry points.
- Read [`references/architecture-overview.md`](references/architecture-overview.md) when a task crosses data, training, and output stages; read [`references/troubleshooting.md`](references/troubleshooting.md) for cross-cutting failures.

## Route by task

- **Install, entry points, help ordering, shell completion, or safe dataset download planning:** read [`cli-workflows/SKILL.md`](sub-skills/cli-workflows/SKILL.md).
- **Convert images/video/device exports, validate `transforms.json`, or choose a dataparser:** read [`data-preparation/SKILL.md`](sub-skills/data-preparation/SKILL.md).
- **Choose a method, build `ns-train` commands, override configs, resume, or use multi-GPU/logging:** read [`training-and-configs/SKILL.md`](sub-skills/training-and-configs/SKILL.md).
- **Launch the viewer, render camera paths, evaluate metrics, or export point clouds/meshes/Gaussian Splats:** read [`visualization-and-export/SKILL.md`](sub-skills/visualization-and-export/SKILL.md).
- **Add a custom method/dataparser or debug plugin registration:** read [`api-extension/SKILL.md`](sub-skills/api-extension/SKILL.md).

## Standard handoff

1. Establish a valid dataset directory and validate its paths/schema.
2. Build a typed `ns-train` command with method arguments before dataparser arguments.
3. Save and preserve the generated `config.yml`; it is the downstream handoff for viewer, evaluation, rendering, and export.
4. For CUDA workflows, check device availability and memory before starting long jobs; prefer explicit ray/batch limits and an output directory.
5. Do not run original repository tests, examples, downloaders, or infinite viewer services as part of ordinary use. The routes contain safe preflights and distilled recipes.

## Currentness

Read [`references/repo-provenance.md`](references/repo-provenance.md) before using this skill against a checkout whose package version, commit, entry points, or method/dataparser catalog may differ. Refresh the skill when those facts change.

Files in this skill

  • SKILL.md3.2 KB
  • references/architecture-overview.md2.5 KB
  • references/repo-provenance.md1.5 KB
  • references/repo-routing-metadata.json332 B
  • references/troubleshooting.md3.5 KB
  • scripts/check_environment.py4.3 KB
  • sub-skills/api-extension/SKILL.md1.8 KB
  • sub-skills/api-extension/references/api-reference.md1.3 KB
  • sub-skills/api-extension/references/extension-guide.md1.5 KB
  • sub-skills/api-extension/references/troubleshooting.md1.2 KB
  • sub-skills/cli-workflows/SKILL.md2.6 KB
  • sub-skills/cli-workflows/references/cli-reference.md2.6 KB
  • sub-skills/cli-workflows/references/installation-and-backends.md1.9 KB
  • sub-skills/cli-workflows/references/troubleshooting.md1.4 KB
  • sub-skills/cli-workflows/scripts/inspect_ns_cli.py2.7 KB
  • sub-skills/data-preparation/SKILL.md2.6 KB
  • sub-skills/data-preparation/references/data-formats.md1.8 KB
  • sub-skills/data-preparation/references/troubleshooting.md1.8 KB
  • sub-skills/data-preparation/references/workflows.md2.3 KB
  • sub-skills/data-preparation/scripts/validate_nerfstudio_dataset.py6.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.