docs(skills): reorganize skills with audience-based prefixes#1603
Merged
docs(skills): reorganize skills with audience-based prefixes#1603
Conversation
Rename doc-generated skills from `nemoclaw-*` to `nemoclaw-user-*`, hand-written skills to `nemoclaw-maintainer-*` and `nemoclaw-contributor-*`. Add a `nemoclaw-skills-guide` index skill that introduces the three buckets and maps intents to skills. Merge CLAUDE.md content into AGENTS.md and symlink CLAUDE.md to AGENTS.md so all agent runtimes read a single source of truth. Update references in CONTRIBUTING.md, docs/CONTRIBUTING.md, PR template, and docs-to-skills.py. Made-with: Cursor
Contributor
📝 WalkthroughWalkthroughThis PR reorganizes NemoClaw agent skills with audience-specific naming prefixes ( Changes
Sequence Diagram(s)sequenceDiagram
actor User
participant NemoClaw CLI
participant OpenShell
participant Sandbox
participant InferenceGateway
User->>NemoClaw CLI: nemoclaw onboard
NemoClaw CLI->>OpenShell: provision sandbox & blueprint
OpenShell->>Sandbox: create container, apply policy
NemoClaw CLI->>InferenceGateway: configure routing
User->>Sandbox: openclaw agent ...
Sandbox->>InferenceGateway: inference.local request
InferenceGateway->>InferenceGateway: forward to host provider
InferenceGateway-->>Sandbox: routed inference response
sequenceDiagram
participant Sandbox
participant OpenShell TUI
participant Operator
participant NetworkPolicy
Sandbox->>OpenShell TUI: blocked egress request
OpenShell TUI->>Operator: display request (host:port, binary, method/path)
Operator->>OpenShell TUI: approve or deny
OpenShell TUI->>NetworkPolicy: update session policy
NetworkPolicy-->>Sandbox: allow/deny for current session
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes The diff introduces extensive documentation changes across many files with consistent patterns (new skill docs, reference pages, and naming updates), but heterogeneous content requires verification that all cross-references are correctly updated and that new documentation is accurate and complete. Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 19
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
.agents/skills/nemoclaw-user-configure-security/references/best-practices.md (1)
1-2:⚠️ Potential issue | 🔴 CriticalMissing SPDX license header.
This Markdown file must include an SPDX license header at the beginning.
📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> +<!-- SPDX-License-Identifier: Apache-2.0 --> + # Security Best Practices🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/skills/nemoclaw-user-configure-security/references/best-practices.md around lines 1 - 2, Add an SPDX license header as the very first line of the Markdown file .agents/skills/nemoclaw-user-configure-security/references/best-practices.md; insert a single-line SPDX identifier like "SPDX-License-Identifier: Apache-2.0" (or the project's required license identifier) on top of the file before "# Security Best Practices" so the file begins with the proper machine-readable license header.scripts/docs-to-skills.py (1)
14-48:⚠️ Potential issue | 🔴 CriticalUpdate pre-commit hook prefix to match script documentation.
The script documentation and examples use
--prefix nemoclaw-user, but.pre-commit-config.yamlline 76 still uses--prefix nemoclaw:entry: bash -c 'python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw && git add .agents/skills/'This mismatch will cause manual runs to generate
nemoclaw-user-*skills while the pre-commit hook generatesnemoclaw-*skills, leading to naming inconsistencies.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@scripts/docs-to-skills.py` around lines 14 - 48, Update the pre-commit hook to use the same prefix as the script docs by changing the hook entry that runs docs-to-skills.py to pass --prefix nemoclaw-user instead of --prefix nemoclaw; locate the hook entry string (the bash -c 'python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix ... && git add .agents/skills/' line in .pre-commit-config.yaml) and replace the prefix token so pre-commit generates nemoclaw-user-* skills matching the examples.docs/CONTRIBUTING.md (1)
1-3:⚠️ Potential issue | 🟠 MajorMissing required SPDX header in this Markdown file.
Please add the project-required SPDX header (HTML comment form) near the top of the file.
As per coding guidelines, every
**/*.{... ,md}source file must includeSPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.andSPDX-License-Identifier: Apache-2.0.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/CONTRIBUTING.md` around lines 1 - 3, Add the required SPDX header as an HTML comment near the top of the CONTRIBUTING.md file: insert the two lines "SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved." and "SPDX-License-Identifier: Apache-2.0" inside an HTML comment (<!-- ... -->) immediately after the existing top-level title or first line so tools can detect the license metadata in this Markdown source.
🧹 Nitpick comments (4)
docs/CONTRIBUTING.md (1)
33-33: Use present tense instead of future tense.Line 33 says “will be overwritten”; prefer present tense (for example, “are overwritten”).
As per coding guidelines, documentation should use present tense and avoid future tense descriptions of current behavior.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/CONTRIBUTING.md` at line 33, Update the sentence that currently reads "will be overwritten" to use present tense; locate the line containing the path pattern `.agents/skills/nemoclaw-user-*/` and replace "will be overwritten on the next run" with "are overwritten on the next run" (or similar present-tense phrasing) so the documentation uses present tense consistently..agents/skills/nemoclaw-user-get-started/SKILL.md (1)
79-80: Avoid documenting execution from a mutable branch URL.Using
refs/heads/mainforcurl | bashmeans script content can change without version pinning. Prefer a tagged release or commit-pinned URL in docs.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/skills/nemoclaw-user-get-started/SKILL.md around lines 79 - 80, The documentation currently shows executing the uninstall script from a mutable branch URL ("curl -fsSL https://raw.githubusercontent.com/NVIDIA/NemoClaw/refs/heads/main/uninstall.sh | bash"); update SKILL.md to pin the script source to a stable tag or specific commit (replace refs/heads/main with a release tag or commit SHA) and update the example text to recommend verifying the script before piping to bash (or provide a checksum), so the command references a fixed URL and safer usage guidance..agents/skills/nemoclaw-user-monitor-sandbox/SKILL.md (1)
71-73: Use the same sandbox placeholder format in examples.Line 71 hardcodes
my-assistantwhile the rest of the page uses<name>. Keep this consistent to reduce copy/paste errors for new users.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/skills/nemoclaw-user-monitor-sandbox/SKILL.md around lines 71 - 73, The example snippet hardcodes "my-assistant" instead of using the sandbox placeholder format used elsewhere; update the command in SKILL.md so it reads "$ nemoclaw <name> connect" (replace the literal my-assistant) to match the placeholder convention already used in other examples (also verify any adjacent examples like "openclaw agent --agent main --local -m \"Test inference\" --session-id debug" use the same <name> placeholder where applicable)..agents/skills/nemoclaw-user-overview/SKILL.md (1)
3-3: Front-matter description looks truncated.The description ends with
releas..., which reads like an accidental truncation and weakens skill routing quality.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/skills/nemoclaw-user-overview/SKILL.md at line 3, The front-matter "description" field in SKILL.md is truncated ("releas..."); open .agents/skills/nemoclaw-user-overview/SKILL.md and replace the YAML description value with a complete, self-contained sentence that summarizes the skill (mentioning NemoClaw vs OpenShell/OpenClaw, internal mechanics, lifecycle/onboarding scope, and changelog usage) so routing isn't harmed; ensure the description is a single-line string (or properly quoted multi-line YAML) without ellipsis and preserves existing keywords used by the skill router.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.agents/skills/nemoclaw-contributor-update-docs/SKILL.md:
- Around line 1-4: The file SKILL.md is missing the required SPDX license header
before the YAML frontmatter; add the exact two-line SPDX header comment (the
CopyrightText line and the SPDX-License-Identifier line) immediately above the
existing frontmatter at the top of the file so the header appears before the
leading `---` that begins the `name: nemoclaw-contributor-update-docs`
frontmatter.
In @.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md:
- Around line 1-5: Add an SPDX license header as the very first line of
.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md (i.e., place
"SPDX-License-Identifier: <LICENSE>" before the leading '---' frontmatter);
ensure the header appears above the existing frontmatter that contains name:
nemoclaw-maintainer-find-review-pr so tools recognize the license.
In @.agents/skills/nemoclaw-skills-guide/SKILL.md:
- Around line 1-4: The file SKILL.md is missing an SPDX license header before
the YAML frontmatter; add a single-line SPDX header (e.g.,
"SPDX-License-Identifier: Apache-2.0" or the project's chosen identifier)
immediately at the top of the file before the leading '---' so the header
precedes the frontmatter; ensure the header exact text matches the project's
SPDX identifier and commit the updated SKILL.md.
In @.agents/skills/nemoclaw-user-configure-inference/SKILL.md:
- Around line 1-5: Add the required SPDX license header as HTML comments at the
top of this Markdown skill file (SKILL.md) so it complies with repo policy:
insert an SPDX header like <!-- SPDX-FileCopyrightText: <copyright holder> -->
and <!-- SPDX-License-Identifier: <license> --> above the existing front-matter;
ensure the header appears before the YAML front-matter and references the
correct license identifier for this repository and the correct copyright holder
for "nemoclaw-user-configure-inference".
In @.agents/skills/nemoclaw-user-configure-security/SKILL.md:
- Around line 1-4: The SKILL.md file is missing an SPDX license header before
the YAML frontmatter; add a single-line SPDX license header comment (e.g.
SPDX-License-Identifier: <LICENSE>) immediately above the opening frontmatter
delimiter '---' so the file begins with the SPDX header followed by the existing
frontmatter; update the header to the correct license identifier for this
repository and commit the change.
In @.agents/skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md:
- Around line 27-56: The docs' sandbox examples drop all capabilities but only
re-add NET_BIND_SERVICE, which breaks the entrypoint's privilege separation in
scripts/nemoclaw-start.sh (line ~42) that requires CHOWN, SETUID, SETGID,
FOWNER, and KILL; update both the CLI example and the Docker Compose snippet to
re-add these capabilities (CHOWN, SETUID, SETGID, FOWNER, KILL) alongside
NET_BIND_SERVICE so the container can perform the gosu/capsh operations
performed in scripts/nemoclaw-start.sh.
In @.agents/skills/nemoclaw-user-deploy-remote/SKILL.md:
- Around line 1-5: This Markdown file lacks the required SPDX HTML comment
header; insert an SPDX HTML comment block at the very top of the file (before
the YAML frontmatter) that includes the SPDX-License-Identifier and appropriate
copyright/attribution tag; update the SKILL.md for the skill named
"nemoclaw-user-deploy-remote" by adding that header so automated license checks
pass.
In @.agents/skills/nemoclaw-user-manage-policy/SKILL.md:
- Around line 1-5: Add the required SPDX license header as an HTML comment at
the top of SKILL.md: open .agents/skills/nemoclaw-user-manage-policy/SKILL.md
and insert the appropriate SPDX identifier comment (e.g., <!--
SPDX-License-Identifier: <license> -->) as the very first line, ensuring there
is only one SPDX header and it follows the project's license choice; save the
file so the Markdown now begins with that HTML comment header.
In @.agents/skills/nemoclaw-user-overview/references/how-it-works.md:
- Around line 1-3: Add the required Markdown SPDX header as an HTML comment at
the very top of the document (before the "# How NemoClaw Works" title) so the
file .agents/skills/nemoclaw-user-overview/references/how-it-works.md includes
an SPDX license identifier; for example add a first line like <!--
SPDX-License-Identifier: Apache-2.0 --> (or the repository's canonical SPDX tag)
to satisfy the "Every source file must include an SPDX license header"
guideline.
In @.agents/skills/nemoclaw-user-overview/references/overview.md:
- Around line 3-8: Replace the adjectival phrase "open source" with the
hyphenated form "open‑source" in the two occurrences identified: the sentence
starting "NVIDIA NemoClaw is an open source reference stack" and the sentence
beginning "NemoClaw pairs open source and hosted models"; update both to
"open-source" to make the compound modifier consistent and stylistically
correct.
In @.agents/skills/nemoclaw-user-overview/SKILL.md:
- Around line 1-5: Add an HTML-format SPDX license header to the top of SKILL.md
(before the YAML frontmatter '---') using the repository's license identifier,
e.g. <!-- SPDX-License-Identifier: <CORRECT-LICENSE> -->; ensure the SPDX
comment sits on its own line above the existing frontmatter and update the
identifier to match the project license.
- Around line 33-35: The Mermaid node labels NC, OS, and OC currently include
emoji (e.g., "🦞 NVIDIA NemoClaw<br/>CLI, plugin, blueprint"); update those
labels to plain text by removing all emoji characters and leaving the
descriptive text only (e.g., "NVIDIA NemoClaw<br/>CLI, plugin, blueprint");
ensure you modify the NC, OS, and OC label strings in SKILL.md so the diagram
preserves the same wording and HTML breaks but contains no emoji.
In @.agents/skills/nemoclaw-user-reference/references/network-policies.md:
- Around line 44-53: The policy table is inconsistent with the baseline YAML:
update the entries so the `github` policy reflects both `github.com:443` and
`api.github.com:443` (remove the separate `github_rest_api` row and merge its
method list into `github`), and change the `telegram` policy's allowed binary
from "Any binary" to `/usr/local/bin/node` to match
nemoclaw-blueprint/policies/openclaw-sandbox.yaml; apply the same corrections to
the duplicate table section later in the file (the second occurrence around the
other referenced lines).
In @.agents/skills/nemoclaw-user-reference/references/troubleshooting.md:
- Line 5: The "Get Help" line in troubleshooting.md currently links to a
third-party Discord invite; remove the Discord invite URL (the text starting
with "NemoClaw Discord channel") and replace it with an official project-owned
support reference (e.g., a project support page, mailing list, or just the
existing "file an issue on GitHub" link) so the "**Get Help:**" paragraph only
points to official channels; update the sentence text under the "**Get Help:**"
heading accordingly and ensure formatting remains consistent in
references/troubleshooting.md.
- Around line 1-3: Add the required SPDX license header as an HTML comment at
the very top of the Markdown file (before the existing "# Troubleshooting"
heading); include an SPDX-License-Identifier entry and the appropriate
copyright/licensor info inside the <!-- ... --> comment so the file complies
with the project's mandatory SPDX header convention.
In @.agents/skills/nemoclaw-user-reference/SKILL.md:
- Around line 1-4: Add an SPDX license header line at the very top of the
SKILL.md file before the YAML frontmatter (the leading --- block) so the file
includes license metadata; insert a single SPDX identifier line (e.g.,
"SPDX-License-Identifier: MIT" or the project's chosen identifier) as the first
non-empty line above the existing frontmatter to satisfy license scan
requirements.
In @.agents/skills/nemoclaw-user-workspace/SKILL.md:
- Line 3: Update the description string in SKILL.md to use the correct uppercase
workspace filenames (SOUL.md, IDENTITY.md, MEMORY.md, AGENTS.md) instead of the
lowercase variants (soul.md, identity.md, memory.md, agents.md) so it matches
the actual paths on case-sensitive systems; edit the description text shown in
the diff to replace each lowercase filename with its uppercase counterpart while
preserving the rest of the sentence.
In `@AGENTS.md`:
- Around line 1-3: Add the required SPDX license header as an HTML comment at
the top of AGENTS.md (e.g., <!-- SPDX-License-Identifier: ... --> and optionally
<!-- SPDX-FileCopyrightText: ... -->) so the file includes the mandatory SPDX
header in Markdown comment form; insert these comments as the first lines before
the "# Agent Instructions" heading.
In `@docs/CONTRIBUTING.md`:
- Around line 57-59: Replace the two CLI code blocks that currently use
```bash``` and raw commands with ```console``` fences and a leading "$ " prompt;
specifically update the occurrences containing the command "python
scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user" (and its
--dry-run variant) so each block starts with ```console and the first line
inside is "$ python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix
nemoclaw-user" (or "$ python ... --dry-run" for the second block) to conform to
the CLI formatting guideline.
---
Outside diff comments:
In
@.agents/skills/nemoclaw-user-configure-security/references/best-practices.md:
- Around line 1-2: Add an SPDX license header as the very first line of the
Markdown file
.agents/skills/nemoclaw-user-configure-security/references/best-practices.md;
insert a single-line SPDX identifier like "SPDX-License-Identifier: Apache-2.0"
(or the project's required license identifier) on top of the file before "#
Security Best Practices" so the file begins with the proper machine-readable
license header.
In `@docs/CONTRIBUTING.md`:
- Around line 1-3: Add the required SPDX header as an HTML comment near the top
of the CONTRIBUTING.md file: insert the two lines "SPDX-FileCopyrightText:
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved." and
"SPDX-License-Identifier: Apache-2.0" inside an HTML comment (<!-- ... -->)
immediately after the existing top-level title or first line so tools can detect
the license metadata in this Markdown source.
In `@scripts/docs-to-skills.py`:
- Around line 14-48: Update the pre-commit hook to use the same prefix as the
script docs by changing the hook entry that runs docs-to-skills.py to pass
--prefix nemoclaw-user instead of --prefix nemoclaw; locate the hook entry
string (the bash -c 'python3 scripts/docs-to-skills.py docs/ .agents/skills/
--prefix ... && git add .agents/skills/' line in .pre-commit-config.yaml) and
replace the prefix token so pre-commit generates nemoclaw-user-* skills matching
the examples.
---
Nitpick comments:
In @.agents/skills/nemoclaw-user-get-started/SKILL.md:
- Around line 79-80: The documentation currently shows executing the uninstall
script from a mutable branch URL ("curl -fsSL
https://raw.githubusercontent.com/NVIDIA/NemoClaw/refs/heads/main/uninstall.sh |
bash"); update SKILL.md to pin the script source to a stable tag or specific
commit (replace refs/heads/main with a release tag or commit SHA) and update the
example text to recommend verifying the script before piping to bash (or provide
a checksum), so the command references a fixed URL and safer usage guidance.
In @.agents/skills/nemoclaw-user-monitor-sandbox/SKILL.md:
- Around line 71-73: The example snippet hardcodes "my-assistant" instead of
using the sandbox placeholder format used elsewhere; update the command in
SKILL.md so it reads "$ nemoclaw <name> connect" (replace the literal
my-assistant) to match the placeholder convention already used in other examples
(also verify any adjacent examples like "openclaw agent --agent main --local -m
\"Test inference\" --session-id debug" use the same <name> placeholder where
applicable).
In @.agents/skills/nemoclaw-user-overview/SKILL.md:
- Line 3: The front-matter "description" field in SKILL.md is truncated
("releas..."); open .agents/skills/nemoclaw-user-overview/SKILL.md and replace
the YAML description value with a complete, self-contained sentence that
summarizes the skill (mentioning NemoClaw vs OpenShell/OpenClaw, internal
mechanics, lifecycle/onboarding scope, and changelog usage) so routing isn't
harmed; ensure the description is a single-line string (or properly quoted
multi-line YAML) without ellipsis and preserves existing keywords used by the
skill router.
In `@docs/CONTRIBUTING.md`:
- Line 33: Update the sentence that currently reads "will be overwritten" to use
present tense; locate the line containing the path pattern
`.agents/skills/nemoclaw-user-*/` and replace "will be overwritten on the next
run" with "are overwritten on the next run" (or similar present-tense phrasing)
so the documentation uses present tense consistently.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 6a92ed38-b238-4d68-9aaa-9e6f955276a2
📒 Files selected for processing (35)
.agents/skills/nemoclaw-contributor-update-docs/SKILL.md.agents/skills/nemoclaw-maintainer-cut-release-tag/SKILL.md.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md.agents/skills/nemoclaw-maintainer-security-code-review/SKILL.md.agents/skills/nemoclaw-reference/references/inference-profiles.md.agents/skills/nemoclaw-skills-guide/SKILL.md.agents/skills/nemoclaw-user-configure-inference/SKILL.md.agents/skills/nemoclaw-user-configure-inference/references/inference-options.md.agents/skills/nemoclaw-user-configure-security/SKILL.md.agents/skills/nemoclaw-user-configure-security/references/best-practices.md.agents/skills/nemoclaw-user-configure-security/references/credential-storage.md.agents/skills/nemoclaw-user-deploy-remote/SKILL.md.agents/skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md.agents/skills/nemoclaw-user-get-started/SKILL.md.agents/skills/nemoclaw-user-manage-policy/SKILL.md.agents/skills/nemoclaw-user-monitor-sandbox/SKILL.md.agents/skills/nemoclaw-user-overview/SKILL.md.agents/skills/nemoclaw-user-overview/references/ecosystem.md.agents/skills/nemoclaw-user-overview/references/how-it-works.md.agents/skills/nemoclaw-user-overview/references/overview.md.agents/skills/nemoclaw-user-overview/references/release-notes.md.agents/skills/nemoclaw-user-reference/SKILL.md.agents/skills/nemoclaw-user-reference/references/architecture.md.agents/skills/nemoclaw-user-reference/references/commands.md.agents/skills/nemoclaw-user-reference/references/network-policies.md.agents/skills/nemoclaw-user-reference/references/troubleshooting.md.agents/skills/nemoclaw-user-workspace/SKILL.md.agents/skills/nemoclaw-user-workspace/references/workspace-files.md.github/PULL_REQUEST_TEMPLATE.mdAGENTS.mdCLAUDE.mdCLAUDE.mdCONTRIBUTING.mddocs/CONTRIBUTING.mdscripts/docs-to-skills.py
💤 Files with no reviewable changes (1)
- .agents/skills/nemoclaw-reference/references/inference-profiles.md
Comment on lines
1
to
4
| --- | ||
| name: update-docs | ||
| name: nemoclaw-contributor-update-docs | ||
| description: Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift. | ||
| --- |
Contributor
There was a problem hiding this comment.
Missing SPDX license header.
This Markdown file must include an SPDX license header before the frontmatter. As per coding guidelines, all .md files require:
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: nemoclaw-contributor-update-docs
description: Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-contributor-update-docs/SKILL.md around lines 1 - 4,
The file SKILL.md is missing the required SPDX license header before the YAML
frontmatter; add the exact two-line SPDX header comment (the CopyrightText line
and the SPDX-License-Identifier line) immediately above the existing frontmatter
at the top of the file so the header appears before the leading `---` that
begins the `name: nemoclaw-contributor-update-docs` frontmatter.
Comment on lines
1
to
5
| --- | ||
| name: find-review-pr | ||
| name: nemoclaw-maintainer-find-review-pr | ||
| description: Finds open GitHub PRs with security and priority-high labels, links each to its issue, detects duplicates (multiple PRs fixing the same issue), and presents a table of review candidates. Use when looking for the next PR to review. Trigger keywords - find pr, find review, next pr, pr to review, duplicate pr, security pr. | ||
| user_invocable: true | ||
| --- |
Contributor
There was a problem hiding this comment.
Missing SPDX license header.
This Markdown file must include an SPDX license header before the frontmatter.
📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: nemoclaw-maintainer-find-review-pr
description: Finds open GitHub PRs with security and priority-high labels, links each to its issue, detects duplicates (multiple PRs fixing the same issue), and presents a table of review candidates. Use when looking for the next PR to review. Trigger keywords - find pr, find review, next pr, pr to review, duplicate pr, security pr.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md around lines 1 -
5, Add an SPDX license header as the very first line of
.agents/skills/nemoclaw-maintainer-find-review-pr/SKILL.md (i.e., place
"SPDX-License-Identifier: <LICENSE>" before the leading '---' frontmatter);
ensure the header appears above the existing frontmatter that contains name:
nemoclaw-maintainer-find-review-pr so tools recognize the license.
Comment on lines
+1
to
+4
| --- | ||
| name: "nemoclaw-skills-guide" | ||
| description: "Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here." | ||
| --- |
Contributor
There was a problem hiding this comment.
Missing SPDX license header.
This new Markdown file must include an SPDX license header before the frontmatter.
📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: "nemoclaw-skills-guide"
description: "Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| --- | |
| name: "nemoclaw-skills-guide" | |
| description: "Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here." | |
| --- | |
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| --- | |
| name: "nemoclaw-skills-guide" | |
| description: "Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here." | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-skills-guide/SKILL.md around lines 1 - 4, The file
SKILL.md is missing an SPDX license header before the YAML frontmatter; add a
single-line SPDX header (e.g., "SPDX-License-Identifier: Apache-2.0" or the
project's chosen identifier) immediately at the top of the file before the
leading '---' so the header precedes the frontmatter; ensure the header exact
text matches the project's SPDX identifier and commit the updated SKILL.md.
Comment on lines
+1
to
+5
| --- | ||
| name: "nemoclaw-user-configure-inference" | ||
| description: "Lists all inference providers offered during NemoClaw onboarding. Use when explaining which providers are available, what the onboard wizard presents, or how inference routing works. Changes the active inference model without restarting the sandbox. Use when switching inference providers, changing the model runtime, or reconfiguring inference routing. Connects NemoClaw to a local inference server. Use when setting up Ollama, vLLM, TensorRT-LLM, NIM, or any OpenAI-compatible local model server with NemoClaw." | ||
| --- | ||
|
|
Contributor
There was a problem hiding this comment.
SPDX header is required but missing.
Add the Markdown SPDX HTML comments to satisfy repo licensing policy.
As per coding guidelines: “Every source file must include an SPDX license header … (HTML comments for Markdown).”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-user-configure-inference/SKILL.md around lines 1 -
5, Add the required SPDX license header as HTML comments at the top of this
Markdown skill file (SKILL.md) so it complies with repo policy: insert an SPDX
header like <!-- SPDX-FileCopyrightText: <copyright holder> --> and <!--
SPDX-License-Identifier: <license> --> above the existing front-matter; ensure
the header appears before the YAML front-matter and references the correct
license identifier for this repository and the correct copyright holder for
"nemoclaw-user-configure-inference".
Comment on lines
1
to
4
| --- | ||
| name: "nemoclaw-security-best" | ||
| description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs." | ||
| name: "nemoclaw-user-configure-security" | ||
| description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs. Explains where NemoClaw stores provider credentials, the file permissions it applies, and the operational security trade-offs of plaintext local storage. Use when reviewing credential handling or advising users how to secure stored API keys." | ||
| --- |
Contributor
There was a problem hiding this comment.
Missing SPDX license header.
This Markdown file must include an SPDX license header before the frontmatter.
📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: "nemoclaw-user-configure-security"
description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs. Explains where NemoClaw stores provider credentials, the file permissions it applies, and the operational security trade-offs of plaintext local storage. Use when reviewing credential handling or advising users how to secure stored API keys."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| --- | |
| name: "nemoclaw-security-best" | |
| description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs." | |
| name: "nemoclaw-user-configure-security" | |
| description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs. Explains where NemoClaw stores provider credentials, the file permissions it applies, and the operational security trade-offs of plaintext local storage. Use when reviewing credential handling or advising users how to secure stored API keys." | |
| --- | |
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| --- | |
| name: "nemoclaw-user-configure-security" | |
| description: "Presents a risk framework for every configurable security control in NemoClaw. Use when evaluating security posture, reviewing sandbox security defaults, or assessing control trade-offs. Explains where NemoClaw stores provider credentials, the file permissions it applies, and the operational security trade-offs of plaintext local storage. Use when reviewing credential handling or advising users how to secure stored API keys." | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-user-configure-security/SKILL.md around lines 1 - 4,
The SKILL.md file is missing an SPDX license header before the YAML frontmatter;
add a single-line SPDX license header comment (e.g. SPDX-License-Identifier:
<LICENSE>) immediately above the opening frontmatter delimiter '---' so the file
begins with the SPDX header followed by the existing frontmatter; update the
header to the correct license identifier for this repository and commit the
change.
|
|
||
| This page covers common issues you may encounter when installing, onboarding, or running NemoClaw, along with their resolution steps. | ||
|
|
||
| > **Get Help:** If your issue is not listed here, join the [NemoClaw Discord channel](https://discord.gg/XFpfPv9Uvx) to ask questions and get help from the community. You can also [file an issue on GitHub](https://github.com/NVIDIA/NemoClaw/issues/new). |
Contributor
There was a problem hiding this comment.
Avoid linking to community resources in repo docs.
The Discord invite link is a community resource and should be removed or replaced with an official project-owned support channel reference.
Based on learnings: “Do not add links to third-party code repositories, community collections, or unofficial resources in documentation or code.”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-user-reference/references/troubleshooting.md at line
5, The "Get Help" line in troubleshooting.md currently links to a third-party
Discord invite; remove the Discord invite URL (the text starting with "NemoClaw
Discord channel") and replace it with an official project-owned support
reference (e.g., a project support page, mailing list, or just the existing
"file an issue on GitHub" link) so the "**Get Help:**" paragraph only points to
official channels; update the sentence text under the "**Get Help:**" heading
accordingly and ensure formatting remains consistent in
references/troubleshooting.md.
Comment on lines
+1
to
+4
| --- | ||
| name: "nemoclaw-user-reference" | ||
| description: "Describes how NemoClaw combines a CLI plugin with a versioned blueprint to move OpenClaw into a controlled sandbox. Use when looking up NemoClaw architecture, plugin structure, or blueprint design. Lists all slash commands and standalone NemoClaw CLI commands. Use when looking up a command, checking command syntax, or browsing the CLI reference. Documents baseline network policy, filesystem rules, and operator approval flow. Use when reviewing default network policies, understanding egress controls, or looking up the approval flow. Diagnoses and resolves common NemoClaw installation, onboarding, and runtime issues. Use when troubleshooting errors, debugging sandbox problems, or resolving setup failures." | ||
| --- |
Contributor
There was a problem hiding this comment.
Missing SPDX license header.
This new Markdown file must include an SPDX license header before the frontmatter.
📄 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: "nemoclaw-user-reference"
description: "Describes how NemoClaw combines a CLI plugin with a versioned blueprint to move OpenClaw into a controlled sandbox. Use when looking up NemoClaw architecture, plugin structure, or blueprint design. Lists all slash commands and standalone NemoClaw CLI commands. Use when looking up a command, checking command syntax, or browsing the CLI reference. Documents baseline network policy, filesystem rules, and operator approval flow. Use when reviewing default network policies, understanding egress controls, or looking up the approval flow. Diagnoses and resolves common NemoClaw installation, onboarding, and runtime issues. Use when troubleshooting errors, debugging sandbox problems, or resolving setup failures."📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| --- | |
| name: "nemoclaw-user-reference" | |
| description: "Describes how NemoClaw combines a CLI plugin with a versioned blueprint to move OpenClaw into a controlled sandbox. Use when looking up NemoClaw architecture, plugin structure, or blueprint design. Lists all slash commands and standalone NemoClaw CLI commands. Use when looking up a command, checking command syntax, or browsing the CLI reference. Documents baseline network policy, filesystem rules, and operator approval flow. Use when reviewing default network policies, understanding egress controls, or looking up the approval flow. Diagnoses and resolves common NemoClaw installation, onboarding, and runtime issues. Use when troubleshooting errors, debugging sandbox problems, or resolving setup failures." | |
| --- | |
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| --- | |
| name: "nemoclaw-user-reference" | |
| description: "Describes how NemoClaw combines a CLI plugin with a versioned blueprint to move OpenClaw into a controlled sandbox. Use when looking up NemoClaw architecture, plugin structure, or blueprint design. Lists all slash commands and standalone NemoClaw CLI commands. Use when looking up a command, checking command syntax, or browsing the CLI reference. Documents baseline network policy, filesystem rules, and operator approval flow. Use when reviewing default network policies, understanding egress controls, or looking up the approval flow. Diagnoses and resolves common NemoClaw installation, onboarding, and runtime issues. Use when troubleshooting errors, debugging sandbox problems, or resolving setup failures." | |
| --- |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-user-reference/SKILL.md around lines 1 - 4, Add an
SPDX license header line at the very top of the SKILL.md file before the YAML
frontmatter (the leading --- block) so the file includes license metadata;
insert a single SPDX identifier line (e.g., "SPDX-License-Identifier: MIT" or
the project's chosen identifier) as the first non-empty line above the existing
frontmatter to satisfy license scan requirements.
| @@ -0,0 +1,169 @@ | |||
| --- | |||
| name: "nemoclaw-user-workspace" | |||
| description: "Backs up and restores OpenClaw workspace files before destructive operations. Use when backing up a sandbox, restoring workspace state, or preparing for a destructive operation. Explains what workspace files are, where they live, and how they persist across sandbox restarts. Use when asking about soul.md, identity.md, memory.md, agents.md, or sandbox file persistence." | |||
Contributor
There was a problem hiding this comment.
Fix filename casing in description for consistency with actual paths.
Line 3 uses lowercase names (soul.md, identity.md, etc.), while the documented workspace files are uppercase (SOUL.md, IDENTITY.md, ...). This can confuse users on case-sensitive systems.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.agents/skills/nemoclaw-user-workspace/SKILL.md at line 3, Update the
description string in SKILL.md to use the correct uppercase workspace filenames
(SOUL.md, IDENTITY.md, MEMORY.md, AGENTS.md) instead of the lowercase variants
(soul.md, identity.md, memory.md, agents.md) so it matches the actual paths on
case-sensitive systems; edit the description text shown in the diff to replace
each lowercase filename with its uppercase counterpart while preserving the rest
of the sentence.
Comment on lines
+1
to
+3
| # Agent Instructions | ||
|
|
||
| ## Project Context | ||
| ## Project Overview |
Contributor
There was a problem hiding this comment.
AGENTS.md is missing the mandatory SPDX header.
Please add the required Markdown SPDX comments at the top of the file.
As per coding guidelines: “Every source file must include an SPDX license header … (HTML comments for Markdown).”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@AGENTS.md` around lines 1 - 3, Add the required SPDX license header as an
HTML comment at the top of AGENTS.md (e.g., <!-- SPDX-License-Identifier: ...
--> and optionally <!-- SPDX-FileCopyrightText: ... -->) so the file includes
the mandatory SPDX header in Markdown comment form; insert these comments as the
first lines before the "# Agent Instructions" heading.
Comment on lines
57
to
59
| ```bash | ||
| python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw | ||
| python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user | ||
| ``` |
Contributor
There was a problem hiding this comment.
Use console code fences with $ prompt for CLI examples.
These CLI snippets currently use bash; switch to console and prefix commands with $.
Suggested patch
-```bash
-python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user
+```console
+$ python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user-bash -python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --dry-run +console
+$ python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --dry-run
As per coding guidelines, CLI code blocks must use the console language tag with $ prompt prefix.
Also applies to: 65-67
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/CONTRIBUTING.md` around lines 57 - 59, Replace the two CLI code blocks
that currently use ```bash``` and raw commands with ```console``` fences and a
leading "$ " prompt; specifically update the occurrences containing the command
"python scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user"
(and its --dry-run variant) so each block starts with ```console and the first
line inside is "$ python scripts/docs-to-skills.py docs/ .agents/skills/
--prefix nemoclaw-user" (or "$ python ... --dry-run" for the second block) to
conform to the CLI formatting guideline.
cv
approved these changes
Apr 8, 2026
16 tasks
miyoungc
added a commit
that referenced
this pull request
Apr 8, 2026
<!-- markdownlint-disable MD041 --> ## Summary Remove the remaining old-name skills. Follow-up after #1603 ## Related Issue <!-- Link to the issue: Fixes #NNN or Closes #NNN. Remove this section if none. --> ## Changes <!-- Bullet list of key changes. --> ## Type of Change <!-- Check the one that applies. --> - [ ] Code change for a new feature, bug fix, or refactor. - [ ] Code change with doc updates. - [ ] Doc only. Prose changes without code sample modifications. - [ ] Doc only. Includes code sample changes. ## Testing <!-- What testing was done? --> - [x] `npx prek run --all-files` passes (or equivalently `make check`). - [ ] `npm test` passes. - [ ] `make docs` builds without warnings. (for doc-only changes) ## Checklist ### General - [x] I have read and followed the [contributing guide](https://github.com/NVIDIA/NemoClaw/blob/main/CONTRIBUTING.md). - [x] I have read and followed the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md). (for doc-only changes) ### Code Changes <!-- Skip if this is a doc-only PR. --> - [ ] Formatters applied — `npx prek run --all-files` auto-fixes formatting (or `make format` for targeted runs). - [ ] Tests added or updated for new or changed behavior. - [ ] No secrets, API keys, or credentials committed. - [ ] Doc pages updated for any user-facing behavior changes (new commands, changed defaults, new features, bug fixes that contradict existing docs). ### Doc Changes <!-- Skip if this PR has no doc changes. --> - [ ] Follows the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md). Try running the `nemoclaw-contributor-update-docs` agent skill to draft changes while complying with the style guide. For example, prompt your agent with "`/nemoclaw-contributor-update-docs` catch up the docs for the new changes I made in this PR." - [ ] New pages include SPDX license header and frontmatter, if creating a new page. - [ ] Cross-references and links verified. --- <!-- DCO sign-off (required by CI). Replace with your real name and email. --> Signed-off-by: Your Name <your-email@example.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Documentation - Removed documentation for multiple NemoClaw skills covering inference configuration, security, deployment, monitoring, policy management, workspace, and reference materials. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rename doc-generated skills from
nemoclaw-*tonemoclaw-user-*, hand-written skills tonemoclaw-maintainer-*andnemoclaw-contributor-*. Add anemoclaw-skills-guideindex skill that introduces the three buckets and maps intents to skills.Merge CLAUDE.md content into AGENTS.md and symlink CLAUDE.md to AGENTS.md so all agent runtimes read a single source of truth.
Update references in CONTRIBUTING.md, docs/CONTRIBUTING.md, PR template, and docs-to-skills.py.
Made-with: Cursor
Summary
Related Issue
Changes
Type of Change
Testing
npx prek run --all-filespasses (or equivalentlymake check).npm testpasses.make docsbuilds without warnings. (for doc-only changes)Checklist
General
Code Changes
npx prek run --all-filesauto-fixes formatting (ormake formatfor targeted runs).Doc Changes
update-docsagent skill to draft changes while complying with the style guide. For example, prompt your agent with "/update-docscatch up the docs for the new changes I made in this PR."Signed-off-by: Your Name your-email@example.com
Summary by CodeRabbit
Release Notes
Documentation
Refactor