Agent skill
nemoclaw-maintainer-day
Runs the daytime maintainer loop for NemoClaw, prioritizing items labeled with the current version target. Picks the highest-value item, executes the right workflow (merge gate, salvage, security sweep, test gaps, hotspot cooling, or sequencing), and reports progress. Use during the workday to land PRs and close issues. Designed for /loop (e.g. /loop 10m /nemoclaw-maintainer-day). Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.
Install this agent skill to your Project
npx add-skill https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-day
SKILL.md
NemoClaw Maintainer Day
Execute one pass of the maintainer loop, prioritizing version-targeted work.
Autonomy: push small fixes and approve when gates pass. Never merge. Stop and ask for merge decisions, architecture decisions, and unclear contributor intent.
References
- PR review priorities: PR-REVIEW-PRIORITIES.md
- Risky code areas: RISKY-AREAS.md
- State schema: STATE-SCHEMA.md
Step 1: Check Version Progress
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>
The first script determines the target version. The second shows shipped vs open.
Step 2: Pick One Action
From the open version-targeted items, pick the highest-value one:
- Ready-now PR — green CI, no conflicts, no major CodeRabbit, has tests → follow MERGE-GATE.md
- Salvage-now PR — close to ready, needs small fix → follow SALVAGE-PR.md
- Security item — touches risky areas → follow SECURITY-SWEEP.md
- Test-gap item — risky code with weak tests → follow TEST-GAPS.md
- Hotspot cooling — repeated conflicts → follow HOTSPOTS.md
- Sequencing needed — too large for one pass → follow SEQUENCE-WORK.md
If all version-targeted items are blocked, fall back to the general backlog. Productive work on non-labeled items is better than waiting.
Prefer finishing one almost-ready contribution over starting a new refactor.
Step 3: Execute
Follow the chosen workflow document. A good pass ends with one of:
- a PR approved, a fix pushed, a test gap closed, a hotspot mitigated, or a blocker surfaced.
Step 4: Report Progress
Re-run the progress script and show the update:
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>
If all version-targeted items are done, suggest running /nemoclaw-maintainer-evening early.
Update .nemoclaw-maintainer/state.json via the state script:
node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history <action> <item> "<note>"
Commit Hygiene
The prek "Regenerate agent skills from docs" hook auto-stages .agents/skills/ files. Before every git add and git commit on a PR branch, run git reset HEAD .agents/skills/nemoclaw-maintainer-* to unstage them. Only commit skill files in dedicated skill PRs.
Stop and Ask When
- Broad refactor or architecture decision needed
- Contributor intent unclear and diff would change semantics
- Multiple subsystems must change for CI
- Sensitive security boundaries with unclear risk
- Next step is opening a new PR or merging
/loop Integration
Designed for /loop 10m /nemoclaw-maintainer-day. Each pass should produce compact output: what was done, what changed, what needs the user. Check state.json history to avoid re-explaining prior context on repeat runs.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
NVIDIA/NemoClaw
nemoclaw-user-skills-coding
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.
NVIDIA/NemoClaw
nemoclaw-user-configure-inference
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.
NVIDIA/NemoClaw
nemoclaw-user-manage-policy
Reviews and approves blocked agent network requests in the TUI. Use when approving or denying sandbox egress requests, managing blocked network calls, or using the approval TUI. Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access.
NVIDIA/NemoClaw
nemoclaw-user-overview
Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Describes how NemoClaw works internally: CLI, plugin, blueprint runner, OpenShell orchestration, inference routing, and protection layers. Use for sandbox lifecycle and architecture mechanics; not for product definition (Overview) or multi-project placement (Ecosystem). Explains what NemoClaw covers: onboarding, lifecycle management, and management of OpenClaw within OpenShell containers, plus capabilities and why it exists. Use when users ask what NemoClaw is or what the project provides. For ecosystem placement or OpenShell-only paths, use the Ecosystem page; for internal mechanics, use How It Works. Lists changelogs and feature history for NemoClaw rel...
NVIDIA/NemoClaw
nemoclaw-maintainer-find-review-pr
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.
NVIDIA/NemoClaw
nemoclaw-maintainer-evening
Runs the end-of-day maintainer handoff for NemoClaw. Checks version target progress, bumps stragglers to the next patch version, generates a QA handoff summary, and cuts the release tag. Use at the end of the workday. Trigger keywords - evening, end of day, EOD, wrap up, ship it, cut tag, handoff, done for the day.
Didn't find tool you were looking for?