chore: refresh and re-sign nemoclaw-user-reference skill#4782
Merged
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
📝 WalkthroughWalkthroughThe pull request refreshes the NemoClaw user-reference skill documentation and evaluation artifacts to generalize architectural descriptions from OpenClaw-specific to compatible multi-agent support. Documentation files are reformatted with bash-style command blocks, CLI guidance is expanded with workflow examples, and evaluation metadata is updated with new benchmark results and underlying evaluation signals. ChangesNemoClaw Skill Documentation and Evaluation Update
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Collaborator
Author
|
/nvskills-ci |
Contributor
PR Review AdvisorFindings: 0 needs attention, 2 worth checking, 1 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Consider writing more tests for
Since last review detailsCurrent findings:
This is an automated advisory review. A human maintainer must make the final merge decision. |
miyoungc
changed the title
miyoungc
changed the title
Contributor
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorFailed: Could not parse JSON from advisor output; see /home/runner/work/NemoClaw/NemoClaw/artifacts/e2e-advisor/e2e-advisor-raw-output.txt |
Contributor
E2E Scenario Advisor RecommendationRequired scenario E2E: None Full scenario advisor summaryE2E Scenario AdvisorFailed: Could not parse JSON from advisor output; see /home/runner/work/NemoClaw/NemoClaw/artifacts/e2e-advisor/e2e-scenario-advisor-raw-output.txt |
Collaborator
Author
|
/nvskills-ci |
Signed-off-by: nvskills-svc-account <svc-nvskills-signing@nvidia.com>
miyoungc
changed the title
prekshivyas
approved these changes
Jun 4, 2026
prekshivyas
left a comment
prekshivyas
left a comment
Contributor
There was a problem hiding this comment.
Approving. Clean follow-up to the reference-skill refresh:
- Scoped entirely to
skills/nemoclaw-user-reference/(10 files, nothing else touched). skill.oms.sigwas attached bysvc-nvskills-signing, not hand-edited, andNVSkills CIpassed — the authoritative validation for the re-signed package.- The refreshed references reflect current source (e.g.
commands.mdcarries thechannels add --forceflag now on main), so the package is in sync, not stale. check-hash,markdown-links,dco-check,commit-lint, and the PR review advisor are green.
Everything changed is markdown/JSON/signature, so the still-running checks job should pass trivially — flagging only that it hadn't finished at approval time.
![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: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (5)
skills/nemoclaw-user-reference/BENCHMARK.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing SPDX header in BENCHMARK.md.
Please add the required SPDX copyright/license header at the top.
As per coding guidelines, all
*.mdfiles must include SPDX headers using HTML comments.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/nemoclaw-user-reference/BENCHMARK.md` at line 1, Add the required SPDX header as an HTML comment at the very top of BENCHMARK.md (above the existing "# Evaluation Report" header): insert the SPDX license identifier and copyright/owner information per repo guidelines (e.g., an HTML comment like <!-- SPDX-License-Identifier: ... --> with the appropriate copyright line) so the file complies with the required SPDX header format.skills/nemoclaw-user-reference/references/architecture.md (1)
18-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove emoji from technical documentation content.
Line 18 (
👤) and lock emoji usages in diagram labels violate the “no emoji in technical prose” rule.As per coding guidelines, “No emoji in technical prose.”
Also applies to: 41-41, 92-92
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/nemoclaw-user-reference/references/architecture.md` at line 18, Replace emoji used in diagram node labels with plain text; specifically change USER(["👤 User"]):::user to USER(["User"]):::user and remove any other emoji instances (e.g., lock/🔒 icons) in similar node definitions so labels contain only technical prose while retaining the existing node identifiers and classes.skills/nemoclaw-user-reference/evals/evals.json (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd SPDX metadata to
skills/nemoclaw-user-reference/evals/evals.json(strict JSON)
evals.jsonis strict JSON and there’s no repo evidence of JSONC/strip-json-comments-style parsing, so adding// SPDX-*headers would break JSON consumers. Other JSON files in this repo embed SPDX via a top-level"$comment"field (e.g.,nemoclaw-blueprint/model-specific-setup/schema.json,schemas/router-pool-config.schema.json); use the same approach forskills/nemoclaw-user-reference/evals/evals.json.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/nemoclaw-user-reference/evals/evals.json` at line 1, Replace any SPDX-style // comments in skills/nemoclaw-user-reference/evals/evals.json with a top-level "$comment" string property containing the SPDX metadata (e.g., "$comment": "SPDX-License-Identifier: ..."), ensuring the file remains strict JSON; add the "$comment" field at the root of the JSON object/array wrapper and remove any // SPDX-* lines so JSON consumers can parse the file; locate the file by name (evals.json) and update the top-level data structure accordingly.skills/nemoclaw-user-reference/references/troubleshooting.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd SPDX header comments at the top of this document.
This Markdown file is missing the required SPDX copyright and license header.
As per coding guidelines, all
*.mdfiles must include the SPDX header pair, using HTML comments for Markdown.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/nemoclaw-user-reference/references/troubleshooting.md` at line 1, Add the required SPDX header comments at the very top of the Markdown file by inserting the SPDX copyright and license HTML comment pair above the existing "# Troubleshooting" heading; update the file "skills/nemoclaw-user-reference/references/troubleshooting.md" so it contains the SPDX header block (as HTML comments) with the appropriate copyright owner and license identifier immediately before the first line.skills/nemoclaw-user-reference/references/network-policies.md (1)
1-1:⚠️ Potential issue | 🟠 Major | ⚡ Quick winInsert the SPDX license header for this Markdown file.
The file is missing the required SPDX HTML-comment header block.
As per coding guidelines,
**/*.{js,ts,tsx,jsx,sh,md,mdx,json,yaml,yml,css,svg}files must include SPDX headers, and Markdown files must use HTML comments.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/nemoclaw-user-reference/references/network-policies.md` at line 1, Add the required SPDX HTML-comment header at the very top of this Markdown file (above the existing "# Network Policies" header) using the standard SPDX format for Markdown (an HTML comment block containing SPDX-License-Identifier and any copyright lines); ensure the comment is in HTML comment form (<!-- ... -->) and matches the project's SPDX header convention so the file "Network Policies" includes the proper SPDX metadata.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/nemoclaw-user-reference/references/architecture.md`:
- Line 1: Add the required SPDX header to the top of the Markdown file by
inserting two HTML comment lines: one containing SPDX-FileCopyrightText with the
appropriate year and copyright owner, and one containing SPDX-License-Identifier
with the correct license identifier; ensure these comments are the very first
lines in architecture.md so they satisfy the repository's SPDX header
requirement.
In `@skills/nemoclaw-user-reference/references/cli-selection-guide.md`:
- Line 1: Add the required SPDX header as an HTML comment at the top of the
Markdown file: insert an HTML comment block containing "SPDX-FileCopyrightText:
<copyright holder>" and "SPDX-License-Identifier: Apache-2.0" above the existing
title line; ensure the header uses the exact SPDX keys and appears before "#
Choose Between NemoClaw and OpenShell CLIs" so tools can detect it.
- Around line 101-102: The CLI examples for the sandbox exec command use the
short flag `-n` but the implemented argv contract expects `--name` for
`openshell sandbox exec`; update all examples (including the occurrences around
the second example) to use `--name <sandbox-name>` instead of `-n
<sandbox-name>` so copy/paste matches the `exec` argv contract.
In `@skills/nemoclaw-user-reference/skill-card.md`:
- Line 1: Add the required SPDX header as an HTML comment at the top of
skill-card.md: insert a one-line or two-line HTML comment containing the
copyright notice and SPDX-License-Identifier (e.g. <!-- Copyright (c) YEAR
OWNER. SPDX-License-Identifier: LICENSE -->) so the file complies with the
repository guideline that all *.md files include SPDX headers; update the header
in skill-card.md accordingly.
In `@skills/nemoclaw-user-reference/SKILL.md`:
- Line 1: Add the required SPDX header as HTML comments at the very top of
SKILL.md: insert an SPDX copyright line (SPDX-FileCopyrightText) and an SPDX
license identifier line (SPDX-License-Identifier) wrapped in <!-- --> so the
file begins with those two HTML comment lines; ensure the copyright holder/year
and the correct license identifier are filled in.
---
Outside diff comments:
In `@skills/nemoclaw-user-reference/BENCHMARK.md`:
- Line 1: Add the required SPDX header as an HTML comment at the very top of
BENCHMARK.md (above the existing "# Evaluation Report" header): insert the SPDX
license identifier and copyright/owner information per repo guidelines (e.g., an
HTML comment like <!-- SPDX-License-Identifier: ... --> with the appropriate
copyright line) so the file complies with the required SPDX header format.
In `@skills/nemoclaw-user-reference/evals/evals.json`:
- Line 1: Replace any SPDX-style // comments in
skills/nemoclaw-user-reference/evals/evals.json with a top-level "$comment"
string property containing the SPDX metadata (e.g., "$comment":
"SPDX-License-Identifier: ..."), ensuring the file remains strict JSON; add the
"$comment" field at the root of the JSON object/array wrapper and remove any //
SPDX-* lines so JSON consumers can parse the file; locate the file by name
(evals.json) and update the top-level data structure accordingly.
In `@skills/nemoclaw-user-reference/references/architecture.md`:
- Line 18: Replace emoji used in diagram node labels with plain text;
specifically change USER(["👤 User"]):::user to USER(["User"]):::user and remove
any other emoji instances (e.g., lock/🔒 icons) in similar node definitions so
labels contain only technical prose while retaining the existing node
identifiers and classes.
In `@skills/nemoclaw-user-reference/references/network-policies.md`:
- Line 1: Add the required SPDX HTML-comment header at the very top of this
Markdown file (above the existing "# Network Policies" header) using the
standard SPDX format for Markdown (an HTML comment block containing
SPDX-License-Identifier and any copyright lines); ensure the comment is in HTML
comment form (<!-- ... -->) and matches the project's SPDX header convention so
the file "Network Policies" includes the proper SPDX metadata.
In `@skills/nemoclaw-user-reference/references/troubleshooting.md`:
- Line 1: Add the required SPDX header comments at the very top of the Markdown
file by inserting the SPDX copyright and license HTML comment pair above the
existing "# Troubleshooting" heading; update the file
"skills/nemoclaw-user-reference/references/troubleshooting.md" so it contains
the SPDX header block (as HTML comments) with the appropriate copyright owner
and license identifier immediately before the first line.
🪄 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: Enterprise
Run ID: 80eeaa83-297a-40fc-9478-99d1ac571690
📒 Files selected for processing (10)
skills/nemoclaw-user-reference/BENCHMARK.mdskills/nemoclaw-user-reference/SKILL.mdskills/nemoclaw-user-reference/evals/evals.jsonskills/nemoclaw-user-reference/references/architecture.mdskills/nemoclaw-user-reference/references/cli-selection-guide.mdskills/nemoclaw-user-reference/references/commands.mdskills/nemoclaw-user-reference/references/network-policies.mdskills/nemoclaw-user-reference/references/troubleshooting.mdskills/nemoclaw-user-reference/skill-card.mdskills/nemoclaw-user-reference/skill.oms.sig
| @@ -1,12 +1,10 @@ | |||
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |||
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |||
| # Architecture Details | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header to this Markdown file.
This file is missing the mandated SPDX copyright/license header at the top.
As per coding guidelines, all *.md files must include SPDX headers using HTML comments.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemoclaw-user-reference/references/architecture.md` at line 1, Add the
required SPDX header to the top of the Markdown file by inserting two HTML
comment lines: one containing SPDX-FileCopyrightText with the appropriate year
and copyright owner, and one containing SPDX-License-Identifier with the correct
license identifier; ensure these comments are the very first lines in
architecture.md so they satisfy the repository's SPDX header requirement.
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | ||
| <!-- SPDX-License-Identifier: Apache-2.0 --> | ||
| # CLI Selection Guide | ||
| # Choose Between NemoClaw and OpenShell CLIs |
Contributor
There was a problem hiding this comment.
Add the required SPDX header at the top of this Markdown file.
This file is missing the mandated SPDX copyright/license header for Markdown files.
As per coding guidelines, **/*.{js,ts,tsx,jsx,sh,md,mdx,json,yaml,yml,css,svg} files must include SPDX headers (Markdown uses HTML comments): SPDX-FileCopyrightText ... and SPDX-License-Identifier: Apache-2.0.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemoclaw-user-reference/references/cli-selection-guide.md` at line 1,
Add the required SPDX header as an HTML comment at the top of the Markdown file:
insert an HTML comment block containing "SPDX-FileCopyrightText: <copyright
holder>" and "SPDX-License-Identifier: Apache-2.0" above the existing title
line; ensure the header uses the exact SPDX keys and appears before "# Choose
Between NemoClaw and OpenShell CLIs" so tools can detect it.
Comment on lines
+101
to
102
| openshell sandbox exec -n <sandbox-name> -- env | grep '^HOME=' | ||
| ``` |
Contributor
There was a problem hiding this comment.
Use --name in openshell sandbox exec examples to match the implemented contract.
These examples use -n, but the exec argv contract shown in src/lib/actions/sandbox/exec.ts:7-78 uses --name. Please align docs to avoid copy/paste failures.
Also applies to: 146-147
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemoclaw-user-reference/references/cli-selection-guide.md` around
lines 101 - 102, The CLI examples for the sandbox exec command use the short
flag `-n` but the implemented argv contract expects `--name` for `openshell
sandbox exec`; update all examples (including the occurrences around the second
example) to use `--name <sandbox-name>` instead of `-n <sandbox-name>` so
copy/paste matches the `exec` argv contract.
| @@ -1,5 +1,5 @@ | |||
| ## Description: <br> | |||
Contributor
There was a problem hiding this comment.
Add SPDX header to skill-card.md.
The required SPDX copyright/license header is missing.
As per coding guidelines, all *.md files must include SPDX headers using HTML comments.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemoclaw-user-reference/skill-card.md` at line 1, Add the required
SPDX header as an HTML comment at the top of skill-card.md: insert a one-line or
two-line HTML comment containing the copyright notice and
SPDX-License-Identifier (e.g. <!-- Copyright (c) YEAR OWNER.
SPDX-License-Identifier: LICENSE -->) so the file complies with the repository
guideline that all *.md files include SPDX headers; update the header in
skill-card.md accordingly.
| @@ -1,18 +1,15 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header at the top of this file.
SKILL.md is missing the required SPDX copyright/license header.
As per coding guidelines, all *.md files must include SPDX headers using HTML comments.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/nemoclaw-user-reference/SKILL.md` at line 1, Add the required SPDX
header as HTML comments at the very top of SKILL.md: insert an SPDX copyright
line (SPDX-FileCopyrightText) and an SPDX license identifier line
(SPDX-License-Identifier) wrapped in <!-- --> so the file begins with those two
HTML comment lines; ensure the copyright holder/year and the correct license
identifier are filled in.
cv
pushed a commit
that referenced
this pull request
Jun 5, 2026
## Summary
- Add the v0.0.59 release notes from the GitHub announcement discussion.
- Refresh local inference and credential-storage guidance for the
current release behavior.
- Regenerate the user skills from the updated Fern docs.
- Tighten release-prep and docs review guidance for generated skills, PR
labels, and shared `$$nemoclaw` command placeholders.
## Verification
- `python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix
nemoclaw-user --doc-platform fern-mdx`
- `rg "permissive mode|shields down|shields up|shields status|config
rotate-token|rotate-token" --glob '*.{md,mdx}'`
- `git diff --check`
- `npm run docs` (rerun outside sandbox after sandbox-only `tsx` IPC
permission failure)
- `npm run typecheck:cli`
- Pre-commit hooks during commit passed, including markdownlint,
docs-to-skills verification, gitleaks, commitlint, and skills YAML
tests.
## Source Summary
- #3679, #4437, #4681, #4766, #4772, #4775, #4786 ->
`docs/about/release-notes.mdx`, `docs/reference/commands.mdx`,
`docs/reference/troubleshooting.mdx`: Summarize OpenClaw 2026.5.27
compatibility, runtime path pinning, plugin registry recovery, live
gateway reconciliation, and clearer host-alias/startup diagnostics.
- #4332, #4402, #4769, #4776, #4779 -> `docs/about/release-notes.mdx`,
`docs/inference/inference-options.mdx`,
`docs/inference/use-local-inference.mdx`,
`docs/inference/switch-inference-providers.mdx`: Document the release
inference changes covering Local NIM waits, Hermes Anthropic routing,
Nemotron 3 Ultra, the current Ollama starter fallback, and Spark
managed-vLLM context length.
- #4628, #4652, #4733, #4745 -> `docs/about/release-notes.mdx`,
`docs/security/credential-storage.mdx`,
`docs/manage-sandboxes/messaging-channels.mdx`,
`docs/reference/troubleshooting.mdx`: Capture permission healing,
gateway-stored credential reuse, cross-sandbox messaging credential
conflict checks, and CDI preflight diagnostics.
- #4728, #4737, #4743, #4744, #4782 -> `.agents/skills/nemoclaw-user-*`:
Regenerate the user skill references from the updated source docs.
- Follow-up maintenance ->
`.agents/skills/nemoclaw-contributor-update-docs/SKILL.md`,
`.coderabbit.yaml`: Add release-prep area labels for docs and skills
PRs, and teach docs review guidance that `$$nemoclaw` is the correct
shared command placeholder for examples that work across agent aliases.
Note: the `documentation` label was not present in the repository, so
this PR is labeled with `v0.0.59` only.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Updated default model for local Ollama inference setup to qwen3.5:9b
* Added Nemotron 3 Ultra 550B as an NVIDIA Endpoints model option
* Clarified credential storage and reuse behavior for post-deployment
(day-two) operations
* Added v0.0.59 release notes covering OpenClaw compatibility, inference
options, Hermes messaging sync, and troubleshooting
* Clarified CLI selection guidance and updated OpenClaw version example
in status output
* Revised release-prep instructions and docs review guidance for CLI
alias usage
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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
4 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.
Summary
Refreshes and re-signs the root-packaged
nemoclaw-user-referenceNVSkills skill so the published skill package matches the current NemoClaw reference content and skill metadata.Related Issue
None.
Changes
skills/nemoclaw-user-reference/SKILL.md,evals/evals.json, and the generated reference markdown files.BENCHMARK.md,skill-card.md, andskill.oms.sig.skills/nemoclaw-user-referencepackage.Type of Change
Verification
npx prek run --all-filespassesnpm testpassesnpm run docsbuilds without warnings (doc changes only)Additional verification:
gh pr checks 4782 --repo NVIDIA/NemoClawreports passingcommit-lint,dco-check,check-hash,markdown-links,ShellCheck,CodeQL, and E2E recommendation checks./nvskills-ciwas requested, andsvc-nvskills-signingattached the NVSkills validation signature inskills/nemoclaw-user-reference/skill.oms.sig.NVSkills CI, CodeRabbit, and the PR review advisor were still pending at the time this description was updated.