chore: skills signing batch 1#4438
Merged
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughRemoves ChangesNemoClaw Generated Skills Export
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Suggested reviewers
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
|
Collaborator
Author
|
/nvskills-ci |
Contributor
E2E Advisor RecommendationRequired E2E: None Dispatch hint: Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
Dispatch hint
|
Contributor
E2E Scenario Advisor RecommendationRequired scenario E2E: None Full scenario advisor summaryE2E Scenario AdvisorBase: Required scenario E2E
Optional scenario E2E
Relevant changed files
|
Contributor
PR Review AdvisorFindings: 3 needs attention, 5 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Since last review detailsCurrent findings:
This is an automated advisory review. A human maintainer must make the final merge decision. |
![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: 2
🤖 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-agent-skills/references/agent-skills.md`:
- Around line 1-2: Add the SPDX HTML comment header to the very top of this
Markdown file (above the "# NemoClaw Agent Skills for Your AI Coding Assistant"
title). Insert a single HTML comment with the SPDX identifier (for example: <!--
SPDX-License-Identifier: MIT -->) or the correct project license identifier,
ensuring it is the first line in the file so the file complies with the
"Markdown documentation files must include SPDX headers in HTML comment format"
guideline.
In `@skills/nemoclaw-user-agent-skills/SKILL.md`:
- Around line 1-5: Prepend the standard SPDX HTML comment header to the top of
SKILL.md before the existing YAML frontmatter (the leading '---' block) so the
file begins with an SPDX copyright/license comment; ensure the header uses HTML
comment syntax (<!-- ... -->) and includes the SPDX-License-Identifier and
copyright lines per project guidelines, leaving the existing frontmatter
(name/description/license) unchanged.
🪄 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: 990552ca-2386-499f-8aa8-aa871635475e
📒 Files selected for processing (6)
.agents/catalog-skills.yamlskills/README.mdskills/catalog-metadata.jsonskills/nemoclaw-user-agent-skills/SKILL.mdskills/nemoclaw-user-agent-skills/evals/evals.jsonskills/nemoclaw-user-agent-skills/references/agent-skills.md
💤 Files with no reviewable changes (1)
- .agents/catalog-skills.yaml
Comment on lines
+1
to
+2
| # NemoClaw Agent Skills for Your AI Coding Assistant | ||
|
|
Contributor
There was a problem hiding this comment.
Prepend SPDX header comments to this Markdown reference page.
The required SPDX HTML comment header is missing at the top of this file.
Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
# NemoClaw Agent Skills for Your AI Coding AssistantAs per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
📝 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
| # NemoClaw Agent Skills for Your AI Coding Assistant | |
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| # NemoClaw Agent Skills for Your AI Coding Assistant |
🤖 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-agent-skills/references/agent-skills.md` around lines 1
- 2, Add the SPDX HTML comment header to the very top of this Markdown file
(above the "# NemoClaw Agent Skills for Your AI Coding Assistant" title). Insert
a single HTML comment with the SPDX identifier (for example: <!--
SPDX-License-Identifier: MIT -->) or the correct project license identifier,
ensuring it is the first line in the file so the file complies with the
"Markdown documentation files must include SPDX headers in HTML comment format"
guideline.
Comment on lines
+1
to
+5
| --- | ||
| name: "nemoclaw-user-agent-skills" | ||
| description: "Describes the agent skills shipped with NemoClaw and how to access them by cloning the repository. Use when users ask about AI agent support, coding assistant integration, or the .agents/skills/ directory. Trigger keywords - nemoclaw agent skills, ai coding assistant, cursor, claude code, copilot." | ||
| license: "Apache-2.0" | ||
| --- |
Contributor
There was a problem hiding this comment.
Add required SPDX header comments at the top of this Markdown file.
This file is missing the SPDX HTML comment header before frontmatter. Please prepend the standard SPDX copyright and license comments.
Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
---
name: "nemoclaw-user-agent-skills"
description: "Describes the agent skills shipped with NemoClaw and how to access them by cloning the repository. Use when users ask about AI agent support, coding assistant integration, or the .agents/skills/ directory. Trigger keywords - nemoclaw agent skills, ai coding assistant, cursor, claude code, copilot."
license: "Apache-2.0"As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
📝 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-agent-skills" | |
| description: "Describes the agent skills shipped with NemoClaw and how to access them by cloning the repository. Use when users ask about AI agent support, coding assistant integration, or the .agents/skills/ directory. Trigger keywords - nemoclaw agent skills, ai coding assistant, cursor, claude code, copilot." | |
| license: "Apache-2.0" | |
| --- | |
| <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| --- | |
| name: "nemoclaw-user-agent-skills" | |
| description: "Describes the agent skills shipped with NemoClaw and how to access them by cloning the repository. Use when users ask about AI agent support, coding assistant integration, or the .agents/skills/ directory. Trigger keywords - nemoclaw agent skills, ai coding assistant, cursor, claude code, copilot." | |
| license: "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-agent-skills/SKILL.md` around lines 1 - 5, Prepend the
standard SPDX HTML comment header to the top of SKILL.md before the existing
YAML frontmatter (the leading '---' block) so the file begins with an SPDX
copyright/license comment; ensure the header uses HTML comment syntax (<!-- ...
-->) and includes the SPDX-License-Identifier and copyright lines per project
guidelines, leaving the existing frontmatter (name/description/license)
unchanged.
Collaborator
Author
|
/nvskills-ci |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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-get-started/references/quickstart-details.md`:
- Around line 1-2: This file is missing the required SPDX HTML comment preamble;
add the SPDX header as HTML comments at the very top of
skills/nemoclaw-user-get-started/references/quickstart-details.md (before the "#
NemoClaw Quickstart with OpenClaw: Details" title). Include the standard SPDX
lines your project requires (e.g. an SPDX-FileCopyrightText comment and an
SPDX-License-Identifier comment) in HTML comment format so the file complies
with the "*.md: Markdown documentation files must include SPDX headers in HTML
comment format" guideline.
In `@skills/nemoclaw-user-get-started/references/windows-preparation.md`:
- Around line 1-2: This Markdown file is missing the required SPDX HTML comment
preamble: insert an SPDX header as an HTML comment at the very top of the file
(above the "# Prepare Windows for NemoClaw" heading), e.g. an HTML comment that
includes SPDX-License-Identifier and any required copyright/notice lines per
repo policy; ensure the header is the first lines of the file and formatted as
an HTML comment (<!-- ... -->).
🪄 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: 06ce26d2-e490-4797-a4ce-647bdbea49f7
📒 Files selected for processing (6)
skills/nemoclaw-user-get-started/SKILL.mdskills/nemoclaw-user-get-started/evals/evals.jsonskills/nemoclaw-user-get-started/references/prerequisites.mdskills/nemoclaw-user-get-started/references/quickstart-details.mdskills/nemoclaw-user-get-started/references/quickstart-hermes.mdskills/nemoclaw-user-get-started/references/windows-preparation.md
✅ Files skipped from review due to trivial changes (3)
- skills/nemoclaw-user-get-started/SKILL.md
- skills/nemoclaw-user-get-started/references/prerequisites.md
- skills/nemoclaw-user-get-started/references/quickstart-hermes.md
Comment on lines
+1
to
+2
| # NemoClaw Quickstart with OpenClaw: Details | ||
|
|
Contributor
There was a problem hiding this comment.
Add the required SPDX HTML header at the top of this Markdown file.
This new .md file starts directly with content and is missing the required SPDX comment preamble.
As per coding guidelines, "/*.md: Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-get-started/references/quickstart-details.md` around
lines 1 - 2, This file is missing the required SPDX HTML comment preamble; add
the SPDX header as HTML comments at the very top of
skills/nemoclaw-user-get-started/references/quickstart-details.md (before the "#
NemoClaw Quickstart with OpenClaw: Details" title). Include the standard SPDX
lines your project requires (e.g. an SPDX-FileCopyrightText comment and an
SPDX-License-Identifier comment) in HTML comment format so the file complies
with the "*.md: Markdown documentation files must include SPDX headers in HTML
comment format" guideline.
Comment on lines
+1
to
+2
| # Prepare Windows for NemoClaw | ||
|
|
Contributor
There was a problem hiding this comment.
Add the required SPDX HTML header at the top of this Markdown file.
This new .md file starts with a heading and omits the SPDX comment preamble required for Markdown docs.
As per coding guidelines, "/*.md: Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-get-started/references/windows-preparation.md` around
lines 1 - 2, This Markdown file is missing the required SPDX HTML comment
preamble: insert an SPDX header as an HTML comment at the very top of the file
(above the "# Prepare Windows for NemoClaw" heading), e.g. an HTML comment that
includes SPDX-License-Identifier and any required copyright/notice lines per
repo policy; ensure the header is the first lines of the file and formatted as
an HTML comment (<!-- ... -->).
The catalog export now omits nemoclaw-skills-guide; sync the catalog-skills-export.test.ts expected directory list to match. Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Contributor
|
Actionable comments posted: 0 |
Collaborator
Author
|
/nvskils-ci |
Collaborator
Author
|
/nvskills-ci |
1 similar comment
Collaborator
Author
|
/nvskills-ci |
2 tasks
Contributor
|
Opened #4448 to simplify the skills publishing pipeline (deletes the allowlist, exporter script, drift gate, and nightly refresh bot). Once #4448 lands, this PR can rebase onto a cleaner main: drop |
Contributor
|
Actionable comments posted: 0 |
Collaborator
Author
|
/nvskills-ci |
3 similar comments
Collaborator
Author
|
/nvskills-ci |
Collaborator
Author
|
/nvskills-ci |
Collaborator
Author
|
/nvskills-ci |
jyaunches
added a commit
that referenced
this pull request
May 28, 2026
## Summary Removes the catalog-skills allowlist, exporter script, drift gate, and nightly refresh automation. Publishing a user-facing skill is now: ```bash cp -r .agents/skills/nemoclaw-user-<name> skills/ git commit -am "chore(skills): publish nemoclaw-user-<name>" # open PR, comment /nvskills-ci, merge ``` `skills/` is the source of truth for what is published. NVSkills CI signs one skill per PR (which is the existing timeout constraint anyway). ## Why The current gate (`scripts/export-catalog-skills.py --check --allow-missing`) requires `.agents/catalog-skills.yaml` and `skills/` to be in lockstep on every commit. NVSkills CI's per-skill signing cadence means we land published skills incrementally over many PRs, so allowlist and export are intentionally out of sync for the duration of the migration. The gate fights that workflow and forced #4438 to skip pre-commit hooks just to push. The system as a whole had three sources of truth (allowlist, source `.agents/skills/`, exported `skills/`) all needing to agree. Collapsing to two (source + published) eliminates the class of inconsistencies the gate was built to catch — because there's nothing left to be inconsistent. ## What replaces drift detection On-demand verification: ask an agent to diff `skills/<name>/` against `.agents/skills/<name>/` and report any content differences (ignoring `skill.oms.sig` and `skill-card.md`). Documented in the rewritten `.github/catalog-skills-signing-flow.md`. The nightly refresh bot's job (regenerating from source) is no longer meaningful since there's no allowlist driving regeneration — each published skill is now an explicit human decision per PR. ## Removed - `.agents/catalog-skills.yaml` (allowlist) - `scripts/export-catalog-skills.py` (exporter + checker, 460 lines) - `test/catalog-skills-export.test.ts` (test for the deleted script) - `.github/workflows/catalog-skills-refresh.yaml` (nightly refresh bot) - `.github/pr-bodies/catalog-skills-refresh.md` (bot PR body template) - `.pre-commit-config.yaml` `catalog-skills-export` hook - `.github/workflows/pr.yaml` "Verify catalog skills export" step - `.github/CODEOWNERS` line for the deleted allowlist ## Rewritten - `.github/catalog-skills-signing-flow.md` — was a Mermaid diagram of the seven-step generator/checker/refresh flow. Now a 40-line manual workflow doc. ## Downstream #4438 (and the 9 per-skill PRs to follow) need to rebase onto this. After rebase, Miyoung's PR becomes a plain `cp -r` of two skill directories with no manifest and no SPDX-stripping — strictly "as authored" content under `skills/`. ## Type of Change - [x] Code change (refactor / removal) ## Verification - [x] No secrets, API keys, or credentials committed Signed-off-by: Julie Yaunches <jyaunches@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Removed catalog skills automation infrastructure, including workflow, scripts, and configuration files * Updated CI verification workflow to focus on platform documentation checks * **Documentation** * Simplified skill publishing guide with step-by-step instructions for adding, refreshing, and validating skills * **Tests** * Removed catalog skills export test suite <!-- review_stack_entry_start --> [](https://app.coderabbit.ai/change-stack/NVIDIA/NemoClaw/pull/4448?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) <!-- review_stack_entry_end --> <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
wscurran
added
enhancement: skill
Contributor
There was a problem hiding this comment.
Actionable comments posted: 17
🤖 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-configure-inference/references/inference-options.md`:
- Line 1: This Markdown file lacks the required SPDX HTML comment header; add
the mandatory SPDX header as an HTML comment at the top of the document (above
the existing "# NemoClaw Inference Options" heading) using the project’s
standard SPDX tag (e.g., <!-- SPDX-License-Identifier: ... -->) so the file
begins with the SPDX comment before any content.
In `@skills/nemoclaw-user-configure-inference/references/set-up-sub-agent.md`:
- Line 1: Prepend the required SPDX HTML comment header to this Markdown file so
it complies with repo rules: add an HTML comment at the very top of
skills/nemoclaw-user-configure-inference/references/set-up-sub-agent.md
containing the SPDX license identifier (e.g., <!-- SPDX-License-Identifier:
Apache-2.0 -->) before the existing content (the "# Set Up Task-Specific
Sub-Agents" header).
In `@skills/nemoclaw-user-configure-inference/SKILL.md`:
- Line 1: Add an SPDX header at the top of SKILL.md in HTML comment format;
insert a single line like <!-- SPDX-License-Identifier: <license-identifier> -->
(replace <license-identifier> with the project's correct SPDX tag) as the very
first line of SKILL.md so the file complies with the Markdown SPDX requirement.
In `@skills/nemoclaw-user-configure-security/references/best-practices.md`:
- Around line 22-43: The Mermaid diagram uses emoji in node labels (e.g., nodes
PROC, FS, AGENT, NET, INF, NC, SB, GW, OUTSIDE, YOU); update each label to
remove emoji and use plain technical text (for example change "⚙️ Process
Layer<br/>Controls what the agent can execute" to "Process Layer<br/>Controls
what the agent can execute") ensuring all occurrences in the block are cleaned
while preserving descriptive text and line breaks.
- Line 1: The file best-practices.md is missing the required SPDX header in HTML
comment format; add a single-line SPDX license identifier as an HTML comment at
the very top of the file (e.g., <!-- SPDX-License-Identifier: ... -->), using
the appropriate SPDX identifier for the project, so the header appears before
the "# NemoClaw Security Best Practices: Controls, Risks, and Posture Profiles"
title.
In `@skills/nemoclaw-user-deploy-remote/references/brev-web-ui.md`:
- Line 1: Add the required SPDX header as an HTML comment at the very top of
this Markdown file: insert a single-line or multi-line HTML comment containing
the SPDX identifier (e.g. <!-- SPDX-FileCopyrightText: <copyright holder> -->
and <!-- SPDX-License-Identifier: <SPDX-License-Identifier> -->) before the
existing content so the file conforms to the "`**/*.md`: Markdown documentation
files must include SPDX headers in HTML comment format" guideline.
In `@skills/nemoclaw-user-manage-policy/references/approve-network-requests.md`:
- Line 1: This Markdown file is missing the required SPDX header; add an HTML
comment SPDX header line (e.g. <!-- SPDX-License-Identifier: <LICENSE> --> using
the project’s canonical license identifier) at the very top of the file,
immediately before the existing first heading "# Approve or Deny Agent Network
Requests", so the document begins with the SPDX comment.
In
`@skills/nemoclaw-user-manage-policy/references/integration-policy-examples.md`:
- Line 1: Add an SPDX HTML comment header as the very first line of the Markdown
file (above the "# Common NemoClaw Integration Policy Examples" title). Insert a
single-line HTML comment of the form <!-- SPDX-License-Identifier: <SPDX_ID> -->
(e.g., MIT, Apache-2.0) using the project's chosen license identifier so the
file complies with the "*.md" guideline requiring an SPDX header.
In `@skills/nemoclaw-user-manage-policy/SKILL.md`:
- Line 1: The SKILL.md file is missing the required SPDX header; add an HTML
comment SPDX header as the first lines of the file (e.g. <!--
SPDX-License-Identifier: MIT -->), ensuring it follows the project’s specified
license identifier and exact HTML comment format and appears before any content
or frontmatter in SKILL.md.
In `@skills/nemoclaw-user-manage-sandboxes/references/backup-restore.md`:
- Line 1: This Markdown file is missing the required SPDX header; add an
HTML-comment SPDX header as the first line of the document (before the "# Backup
and Restore Workspace Files" heading) using the project's chosen SPDX identifier
(for example, <!-- SPDX-License-Identifier: MIT -->), ensuring the exact SPDX
token matches the repository license policy.
In `@skills/nemoclaw-user-manage-sandboxes/references/messaging-channels.md`:
- Line 1: Add the required SPDX header as an HTML comment at the top of this
Markdown file (above the "# Messaging Channels" heading): insert a single-line
SPDX declaration like <!-- SPDX-License-Identifier: <LICENSE> --> (replacing
<LICENSE> with the appropriate identifier per project policy) so the file
complies with the "*.md" SPDX header rule.
In `@skills/nemoclaw-user-overview/references/overview.md`:
- Line 1: Add the required SPDX HTML comment header at the very top of the
Markdown file (above the "# Overview of NVIDIA NemoClaw" heading) in the HTML
comment format used by our guidelines (e.g., an HTML comment containing
SPDX-License-Identifier and any required SPDX-FileCopyrightText); ensure the
SPDX header is present and correctly formatted so the file complies with the
"`**/*.md`: Markdown documentation files must include SPDX headers in HTML
comment format" rule.
In `@skills/nemoclaw-user-overview/references/release-notes.md`:
- Line 1: Add the required SPDX header to the top of release-notes.md by
inserting an HTML comment containing the correct SPDX identifier (for example,
SPDX-License-Identifier: MIT) as the very first line of the file so it conforms
to the "*.md" guideline requiring SPDX headers in HTML comment format.
In `@skills/nemoclaw-user-reference/references/cli-selection-guide.md`:
- Line 1: Add the required SPDX header as an HTML comment immediately before the
existing title line in cli-selection-guide.md; insert a single-line HTML comment
containing the SPDX identifier (e.g., <!-- SPDX-License-Identifier: <identifier>
-->) directly above the "# CLI Selection Guide" heading so the document includes
the mandated SPDX header format.
In `@skills/nemoclaw-user-reference/references/commands.md`:
- Line 1: Add an SPDX HTML comment header at the very top of the Markdown file
before the existing "# NemoClaw CLI Commands Reference" line; insert a
single-line HTML comment of the form <!-- SPDX-License-Identifier:
<YOUR_LICENSE> --> (replace <YOUR_LICENSE> with the project's SPDX identifier)
so the file contains the required SPDX header.
In `@skills/nemoclaw-user-reference/references/network-policies.md`:
- Line 1: This Markdown file starts with "# Network Policies" but is missing the
required SPDX header; add the mandatory SPDX HTML comment as the first line of
the file (e.g. <!-- SPDX-License-Identifier: <LICENSE-ID> -->) above the "#
Network Policies" heading to satisfy the "`**/*.md` must include SPDX headers in
HTML comment format" guideline.
In `@skills/nemoclaw-user-reference/references/troubleshooting.md`:
- Line 1: This Markdown file is missing the required SPDX header; add an SPDX
license header as an HTML comment at the very top of the document (above the "#
Troubleshooting" header) in the format mandated by the guidelines (e.g., <!--
SPDX-License-Identifier: <identifier> -->) so the file includes the required
SPDX metadata.
🪄 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: 64125fef-97b3-458d-b589-7098fe088234
⛔ Files ignored due to path filters (1)
skills/nemoclaw-user-overview/references/images/nemoclaw-highlevel-component-diagram.pngis excluded by!**/*.png
📒 Files selected for processing (47)
skills/catalog-metadata.jsonskills/nemoclaw-user-agent-skills/evals/evals.jsonskills/nemoclaw-user-configure-inference/SKILL.mdskills/nemoclaw-user-configure-inference/evals/evals.jsonskills/nemoclaw-user-configure-inference/references/inference-options.mdskills/nemoclaw-user-configure-inference/references/set-up-sub-agent.mdskills/nemoclaw-user-configure-inference/references/switch-inference-providers.mdskills/nemoclaw-user-configure-inference/references/tool-calling-reliability.mdskills/nemoclaw-user-configure-inference/references/use-local-inference-details.mdskills/nemoclaw-user-configure-security/SKILL.mdskills/nemoclaw-user-configure-security/evals/evals.jsonskills/nemoclaw-user-configure-security/references/best-practices.mdskills/nemoclaw-user-configure-security/references/credential-storage.mdskills/nemoclaw-user-configure-security/references/openclaw-controls.mdskills/nemoclaw-user-deploy-remote/SKILL.mdskills/nemoclaw-user-deploy-remote/evals/evals.jsonskills/nemoclaw-user-deploy-remote/references/brev-web-ui.mdskills/nemoclaw-user-deploy-remote/references/install-openclaw-plugins.mdskills/nemoclaw-user-deploy-remote/references/sandbox-hardening.mdskills/nemoclaw-user-get-started/evals/evals.jsonskills/nemoclaw-user-manage-policy/SKILL.mdskills/nemoclaw-user-manage-policy/evals/evals.jsonskills/nemoclaw-user-manage-policy/references/approve-network-requests.mdskills/nemoclaw-user-manage-policy/references/customize-network-policy-details.mdskills/nemoclaw-user-manage-policy/references/integration-policy-examples.mdskills/nemoclaw-user-manage-sandboxes/SKILL.mdskills/nemoclaw-user-manage-sandboxes/evals/evals.jsonskills/nemoclaw-user-manage-sandboxes/references/backup-restore.mdskills/nemoclaw-user-manage-sandboxes/references/lifecycle-details.mdskills/nemoclaw-user-manage-sandboxes/references/messaging-channels.mdskills/nemoclaw-user-manage-sandboxes/references/runtime-controls.mdskills/nemoclaw-user-manage-sandboxes/references/workspace-files.mdskills/nemoclaw-user-monitor-sandbox/SKILL.mdskills/nemoclaw-user-monitor-sandbox/evals/evals.jsonskills/nemoclaw-user-overview/SKILL.mdskills/nemoclaw-user-overview/evals/evals.jsonskills/nemoclaw-user-overview/references/ecosystem.mdskills/nemoclaw-user-overview/references/how-it-works.mdskills/nemoclaw-user-overview/references/overview.mdskills/nemoclaw-user-overview/references/release-notes.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.md
✅ Files skipped from review due to trivial changes (23)
- skills/nemoclaw-user-monitor-sandbox/SKILL.md
- skills/nemoclaw-user-manage-sandboxes/references/lifecycle-details.md
- skills/nemoclaw-user-reference/SKILL.md
- skills/nemoclaw-user-manage-sandboxes/references/runtime-controls.md
- skills/nemoclaw-user-manage-sandboxes/references/workspace-files.md
- skills/nemoclaw-user-configure-security/references/credential-storage.md
- skills/nemoclaw-user-configure-inference/references/switch-inference-providers.md
- skills/nemoclaw-user-configure-security/references/openclaw-controls.md
- skills/nemoclaw-user-overview/references/how-it-works.md
- skills/catalog-metadata.json
- skills/nemoclaw-user-manage-policy/references/customize-network-policy-details.md
- skills/nemoclaw-user-manage-sandboxes/SKILL.md
- skills/nemoclaw-user-configure-inference/references/tool-calling-reliability.md
- skills/nemoclaw-user-manage-sandboxes/evals/evals.json
- skills/nemoclaw-user-overview/SKILL.md
- skills/nemoclaw-user-reference/references/architecture.md
- skills/nemoclaw-user-configure-security/SKILL.md
- skills/nemoclaw-user-configure-security/evals/evals.json
- skills/nemoclaw-user-overview/references/ecosystem.md
- skills/nemoclaw-user-deploy-remote/SKILL.md
- skills/nemoclaw-user-deploy-remote/references/sandbox-hardening.md
- skills/nemoclaw-user-deploy-remote/references/install-openclaw-plugins.md
- skills/nemoclaw-user-configure-inference/references/use-local-inference-details.md
🚧 Files skipped from review as they are similar to previous changes (1)
- skills/nemoclaw-user-get-started/evals/evals.json
| @@ -0,0 +1,140 @@ | |||
| # NemoClaw Inference Options | |||
Contributor
There was a problem hiding this comment.
Add SPDX header to satisfy Markdown policy.
The file is missing the mandatory SPDX HTML comment header.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-configure-inference/references/inference-options.md` at
line 1, This Markdown file lacks the required SPDX HTML comment header; add the
mandatory SPDX header as an HTML comment at the top of the document (above the
existing "# NemoClaw Inference Options" heading) using the project’s standard
SPDX tag (e.g., <!-- SPDX-License-Identifier: ... -->) so the file begins with
the SPDX comment before any content.
| @@ -0,0 +1,118 @@ | |||
| # Set Up Task-Specific Sub-Agents | |||
Contributor
There was a problem hiding this comment.
Prepend the required SPDX HTML comment header.
This Markdown doc currently omits the SPDX header required by repo rules.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-configure-inference/references/set-up-sub-agent.md` at
line 1, Prepend the required SPDX HTML comment header to this Markdown file so
it complies with repo rules: add an HTML comment at the very top of
skills/nemoclaw-user-configure-inference/references/set-up-sub-agent.md
containing the SPDX license identifier (e.g., <!-- SPDX-License-Identifier:
Apache-2.0 -->) before the existing content (the "# Set Up Task-Specific
Sub-Agents" header).
| @@ -0,0 +1,281 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
Add SPDX header at the beginning of the file.
This Markdown file is missing the required SPDX header in HTML comment format.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-configure-inference/SKILL.md` at line 1, Add an SPDX
header at the top of SKILL.md in HTML comment format; insert a single line like
<!-- SPDX-License-Identifier: <license-identifier> --> (replace
<license-identifier> with the project's correct SPDX tag) as the very first line
of SKILL.md so the file complies with the Markdown SPDX requirement.
| @@ -0,0 +1,509 @@ | |||
| # NemoClaw Security Best Practices: Controls, Risks, and Posture Profiles | |||
Contributor
There was a problem hiding this comment.
Add SPDX header at the top of this Markdown file.
This doc is missing the required SPDX header in HTML comment format.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-configure-security/references/best-practices.md` at line
1, The file best-practices.md is missing the required SPDX header in HTML
comment format; add a single-line SPDX license identifier as an HTML comment at
the very top of the file (e.g., <!-- SPDX-License-Identifier: ... -->), using
the appropriate SPDX identifier for the project, so the header appears before
the "# NemoClaw Security Best Practices: Controls, Risks, and Posture Profiles"
title.
Comment on lines
+22
to
+43
| YOU["👤 Operator"] | ||
|
|
||
| subgraph NC["NemoClaw + OpenShell"] | ||
| direction TB | ||
|
|
||
| subgraph SB["Sandbox: the agent's isolated world"] | ||
| direction LR | ||
| PROC["⚙️ Process Layer<br/>Controls what the agent can execute"] | ||
| FS["📁 Filesystem Layer<br/>Controls what the agent can read and write"] | ||
| AGENT["🤖 Agent"] | ||
| end | ||
|
|
||
| subgraph GW["Gateway: the gatekeeper"] | ||
| direction LR | ||
| NET["🌐 Network Layer<br/>Controls where the agent can connect"] | ||
| INF["🧠 Inference Layer<br/>Controls which AI models the agent can use"] | ||
| end | ||
| end | ||
| end | ||
|
|
||
| OUTSIDE["🌍 Outside World<br/>Internet · AI Providers · APIs"] | ||
|
|
Contributor
There was a problem hiding this comment.
Remove emoji from the technical diagram labels.
The Mermaid node labels include emoji, which violates the docs rule for technical prose.
As per coding guidelines, "No emoji in technical prose."
🤖 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-configure-security/references/best-practices.md` around
lines 22 - 43, The Mermaid diagram uses emoji in node labels (e.g., nodes PROC,
FS, AGENT, NET, INF, NC, SB, GW, OUTSIDE, YOU); update each label to remove
emoji and use plain technical text (for example change "⚙️ Process
Layer<br/>Controls what the agent can execute" to "Process Layer<br/>Controls
what the agent can execute") ensuring all occurrences in the block are cleaned
while preserving descriptive text and line breaks.
| @@ -0,0 +1,242 @@ | |||
| # Release Notes | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header at the top of this Markdown file.
This documentation file is missing the required SPDX header comment.
Proposed fix
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
# Release NotesAs per coding guidelines "**/*.md: Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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-overview/references/release-notes.md` at line 1, Add the
required SPDX header to the top of release-notes.md by inserting an HTML comment
containing the correct SPDX identifier (for example, SPDX-License-Identifier:
MIT) as the very first line of the file so it conforms to the "*.md" guideline
requiring SPDX headers in HTML comment format.
| @@ -0,0 +1,203 @@ | |||
| # CLI Selection Guide | |||
Contributor
There was a problem hiding this comment.
Insert SPDX header before the title.
This Markdown page is missing the required SPDX header in HTML comment format.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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 immediately before the existing
title line in cli-selection-guide.md; insert a single-line HTML comment
containing the SPDX identifier (e.g., <!-- SPDX-License-Identifier: <identifier>
-->) directly above the "# CLI Selection Guide" heading so the document includes
the mandated SPDX header format.
| @@ -0,0 +1,1379 @@ | |||
| # NemoClaw CLI Commands Reference | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header to this Markdown document.
The file starts directly with content and is missing the SPDX HTML comment header.
As per coding guidelines, "Markdown documentation files must include SPDX headers in HTML comment format".
🤖 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/commands.md` at line 1, Add an SPDX
HTML comment header at the very top of the Markdown file before the existing "#
NemoClaw CLI Commands Reference" line; insert a single-line HTML comment of the
form <!-- SPDX-License-Identifier: <YOUR_LICENSE> --> (replace <YOUR_LICENSE>
with the project's SPDX identifier) so the file contains the required SPDX
header.
| @@ -0,0 +1,123 @@ | |||
| # Network Policies | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header at the top of this Markdown file.
The file begins with Markdown content and omits the mandatory SPDX HTML header.
Proposed fix
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
# Network PoliciesAs per coding guidelines "**/*.md: Markdown documentation files must include SPDX headers in HTML comment format".
📝 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
| # Network Policies | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| # Network Policies |
🤖 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,
This Markdown file starts with "# Network Policies" but is missing the required
SPDX header; add the mandatory SPDX HTML comment as the first line of the file
(e.g. <!-- SPDX-License-Identifier: <LICENSE-ID> -->) above the "# Network
Policies" heading to satisfy the "`**/*.md` must include SPDX headers in HTML
comment format" guideline.
| @@ -0,0 +1,1419 @@ | |||
| # Troubleshooting | |||
Contributor
There was a problem hiding this comment.
Add required SPDX header at the top of this Markdown file.
Required SPDX header is missing from this Markdown doc.
Proposed fix
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
# TroubleshootingAs per coding guidelines "**/*.md: Markdown documentation files must include SPDX headers in HTML comment format".
📝 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
| # Troubleshooting | |
| <!-- SPDX-License-Identifier: Apache-2.0 --> | |
| # Troubleshooting |
🤖 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, This
Markdown file is missing the required SPDX header; add an SPDX license header as
an HTML comment at the very top of the document (above the "# Troubleshooting"
header) in the format mandated by the guidelines (e.g., <!--
SPDX-License-Identifier: <identifier> -->) so the file includes the required
SPDX metadata.
…agent-skills # Conflicts: # .agents/catalog-skills.yaml # test/catalog-skills-export.test.ts
This was referenced May 28, 2026
This reverts commit 4c3d19a.
Contributor
|
/nvskills-ci |
](https://app.coderabbit.ai/change-stack/NVIDIA/NemoClaw/pull/4448?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack){kind=link}
Signed-off-by: nvskills-svc-account <svc-nvskills-signing@nvidia.com>
miyoungc
changed the title
Collaborator
Author
|
/nvskills-ci |
jyaunches
approved these changes
May 28, 2026
This was referenced May 29, 2026
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
export nemoclaw user agent skills
Related Issue
Changes
Type of Change
Verification
npx prek run --all-filespassesnpm testpassesnpm run docsbuilds without warnings (doc changes only)Signed-off-by: Your Name your-email@example.com
Summary by CodeRabbit