How do I install the Nemoclaw Maintainer Day skill?

Run npx skillmds@latest add nvidia/nemoclaw-maintainer-day-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nemoclaw Maintainer Day safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nemoclaw Maintainer Day?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nemoclaw Maintainer Day free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nemoclaw Maintainer Day?

NVIDIA (@nvidia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nemoclaw Maintainer Day by nvidia — Agent Skill

Name: Nemoclaw Maintainer Day
Rating: 4.2 (5 reviews)
Author: NVIDIA

Nemoclaw Maintainer Day

Run one NemoClaw daytime maintainer pass. Prioritize items for the release version. Select a merge, salvage, security, test, conflict, or sequencing workflow and report progress. Use during the workday to land PRs and close issues. Designed for /loop, for example /loop 10m /nemoclaw-maintainer-day. Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.

NVIDIA Updated Sep 22, 2026 2.2k repo stars

File contents

NemoClaw Maintainer Day

Execute one pass of the maintainer loop, prioritizing version-targeted work.

Autonomy: You may push small fixes after required CI and scheduled automated reviews settle for one unchanged latest PR commit. You may approve a PR when all gates pass. Report contributor and approver overlap as an advisory. It does not change merge readiness or require another reviewer. Never merge. Ask the user about merge, product-scope, and architecture decisions. Also ask when contributor intent is unclear.

Treat the recorded latest PR commit as an optimistic publication guard. Immediately before a push, confirm that the remote branch still points to that commit. Stop when another workflow publishes first.

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 selects the target version. The second lists shipped and open items.

Step 2: Pick One Action

Before reviewing, repairing, approving, integrating, or pushing a PR, complete PR follow-up successfully for one unchanged latest PR commit. This prerequisite does not apply to an item with no PR candidate.

Select the first applicable action for an open item:

PR ready for approval — CI passes, no conflicts remain, and tests cover the change. Confirm that there is no unresolved correctness or security issue. Follow MERGE-GATE.md.
PR that needs a small fix — Follow SALVAGE-PR.md.
Security item — The item touches a risky area. Follow SECURITY-SWEEP.md.
Test gap — Risky code does not have sufficient tests. Follow TEST-GAPS.md.
Repeated conflicts — Follow HOTSPOTS.md.
Work that needs sequencing — The work is too large for one pass. Follow SEQUENCE-WORK.md.

If all items for the release version are blocked, select an item from the backlog.

Prefer to complete a contribution that needs little work before you start a refactor.

Step 3: Execute

Follow the selected workflow. Complete one outcome in each pass:

Approve a PR.
Push a fix.
Add a missing test.
Reduce a source of merge conflicts.
Report a blocker.

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 items for the release version are done, suggest /nemoclaw-maintainer-evening.

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

Commit skill files only when the task changes agent guidance. Do not include unrelated skill changes in code or documentation PRs.

Stop and Ask When

A PR creates a supported product surface without an accepted product decision.
The work requires a refactor or architecture decision.
Contributor intent is unclear and the change can alter behavior.
CI requires changes to multiple subsystems.
A security boundary has an unclear risk.
The next step is to open a PR or merge.

/loop Integration

Use this skill with /loop 10m /nemoclaw-maintainer-day. Keep each pass report short. State what you did, what changed, and what needs a user decision. Read state.json to avoid repeated context.

---name: nemoclaw-maintainer-day-2description: Run one NemoClaw daytime maintainer pass. Prioritize items for the release version. Select a merge, salvage, security, test, conflict, or sequencing workflow and report progress. Use during the workday to land PRs and close issues. Designed for /loop, for example /loop 10m /nemoclaw-maintainer-day. Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.---# NemoClaw Maintainer DayExecute one pass of the maintainer loop, prioritizing version-targeted work.**Autonomy:** You may push small fixes after required CI and scheduled automated reviews settle forone unchanged latest PR commit. You may approve a PR when all gates pass.Report contributor and approver overlap as an advisory. It does not change merge readiness or require another reviewer.Never merge. Ask the user about merge, product-scope, and architecture decisions. Also ask when contributor intent is unclear.Treat the recorded latest PR commit as an optimistic publication guard. Immediately before a push,confirm that the remote branch still points to that commit. Stop when another workflow publishesfirst.## References- PR review priorities: [PR-REVIEW-PRIORITIES.md](PR-REVIEW-PRIORITIES.md)- Risky code areas: [RISKY-AREAS.md](RISKY-AREAS.md)- State schema: [STATE-SCHEMA.md](STATE-SCHEMA.md)## Step 1: Check Version Progress```bashnode --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.tsnode --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>```The first script selects the target version. The second lists shipped and open items.## Step 2: Pick One ActionBefore reviewing, repairing, approving, integrating, or pushing a PR, complete[PR follow-up](../_shared/pr-follow-up.md) successfully for one unchanged latest PR commit. Thisprerequisite does not apply to an item with no PR candidate.Select the first applicable action for an open item:1. **PR ready for approval** — CI passes, no conflicts remain, and tests cover the change. Confirm that there is no unresolved correctness or security issue. Follow [MERGE-GATE.md](MERGE-GATE.md).2. **PR that needs a small fix** — Follow [SALVAGE-PR.md](SALVAGE-PR.md).3. **Security item** — The item touches a risky area. Follow [SECURITY-SWEEP.md](SECURITY-SWEEP.md).4. **Test gap** — Risky code does not have sufficient tests. Follow [TEST-GAPS.md](TEST-GAPS.md).5. **Repeated conflicts** — Follow [HOTSPOTS.md](HOTSPOTS.md).6. **Work that needs sequencing** — The work is too large for one pass. Follow [SEQUENCE-WORK.md](SEQUENCE-WORK.md).If all items for the release version are blocked, select an item from the backlog.Prefer to complete a contribution that needs little work before you start a refactor.## Step 3: ExecuteFollow the selected workflow. Complete one outcome in each pass:- Approve a PR.- Push a fix.- Add a missing test.- Reduce a source of merge conflicts.- Report a blocker.## Step 4: Report ProgressRe-run the progress script and show the update:```bashnode --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-progress.ts <version>```If all items for the release version are done, suggest `/nemoclaw-maintainer-evening`.Update `.nemoclaw-maintainer/state.json` via the state script:```bashnode --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts history <action> <item> "<note>"```## Commit HygieneCommit skill files only when the task changes agent guidance.Do not include unrelated skill changes in code or documentation PRs.## Stop and Ask When- A PR creates a supported product surface without an accepted product decision.- The work requires a refactor or architecture decision.- Contributor intent is unclear and the change can alter behavior.- CI requires changes to multiple subsystems.- A security boundary has an unclear risk.- The next step is to open a PR or merge.## /loop IntegrationUse this skill with `/loop 10m /nemoclaw-maintainer-day`.Keep each pass report short. State what you did, what changed, and what needs a user decision.Read `state.json` to avoid repeated context.

Frequently asked questions