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 Update Docs

by NVIDIA in NVIDIA/NemoClaw

Update NemoClaw documentation for merged behavior changes. An agent skill from NVIDIA/NemoClaw.

OfficialApache-2.0Auto-check passed

Install Nemoclaw Contributor Update Docs

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

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

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-contributor-update-docs --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-update-docs .claude/skills/nemoclaw-contributor-update-docs && 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-update-docs
GitHub stars
23k
Token cost
~934 tokens
SKILL.md length
443 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Update NemoClaw documentation for merged behavior changes. An agent skill from NVIDIA/NemoClaw.

  • Works in 6 steps: Read the commit and PR context. → Decide whether supported user-visible… → Verify the behavior in current source… → …
  • Post-merge catch-up
  • SKILL.md covers Establish the range, Load current authority, Find documentation impact and Update the owning content, plus 1 more section
  • Calls npm

What it does

Nemoclaw Contributor Update Docs is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Update NemoClaw documentation for merged behavior changes. Use for post-merge catch-up or a requested documentation drift audit.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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.

When your agent uses it

  • Post-merge catch-up
  • A requested documentation drift audit

Example prompts

  • “/nemoclaw-contributor-update-docs”

Workflow steps

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

  1. Read the commit and PR context.
  2. Decide whether supported user-visible behavior changed.
  3. Verify the behavior in current source and tests.
  4. Confirm accepted product scope for every support claim.
  5. Find the owning page by searching current terminology, commands, configuration keys, errors,
  6. Inspect every applicable guide variant before editing shared content.

What it can do on your machine

Read from SKILL.md and the folder at commit 5f0b6b6. 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

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

  • Network

    No URLs in SKILL.md. Its commands use npm, 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 Update Docs loads about 934 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 443 words of instructions outside code blocks.

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

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 5f0b6b6, republished under its Apache-2.0 licence (© NVIDIA). 443 words, ~934 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-contributor-update-docs/SKILL.md (or your agent's skills folder).
name
nemoclaw-contributor-update-docs
description
Update NemoClaw documentation for merged behavior changes. Use for post-merge catch-up or a requested documentation drift audit.
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->

Update Documentation from Changes

Update documentation from current behavior. Use checked-in source, tests, and accepted product scope as behavior authority.

Establish the range

For Docs / Author Post-Merge Catch-Up, inspect changes from the latest reachable semver tag through the exact pushed main commit. Do not advance either boundary while authoring. For a direct documentation task, use the commit range supplied by the user or current checkout context.

Release-entry completion belongs to nemoclaw-maintainer-evening, not this workflow.

For an existing managed draft, extend its staged changes after the workflow merges them with main. Preserve previous documentation changes unless current source and tests justify a revision or removal. The independent reviewer checks those revisions against the previous draft commit.

Load current authority

Follow Discover the Current Implementation.

Read the active documentation guidance, the shared Documentation Writing and Review contract, and the current documentation navigation. Read the repository documentation skip file when it exists. Apply its current exclusions and prohibited terms.

Do not duplicate writing rules, page ownership, route conventions, agent variants, changelog format, or validation commands in this skill. Derive them from the current documentation guidance, source tree, package scripts, and workflows.

Find documentation impact

For each candidate change:

  1. Read the commit and PR context.
  2. Decide whether supported user-visible behavior changed.
  3. Verify the behavior in current source and tests.
  4. Confirm accepted product scope for every support claim.
  5. Find the owning page by searching current terminology, commands, configuration keys, errors, navigation, and recent documentation history.
  6. Inspect every applicable guide variant before editing shared content.

Ignore test-only and internal refactors unless they expose a documentation defect. Apply the current skip-file reporting policy. Record other evidence-backed exclusions in task evidence.

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

Update the owning content

Read each complete source page before editing. Update the narrowest page that owns the behavior. Create or restructure pages only when the current documentation guidance requires it. Use nemoclaw-maintainer-refactor-docs for information-architecture work.

State the user outcome, prerequisites, risks, lifecycle effects, and acceptance criterion that the current behavior supports. Do not infer a command, default, path, or support claim from historical documentation or a commit message.

Validate and hand off

In Docs / Author Post-Merge Catch-Up, change only docs/**, fern/docs.yml, and fern/assets/**; the workflow independently reviews the patch. Required PR checks run npm run docs; do not perform GitHub writes from the authoring step.

For a direct documentation task, run the current documentation checks discovered from repository guidance and package scripts. Inspect generated variants and links affected by the change and follow the shared writing and review contract.

Summarize updated pages, new pages, skipped changes, product-scope exclusions, and validation evidence. Use nemoclaw-contributor-create-pr when the user asks to publish a direct documentation PR.

© 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

Just SKILL.md in .agents/skills/nemoclaw-contributor-update-docs of NVIDIA/NemoClaw.

Open the folder on GitHubat commit 5f0b6b6

Compare with similar skills

Nemoclaw Contributor Update Docs 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 Update Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Contributor Update Docs this skillNVIDIA/NemoClaw23k—~934Automated safety check: PassApache-2.0
Mergeremotion-dev/remotion63k—~508Automated safety check: PassCustom licence
Mergewithastro/astro63k—~153Automated safety check: PassCustom licence
Merge Contributor PRdyoshikawa/rulesync1.5k—~8.9kAutomated safety check: WarnMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Merge Upsymfony/symfony31k—~4kAutomated safety check: PassMIT

Similar skills

  • Merge

    remotion-dev/remotion

    Official

    Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR.

    63k GitHub stars~508 tokensUpdated today
    DevelopmentAuto-check passed

  • Merge

    withastro/astro

    Official

    Handle main-to-next merge tasks including conflict resolution, changeset cleanup, and CI fix-ups.

    63k GitHub stars~153 tokensUpdated today
    Auto-check passed

  • Merge Contributor PR

    dyoshikawa/rulesync

    Take a contributor's pull request that cannot be merged as-is — usually a conflict with main — resolve the blocker without rewriting their commits, and merge it with a merge commit so their…

    1.5k GitHub stars~8.9k tokensUpdated today
    DevelopmentAuto-check: warnings

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Merge Up

    symfony/symfony

    Cascade-merge maintained Symfony branches from oldest to newest (e.g.

    31k GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed

  • Merge

    alirezarezvani/claude-skills

    Merge the winning agent's branch into base, archive losers, and clean up worktrees.

    28k GitHub stars~587 tokensUpdated 1 mo ago
    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 Update Docs

What does Nemoclaw Contributor Update Docs do?

Update NemoClaw documentation for merged behavior changes. An agent skill from NVIDIA/NemoClaw. Nemoclaw Contributor Update Docs is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Update NemoClaw documentation for merged behavior changes.

When should I use Nemoclaw Contributor Update Docs?

Nemoclaw Contributor Update Docs fits situations like: post-merge catch-up; A requested documentation drift audit.

How do I install Nemoclaw Contributor Update Docs in Claude Code?

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

How do I install Nemoclaw Contributor Update Docs in Codex?

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

Can I use Nemoclaw Contributor Update Docs 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-update-docs -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-update-docs, .gemini/skills/nemoclaw-contributor-update-docs, .github/skills/nemoclaw-contributor-update-docs and .opencode/skills/nemoclaw-contributor-update-docs in your project.

What does Nemoclaw Contributor Update Docs need to run?

Going by SKILL.md and its folder, Nemoclaw Contributor Update Docs needs the command-line tools its instructions call (npm).

Does Nemoclaw Contributor Update Docs access the network?

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

Is Nemoclaw Contributor Update Docs 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 Update Docs use?

Nemoclaw Contributor Update Docs 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 Update Docs use?

About 934 tokens (SKILL.md is roughly 3.7k 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 Update Docs?

Skills that share tags, products or a category with Nemoclaw Contributor Update Docs: Merge (remotion-dev/remotion, 63k stars), Merge (withastro/astro, 63k stars), Merge Contributor PR (dyoshikawa/rulesync, 1.5k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Contributor Update Docs?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NemoClaw, which has 22,686 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 9, 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.