NemoClaw Skills Guide
NVIDIA NemoClaw runs OpenClaw always-on assistants inside hardened OpenShell sandboxes with NVIDIA inference (Nemotron).
It provides CLI tooling, guided onboarding, a security blueprint, routed inference, and workspace management.
This guide lists every agent skill shipped with NemoClaw, organized by audience.
Load the specific skill you need after identifying it here.
Skill Buckets
Skills are grouped into three buckets by audience.
The prefix in each skill name indicates who it is for.
nemoclaw-user-* (1 skill)
For end users operating a NemoClaw sandbox.
Covers routing human users' AI agents to the canonical NemoClaw Markdown documentation.
nemoclaw-maintainer-*
For project maintainers.
Covers the daily maintainer cadence, trusted E2E dispatch, continuous E2E maintenance, runtime-provider integration and qualification, Launchable validation, workflow policy, CI failure classification, CI performance analysis, pull request value-stream analysis, documentation refactors, releases, review selection, comparison, triage, security review, and stale bug verification.
nemoclaw-contributor-* (6 skills)
For contributors to the NemoClaw codebase.
The lifecycle runs from checkout setup through planning, implementation, and publication.
Each stage has one owner: nemoclaw-contributor-plan-issue refines an issue into capability slices,
nemoclaw-contributor-implement-issue implements a slice and owns its tests, and
nemoclaw-contributor-create-pr publishes the branch and follows CI and automated review.
Load nemoclaw-contributor-update-dependencies for a dependency upgrade and
nemoclaw-contributor-update-docs for documentation catch-up.
The dependency workflow runs inside the implementation stage.
Component-specific guidance lives with the package it describes, not in a skill.
Skill Catalog
User Skills
| Skill |
Summary |
nemoclaw-user-guide |
Route human users' AI agents to llms.txt and the relevant NemoClaw Markdown docs for installation, configuration, operation, security, and troubleshooting. |
Maintainer Skills
| Skill |
Summary |
nemoclaw-maintainer-morning |
Morning standup: triage the backlog, determine the day's target version, label selected items, surface stragglers, and output the daily plan. |
nemoclaw-maintainer-triage |
Propose Issue Type, Project fields, and approved labels for issues and PRs. Apply only changes that the maintainer accepts. |
nemoclaw-maintainer-policies |
Answer maintainer workflow questions from the read-only policy references. |
nemoclaw-maintainer-cross-issue-sweep |
Find open issues that a PR can also fix or conflict with. Report file and line evidence. |
nemoclaw-maintainer-day |
Run one daytime maintainer pass for the release version. Select a merge, salvage, security, test, conflict, or sequencing workflow. Designed for /loop. |
nemoclaw-maintainer-evening |
Complete the cumulative documentation PR and release entry, show release context, and optionally start tag cutting. |
nemoclaw-maintainer-cut-release-tag |
Verify candidate evidence, record the maintainer's E2E decision, and cut one signed semver tag. |
nemoclaw-maintainer-e2e |
Describe default E2E triggered by pushes to main, dispatch exact-revision manual PR E2E, and verify applicable workflow evidence. |
nemoclaw-maintainer-classify-ci-failure |
Classify one failed GitHub Actions job from bounded, redacted logs and an optional validated artifact. |
nemoclaw-maintainer-analyze-ci-performance |
Analyze retained CLI test timings and base-image publication latency with bounded, read-only GitHub evidence. |
nemoclaw-maintainer-analyze-pr-value-stream |
Measure one PR from its earliest observable branch push through merge, separate approval delay from automation time, and compare the latest revision with a target. |
nemoclaw-maintainer-runtime-provider |
Implement or review one managed runtime provider through the bundle API, qualification-backed activation, provider-neutral orchestration, and exact-commit E2E qualification. |
nemoclaw-maintainer-fix-e2e-failures |
Continuously fix automatic main E2E failures by root cause, coordinate peer approvals, merge eligible PRs, and monitor new results. |
nemoclaw-maintainer-validate-launchable |
Run advisory validation of the staging Brev Launchable deployment, image and runtime identity, preinstalled user journey, inference, and cleanup. |
nemoclaw-maintainer-release-notes |
Draft the post-tag Announcement from live tag/compare data, with the three-paragraph narrative, categorized change list, and external-only contributor thanks. |
nemoclaw-maintainer-find-review-pr |
Find open security PRs with Urgent or High Project Priority. Link each PR to its issue and identify competing PRs. |
nemoclaw-maintainer-pr-comparator |
Compare open PRs for the same issue. Apply gates and score the eligible PRs before you recommend one to merge. |
nemoclaw-maintainer-normalize-title-tags |
Preview and remove bracketed NemoClaw title tags from issues and PRs case-insensitively, even when the tag appears later in the title. |
nemoclaw-maintainer-refactor-docs |
Split oversized Fern docs into focused topics with journey-based navigation, canonical ownership, route-safe redirects, variant checks, and deduplication. |
nemoclaw-maintainer-security-code-review |
Review PR or issue changes in nine security categories. Report PASS, WARNING, or FAIL for each category. |
nemoclaw-maintainer-verify-stale |
Verify whether old issues with native Issue Type Bug still reproduce on latest. Reuses or provisions a Brev box, scores confidence, and proposes evidence-backed Project/comment writes for approval; never auto-closes. |
Contributor Skills
| Skill |
Summary |
nemoclaw-contributor-onboard |
Set up, repair, or verify a trusted source checkout, with explicit opt-ins for host-visible CLI exposure, the pinned agent, and runtime onboarding. |
nemoclaw-contributor-plan-issue |
Research, refine, and divide a named issue into independently valuable capability slices without implementing or publishing them. |
nemoclaw-contributor-implement-issue |
Implement the smallest accepted issue capability slice with focused validation and no pull request publication. |
nemoclaw-contributor-create-pr |
Create a PR with the NemoClaw template, required checks, DCO declaration, and verified commits. Then, monitor CI and automated reviews. |
nemoclaw-contributor-update-dependencies |
Audit and implement a dependency upgrade from current upstream and downstream contracts, including Hermes CalVer and base-image upgrades. |
nemoclaw-contributor-update-docs |
Find user-visible changes merged to main and update their owning documentation under current repository policy. |
Getting Started
Ask the user which role best describes them:
- User — operating a NemoClaw sandbox (running, configuring, monitoring).
- Contributor — contributing code or docs to the NemoClaw project.
- Maintainer — triaging, reviewing, releasing, and managing the project day-to-day.
Skills are cumulative. Each role includes the skills from the roles above it:
| Role |
Skills included |
Start with |
| User |
nemoclaw-user-* |
nemoclaw-user-guide |
| Contributor |
nemoclaw-user-* + nemoclaw-contributor-* |
nemoclaw-contributor-onboard |
| Maintainer |
All skills |
nemoclaw-maintainer-morning |
After identifying the role, present the applicable skills from the Skill Catalog above and recommend the starting skill.
1---2name: nemoclaw-skills-guide-23description: 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.4license: Apache-2.05---67<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->8<!-- SPDX-License-Identifier: Apache-2.0 -->910# NemoClaw Skills Guide1112NVIDIA NemoClaw runs OpenClaw always-on assistants inside hardened OpenShell sandboxes with NVIDIA inference (Nemotron).13It provides CLI tooling, guided onboarding, a security blueprint, routed inference, and workspace management.1415This guide lists every agent skill shipped with NemoClaw, organized by audience.16Load the specific skill you need after identifying it here.1718## Skill Buckets1920Skills are grouped into three buckets by audience.21The prefix in each skill name indicates who it is for.2223### `nemoclaw-user-*` (1 skill)2425For end users operating a NemoClaw sandbox.26Covers routing human users' AI agents to the canonical NemoClaw Markdown documentation.2728### `nemoclaw-maintainer-*`2930For project maintainers.31Covers the daily maintainer cadence, trusted E2E dispatch, continuous E2E maintenance, runtime-provider integration and qualification, Launchable validation, workflow policy, CI failure classification, CI performance analysis, pull request value-stream analysis, documentation refactors, releases, review selection, comparison, triage, security review, and stale bug verification.3233### `nemoclaw-contributor-*` (6 skills)3435For contributors to the NemoClaw codebase.36The lifecycle runs from checkout setup through planning, implementation, and publication.37Each stage has one owner: `nemoclaw-contributor-plan-issue` refines an issue into capability slices,38`nemoclaw-contributor-implement-issue` implements a slice and owns its tests, and39`nemoclaw-contributor-create-pr` publishes the branch and follows CI and automated review.40Load `nemoclaw-contributor-update-dependencies` for a dependency upgrade and41`nemoclaw-contributor-update-docs` for documentation catch-up.42The dependency workflow runs inside the implementation stage.43Component-specific guidance lives with the package it describes, not in a skill.4445## Skill Catalog4647### User Skills4849<!-- user-skills-table:begin -->50| Skill | Summary |51|-------|---------|52| `nemoclaw-user-guide` | Route human users' AI agents to `llms.txt` and the relevant NemoClaw Markdown docs for installation, configuration, operation, security, and troubleshooting. |53<!-- user-skills-table:end -->5455### Maintainer Skills5657| Skill | Summary |58|-------|---------|59| `nemoclaw-maintainer-morning` | Morning standup: triage the backlog, determine the day's target version, label selected items, surface stragglers, and output the daily plan. |60| `nemoclaw-maintainer-triage` | Propose Issue Type, Project fields, and approved labels for issues and PRs. Apply only changes that the maintainer accepts. |61| `nemoclaw-maintainer-policies` | Answer maintainer workflow questions from the read-only policy references. |62| `nemoclaw-maintainer-cross-issue-sweep` | Find open issues that a PR can also fix or conflict with. Report file and line evidence. |63| `nemoclaw-maintainer-day` | Run one daytime maintainer pass for the release version. Select a merge, salvage, security, test, conflict, or sequencing workflow. Designed for `/loop`. |64| `nemoclaw-maintainer-evening` | Complete the cumulative documentation PR and release entry, show release context, and optionally start tag cutting. |65| `nemoclaw-maintainer-cut-release-tag` | Verify candidate evidence, record the maintainer's E2E decision, and cut one signed semver tag. |66| `nemoclaw-maintainer-e2e` | Describe default E2E triggered by pushes to `main`, dispatch exact-revision manual PR E2E, and verify applicable workflow evidence. |67| `nemoclaw-maintainer-classify-ci-failure` | Classify one failed GitHub Actions job from bounded, redacted logs and an optional validated artifact. |68| `nemoclaw-maintainer-analyze-ci-performance` | Analyze retained CLI test timings and base-image publication latency with bounded, read-only GitHub evidence. |69| `nemoclaw-maintainer-analyze-pr-value-stream` | Measure one PR from its earliest observable branch push through merge, separate approval delay from automation time, and compare the latest revision with a target. |70| `nemoclaw-maintainer-runtime-provider` | Implement or review one managed runtime provider through the bundle API, qualification-backed activation, provider-neutral orchestration, and exact-commit E2E qualification. |71| `nemoclaw-maintainer-fix-e2e-failures` | Continuously fix automatic `main` E2E failures by root cause, coordinate peer approvals, merge eligible PRs, and monitor new results. |72| `nemoclaw-maintainer-validate-launchable` | Run advisory validation of the staging Brev Launchable deployment, image and runtime identity, preinstalled user journey, inference, and cleanup. |73| `nemoclaw-maintainer-release-notes` | Draft the post-tag Announcement from live tag/compare data, with the three-paragraph narrative, categorized change list, and external-only contributor thanks. |74| `nemoclaw-maintainer-find-review-pr` | Find open security PRs with Urgent or High Project Priority. Link each PR to its issue and identify competing PRs. |75| `nemoclaw-maintainer-pr-comparator` | Compare open PRs for the same issue. Apply gates and score the eligible PRs before you recommend one to merge. |76| `nemoclaw-maintainer-normalize-title-tags` | Preview and remove bracketed `NemoClaw` title tags from issues and PRs case-insensitively, even when the tag appears later in the title. |77| `nemoclaw-maintainer-refactor-docs` | Split oversized Fern docs into focused topics with journey-based navigation, canonical ownership, route-safe redirects, variant checks, and deduplication. |78| `nemoclaw-maintainer-security-code-review` | Review PR or issue changes in nine security categories. Report PASS, WARNING, or FAIL for each category. |79| `nemoclaw-maintainer-verify-stale` | Verify whether old issues with native Issue Type `Bug` still reproduce on latest. Reuses or provisions a Brev box, scores confidence, and proposes evidence-backed Project/comment writes for approval; never auto-closes. |8081### Contributor Skills8283| Skill | Summary |84|-------|---------|85| `nemoclaw-contributor-onboard` | Set up, repair, or verify a trusted source checkout, with explicit opt-ins for host-visible CLI exposure, the pinned agent, and runtime onboarding. |86| `nemoclaw-contributor-plan-issue` | Research, refine, and divide a named issue into independently valuable capability slices without implementing or publishing them. |87| `nemoclaw-contributor-implement-issue` | Implement the smallest accepted issue capability slice with focused validation and no pull request publication. |88| `nemoclaw-contributor-create-pr` | Create a PR with the NemoClaw template, required checks, DCO declaration, and verified commits. Then, monitor CI and automated reviews. |89| `nemoclaw-contributor-update-dependencies` | Audit and implement a dependency upgrade from current upstream and downstream contracts, including Hermes CalVer and base-image upgrades. |90| `nemoclaw-contributor-update-docs` | Find user-visible changes merged to `main` and update their owning documentation under current repository policy. |9192## Getting Started9394Ask the user which role best describes them:9596- **User** — operating a NemoClaw sandbox (running, configuring, monitoring).97- **Contributor** — contributing code or docs to the NemoClaw project.98- **Maintainer** — triaging, reviewing, releasing, and managing the project day-to-day.99100Skills are cumulative. Each role includes the skills from the roles above it:101102| Role | Skills included | Start with |103|------|----------------|------------|104| User | `nemoclaw-user-*` | `nemoclaw-user-guide` |105| Contributor | `nemoclaw-user-*` + `nemoclaw-contributor-*` | `nemoclaw-contributor-onboard` |106| Maintainer | All skills | `nemoclaw-maintainer-morning` |107108After identifying the role, present the applicable skills from the Skill Catalog above and recommend the starting skill.
NVIDIA