New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Nemoclaw Contributor Onboard

by NVIDIA in NVIDIA/NemoClaw

Set up, repair, or check a NemoClaw contributor checkout. An agent skill from NVIDIA/NemoClaw.

OfficialApache-2.0Auto-check passed

Install Nemoclaw Contributor Onboard

skills CLI
$ npx skills add NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-contributor-onboard --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NemoClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nemoclaw-contributor-onboard .claude/skills/nemoclaw-contributor-onboard && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nemoclaw-contributor-onboard
GitHub stars
23k
Token cost
~1.4k tokens
SKILL.md length
713 words
Files
3
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Set up, repair, or check a NemoClaw contributor checkout. An agent skill from NVIDIA/NemoClaw.

  • Works in 4 steps: Read the root AGENTS.md and… → Inspect the worktree and current branch… → Refresh the trusted origin/main… → …
  • SKILL.md covers Establish Trust First, Route by Intent, Handle User-Controlled Changes and Decide on Runtime Onboarding, plus 3 more sections
  • Calls npm and gh

What it does

Nemoclaw Contributor Onboard is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Set up, repair, or check a NemoClaw contributor checkout. Also handles requested development CLI exposure, runtime onboarding, and pinned-agent launch.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `agents/openai.yaml` and `evals/evals.json`).

The repository describes itself as: Run agents like Hermes, LangChain Deep Agents, and OpenClaw more securely inside NVIDIA OpenShell with managed inference. The licence is Apache-2.0.

Example prompts

  • “/nemoclaw-contributor-onboard”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the root AGENTS.md and CONTRIBUTING.md completely.
  2. Inspect the worktree and current branch without discarding or overwriting existing changes.
  3. Refresh the trusted origin/main reference, then compare the entire checkout/worktree diff against that up-to-date base before executing…
  4. If an execution surface differs from trusted origin/main, review the diff before running it. Existing implementation authorization covers…

What it can do on your machine

Read from SKILL.md and the folder at commit 4e3bf44. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nemoclaw Contributor Onboard loads about 1.4k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 713 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/NemoClaw at commit 4e3bf44, republished under its Apache-2.0 licence (© NVIDIA). 713 words, ~1,450 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-contributor-onboard/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
nemoclaw-contributor-onboard
description
Set up, repair, or check a NemoClaw contributor checkout. Also handles requested development CLI exposure, runtime onboarding, and pinned-agent launch.
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->

Onboard a NemoClaw Contributor

Use the repository setup script as the executable source of truth. Do not duplicate its dependency, build, hook, CLI-exposure, or readiness logic in agent commands.

Establish Trust First

  1. Read the root AGENTS.md and CONTRIBUTING.md completely.
  2. Inspect the worktree and current branch without discarding or overwriting existing changes.
  3. Refresh the trusted origin/main reference, then compare the entire checkout/worktree diff against that up-to-date base before executing any checkout-local code. Include staged, unstaged, and untracked files; review lockfiles and all transitively executed source, not only the entry script or package manifests.
  4. If an execution surface differs from trusted origin/main, review the diff before running it. Existing implementation authorization covers in-scope repository-local validation. Isolate candidate code from host credentials and host mutations. This includes setup scripts and installed hooks. Stop before execution if that isolation cannot be established. Ask only for exposure or side effects outside that authorization.

Route by Intent

  • Readiness only: run ./scripts/dev-setup.sh --doctor and never run setup, repair, CLI exposure, runtime onboarding, or the pinned agent. Use ./scripts/dev-setup.sh --doctor --json when a machine-readable report helps.
  • Initial checkout setup: run ./scripts/dev-setup.sh from the repository root.
  • Explicit repository repair: run ./scripts/dev-setup.sh --repair only when the user asks to repair or retry repository-local setup.
  • CLI exposure: after explicit approval, run ./scripts/dev-setup.sh --expose-cli.
  • Runtime onboarding: after explicit approval, run ./scripts/dev-setup.sh --with-runtime.

The default and repair modes may update repository-local dependencies, builds, hooks, and the root Python environment. They must not create a gateway or sandbox or expose a host-visible nemoclaw command. CLI exposure is an explicit opt-in that may use an npm link or a user-local shim.

Handle User-Controlled Changes

Require explicit authorization before installing or changing host packages, starting or replacing a container runtime, accepting a license, generating or registering a signing key, changing GitHub state, or changing global Git configuration. Use authorization already supplied for that action and scope; ask only when it is missing.

  • Ask for contributor name and email only when the doctor reports that identity is missing.
  • Prefer repository-local Git identity changes when the user approves them.
  • Use gh auth login -h github.com for missing GitHub authentication and pause for browser or device authentication.
  • Let the user choose and register a Git-supported commit-signing key.
  • Follow ../_shared/git-github-hard-stop.md for authentication, authorization, SSH, remote-access, or push failures.
  • Never print tokens, credential values, private keys, or command output that may contain them.
  • Never place secrets in command arguments, generated reports, or tracked files.

After an approved host, account, identity, or signing remediation, rerun npm run dev:doctor or ./scripts/dev-setup.sh --doctor instead of rerunning setup. Reserve setup and --repair for repository-local dependency, build, or hook repair.

Show full SKILL.md (275 more words)Show less

Decide on Runtime Onboarding

Determine whether the intended issue requires a live gateway or sandbox from its validation boundary. Ask only if that need or the authorization for it is unresolved. Documentation work and isolated unit tests normally do not require runtime onboarding.

If runtime validation is required and the user approves it, run:

bash
./scripts/dev-setup.sh --with-runtime

This delegates to interactive nemoclaw onboard and also opts into development CLI exposure as part of that approved flow. Do not preselect third-party software acceptance, inference provider or model, credentials, sandbox name or resources, messaging integrations, or network policy unless the user already supplied those decisions.

Launch the Pinned Agent Only on Request

When the user specifically asks to use the repository-pinned coding agent, run the doctor first. If readiness fails, report the remediation and obtain authorization for the matching setup or repair mode rather than mutating the checkout automatically. When readiness passes, run:

bash
npm run agent

Pass user-supplied Pi arguments after --. Do not install or invoke a global Pi binary.

Hand Off to the Contributor Lifecycle

This workflow ends after the doctor reports that every contributor-readiness check passes and every approved CLI-exposure, runtime-onboarding, or pinned-agent step is complete. Name the workflow that owns the next stage instead of restating its rules:

  • nemoclaw-contributor-plan-issue refines an issue into capability slices.
  • nemoclaw-contributor-implement-issue implements a slice and owns its tests.
  • nemoclaw-contributor-create-pr publishes the change and owns the branch-state, commit-verification, DCO, template, and review follow-up requirements.

Do not create a branch, commit, push, or PR unless the user's request includes that action.

Report the Result

Summarize repository-local setup performed, doctor status, user-controlled remediations still needed, whether CLI exposure or runtime onboarding ran, and the next safe contributor action.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .agents/skills/nemoclaw-contributor-onboard of NVIDIA/NemoClaw.

  • SKILL.md
  • agents/openai.yaml
  • evals/evals.json

Open the folder on GitHubat commit 4e3bf44

Compare with similar skills

Nemoclaw Contributor Onboard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nemoclaw Contributor Onboard compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Contributor Onboard this skillNVIDIA/NemoClaw23k—~1.4kAutomated safety check: PassApache-2.0
Codewhale Contributor Onboardingcodewhale-hq/Codewhale41k—~1.3kAutomated safety check: PassMIT
Contributor Onboarding DocDonchitos/Claude-Code-Game-Studios26k—~1.4kAutomated safety check: PassMIT
Onboard Contributorrundeck/rundeck6.3k—~848Automated safety check: PassApache-2.0
Checkoutremotion-dev/remotion63k—~166Automated safety check: PassCustom licence
Onboardalirezarezvani/claude-skills28k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Codewhale Contributor Onboarding

    codewhale-hq/Codewhale

    Reports whether a fresh Codewhale checkout is current, builds and passes its tests, and what changed since the contributor was last here, without touching the working tree.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Contributor Onboarding Doc

    Donchitos/Claude-Code-Game-Studios

    Writes an onboarding document for a new contributor or agent, covering project state, conventions and priorities relevant to a chosen role.

    26k GitHub stars~1.4k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Onboard Contributor

    rundeck/rundeck

    Guide a new contributor through the rundeck OSS repo. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~848 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Checkout

    remotion-dev/remotion

    Official

    Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build.

    63k GitHub stars~166 tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • Onboard

    alirezarezvani/claude-skills

    /cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema.

    28k GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Codebase Onboarding

    affaan-m/ECC

    Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

    277k GitHub starsUsed in 3 repos~2k tokens
    DevelopmentAuto-check passed

More from NVIDIA/NemoClaw

All 30 skills in this repo

  • Nemoclaw Maintainer Cross Issue Sweep

    NVIDIA/NemoClaw

    Official

    Find open issues that a NemoClaw PR may also fix or conflict with.

    23k GitHub stars~893 tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Day

    NVIDIA/NemoClaw

    Official

    Run a NemoClaw daytime maintainer pass over release-targeted work.

    23k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemoclaw Contributor Update Dependencies

    NVIDIA/NemoClaw

    Official

    Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Fix E2E Failures

    NVIDIA/NemoClaw

    Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Analyze CI Performance

    NVIDIA/NemoClaw

    Official

    Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.

    23k GitHub stars~644 tokensUpdated today
    Auto-check passed

Questions about Nemoclaw Contributor Onboard

What does Nemoclaw Contributor Onboard do?

Set up, repair, or check a NemoClaw contributor checkout. An agent skill from NVIDIA/NemoClaw. Nemoclaw Contributor Onboard is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Set up, repair, or check a NemoClaw contributor checkout.

How do I install Nemoclaw Contributor Onboard in Claude Code?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard -a claude-code`. Or copy the skill folder (.agents/skills/nemoclaw-contributor-onboard in NVIDIA/NemoClaw) into .claude/skills/nemoclaw-contributor-onboard in your project. Claude Code loads it when a task matches its description.

How do I install Nemoclaw Contributor Onboard in Codex?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard -a codex`. Or copy the skill folder (.agents/skills/nemoclaw-contributor-onboard in NVIDIA/NemoClaw) into .agents/skills/nemoclaw-contributor-onboard in your project. Codex loads it when a task matches its description.

Can I use Nemoclaw Contributor Onboard in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-contributor-onboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemoclaw-contributor-onboard, .gemini/skills/nemoclaw-contributor-onboard, .github/skills/nemoclaw-contributor-onboard and .opencode/skills/nemoclaw-contributor-onboard in your project.

What does Nemoclaw Contributor Onboard need to run?

Going by SKILL.md and its folder, Nemoclaw Contributor Onboard needs the command-line tools its instructions call (npm and gh). Our summary lists: Python 3.

Does Nemoclaw Contributor Onboard access the network?

SKILL.md contains no URLs. Its commands use npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nemoclaw Contributor Onboard safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nemoclaw Contributor Onboard use?

Nemoclaw Contributor Onboard is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemoclaw Contributor Onboard use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemoclaw Contributor Onboard?

Skills that share tags, products or a category with Nemoclaw Contributor Onboard: Codewhale Contributor Onboarding (codewhale-hq/Codewhale, 41k stars), Contributor Onboarding Doc (Donchitos/Claude-Code-Game-Studios, 26k stars), Onboard Contributor (rundeck/rundeck, 6.3k stars) and Checkout (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Contributor Onboard?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NemoClaw, which has 22,706 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 11, 2026.

Source: NVIDIA/NemoClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.