nemoclaw-contributor-onboard

Prepares a NemoClaw source checkout for contribution using the repository setup script and readiness doctor.

22.3k|3.1k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-onboard
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-onboard
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New contributors to the NemoClaw repository often struggle to configure a development machine correctly, verify readiness, and know which setup mode (initial, repair, doctor, CLI exposure, runtime onboarding) applies to their situation.

Core Features & Use Cases

  • Intent-based routing: Runs ./scripts/dev-setup.sh in the correct mode (default, --doctor, --repair, --expose-cli, --with-runtime) based on whether the user wants readiness checks, initial setup, repair, CLI exposure, or runtime onboarding.
  • Trust-first execution: Compares the checkout against a refreshed trusted origin/main and requires explicit approval before running any changed execution surface.
  • Safe remediation: Pauses for approval before host package changes, Git identity or signing-key configuration, and GitHub authentication, and never exposes secrets in output.
  • Use Case: A new contributor clones NemoClaw and asks to prepare their machine for a first PR; the Skill runs the setup script, verifies readiness with the doctor, and hands off to the issue-planning workflow.

Quick Start

Ask the agent to set up your machine as a NemoClaw contributor and verify the checkout is ready for a first PR.

Frequently Asked Questions about nemoclaw-contributor-onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up my machine for NemoClaw development?

Run `./scripts/dev-setup.sh` from the repository root, which handles dependencies, builds, hooks, and CLI exposure as the executable source of truth. Afterward, verify readiness with `./scripts/dev-setup.sh --doctor`.

How do I check NemoClaw contributor readiness without changing anything?

Run `./scripts/dev-setup.sh --doctor` for a readiness-only check that makes no repository, host, or GitHub changes. Use `--doctor --json` for a machine-readable report.

When should I use dev-setup repair mode versus full setup?

Use `./scripts/dev-setup.sh --repair` only for explicit repository-local dependency, build, or hook problems. Reserve full setup for initial checkout preparation, and rerun the doctor after host or account remediations instead of rerunning setup.

Does NemoClaw contributor setup require a live sandbox or gateway?

No, runtime onboarding via `./scripts/dev-setup.sh --with-runtime` is optional and only needed when the intended issue requires a live gateway or sandbox. Documentation work and isolated unit tests do not require it.

Why does the setup script require approval before running on a modified branch?

The workflow compares the entire checkout against a refreshed trusted `origin/main`, including staged, unstaged, and untracked files. If any execution surface differs, explicit approval is required before running it to prevent executing unreviewed code.