Official agent skill

Nemoclaw Maintainer Refactor Docs

by NVIDIA in NVIDIA/NemoClaw

Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes.

OfficialApache-2.0Auto-check passedDevelopment

Install Nemoclaw Maintainer Refactor Docs

skills CLI
$ npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-refactor-docs -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-maintainer-refactor-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-maintainer-refactor-docs .claude/skills/nemoclaw-maintainer-refactor-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-maintainer-refactor-docs
GitHub stars
23k
Token cost
~1.1k tokens
SKILL.md length
533 words
Files
5 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes.

  • Structural documentation refactors
  • SKILL.md covers Prerequisites, Choose the Deliverable, Load the phase that applies and Completion Contract, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Refactoring

What it does

Nemoclaw Maintainer Refactor Docs is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Use for structural documentation refactors.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/migration.md` and `references/structure.md`).

It sits in Development, covering Refactoring. 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

  • Structural documentation refactors
  • Tasks that involve Refactoring

Example prompts

  • “/nemoclaw-maintainer-refactor-docs”

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 Maintainer Refactor Docs loads about 1.1k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 533 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~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 bced57c, republished under its Apache-2.0 licence (© NVIDIA). 533 words, ~1,096 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-maintainer-refactor-docs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
nemoclaw-maintainer-refactor-docs
description
Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Use for structural documentation refactors.
<!--
  SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
  SPDX-License-Identifier: Apache-2.0
-->

Refactor NemoClaw Documentation

Refactor a bounded documentation section without changing product meaning. Improve findability while preserving every useful fact, one canonical owner per topic, and every supported published route.

Prerequisites

  • Work from the NemoClaw repository root.
  • Follow the shared Documentation Writing and Review contract before planning or editing.
  • Read the full target pages, their navigation entries in docs/index.yml, their redirects in fern/docs.yml, and their inbound links before editing.

Choose the Deliverable

  • Treat cross-section ownership, navigation hierarchy, and published URL changes as maintainer-owned decisions.
  • For a request to plan, audit, or propose a structure, stop after the information architecture, ownership map, and URL migration plan.
  • For a request to refactor, implement the plan, validate it, and report the completed migration.
  • Keep the work bounded to the named docs section. Report adjacent debt instead of folding unrelated cleanup into the refactor.
  • Allow a cross-section move when canonical ownership requires it, but identify the move explicitly in the plan and migration report.
  • Surface a choice only when it changes topic ownership, public URLs, supported variants, or user workflow. Use established repository conventions for routine details.

Load the phase that applies

  • For an audit or structure plan, use Structure and Ownership.
  • Before changing published routes or moving content, use Migration. A plan that changes URLs must include its route and anchor mapping.
  • For an implemented refactor, use Validation and Review. Repair findings and rerun affected checks before reporting completion.

Do not load execution-only detail for a plan-only request. A request to perform the refactor includes implementation and validation; it does not require a separate approval of routine layout choices within the accepted scope.

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

Completion Contract

For a plan-only request, completion means the ownership map, proposed structure, route migration plan, and unresolved decisions are recorded. The implementation checks and validation results below apply only when the refactor was performed.

For an implemented refactor, require all of these conditions:

  • Every visible TOC item that readers can select is a real topic page.
  • Every foldable grouping node is non-clickable and has no page content.
  • Each page owns one primary topic or task.
  • Every old section is mapped to a destination or intentionally removed with a stated reason.
  • Troubleshooting and reference guidance has one canonical owner.
  • No supported variant renders a link or redirect to an unpublished page.
  • Legacy URLs redirect directly to final published pages.
  • Shared content renders correctly for every applicable agent variant.
  • Source and generated variant pages have no unresolved oversized or multi-purpose prose blocks.
  • Simple lists remain compact.
  • The docs build, route checks, link checks, and diff check pass.

Report the Result

For a plan-only request, report the proposed structure, ownership, routes, and remaining decisions. For an implemented refactor, summarize:

  • The final journey-based TOC.
  • Pages created, moved, consolidated, and deleted.
  • Canonical troubleshooting and reference ownership decisions.
  • Redirects and legacy routes preserved.
  • Variant-specific differences.
  • Readability edits made to dense paragraph blocks.
  • Validation commands and results.
  • Any intentionally deferred adjacent cleanup.

Use the Inference section as the living example of this method when a concrete pattern is needed. Its structure separates About Inference Routing, choosing a provider and model, hosted/local/custom setup paths, management, validation, and canonical Reference troubleshooting. Copy the reasoning and consistency rules, not the inference-specific page names.

© 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 4 other files (references) in .agents/skills/nemoclaw-maintainer-refactor-docs of NVIDIA/NemoClaw.

  • SKILL.md
  • agents/openai.yaml
  • references/migration.md
  • references/structure.md
  • references/validation.md

Open the folder on GitHubat commit bced57c

Compare with similar skills

Nemoclaw Maintainer Refactor 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 Maintainer Refactor Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Maintainer Refactor Docs this skillNVIDIA/NemoClaw23k—~1.1kAutomated safety check: PassApache-2.0
Guidelinesakash-network/node1.1k22 repos~577Automated safety check: PassMIT
Component Refactoringlangflow-ai/langflow156k—~3.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed
  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed

More from NVIDIA/NemoClaw

All 30 skills in this repo
  • Official

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

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

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

    23k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

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

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.

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

Categories

Questions about Nemoclaw Maintainer Refactor Docs

What does Nemoclaw Maintainer Refactor Docs do?

Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Nemoclaw Maintainer Refactor Docs is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes.

When should I use Nemoclaw Maintainer Refactor Docs?

Nemoclaw Maintainer Refactor Docs fits situations like: structural documentation refactors; tasks that involve Refactoring.

How do I install Nemoclaw Maintainer Refactor Docs in Claude Code?

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

How do I install Nemoclaw Maintainer Refactor Docs in Codex?

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

Can I use Nemoclaw Maintainer Refactor 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-maintainer-refactor-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-maintainer-refactor-docs, .gemini/skills/nemoclaw-maintainer-refactor-docs, .github/skills/nemoclaw-maintainer-refactor-docs and .opencode/skills/nemoclaw-maintainer-refactor-docs in your project.

What does Nemoclaw Maintainer Refactor Docs need to run?

SKILL.md names no scripts, command-line tools or credentials: Nemoclaw Maintainer Refactor Docs is instructions for the agent only.

Does Nemoclaw Maintainer Refactor Docs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nemoclaw Maintainer Refactor 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 Maintainer Refactor Docs use?

Nemoclaw Maintainer Refactor 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 Maintainer Refactor Docs use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Nemoclaw Maintainer Refactor Docs?

Skills that share tags, products or a category with Nemoclaw Maintainer Refactor Docs: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Maintainer Refactor Docs?

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