mcpbeat

Nemoclaw Maintainer Morning

nvidia/nemoclaw-maintainer-morning

Runs the morning maintainer standup for NemoClaw. Triages the backlog, determines the day's target version, labels selected items, surfaces stragglers from previous versions, and outputs the daily plan. Use at the start of the workday. Trigger keywords - morning, standup, start of day, daily plan, what are we shipping today.

837 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
22044
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-morning

The instruction itself

6 sections, as written by the author

NemoClaw Maintainer Morning

Start the day: triage, pick a version target, label items, share the plan.

See PR-REVIEW-PRIORITIES.md for the daily cadence and review priorities.

Step 1: Determine Target Version and Stragglers

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/version-target.ts

This fetches tags, computes the next patch version, and finds open items still carrying older version labels. Surface stragglers first — they indicate post-tag housekeeping was interrupted or an item slipped across multiple cycles. Decide whether to relabel them to today's target or defer them out of the daily release flow.

Step 2: Triage

Run the triage script to rank the full backlog:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts --approved-only

If too few results, run without --approved-only. The script fetches open PRs through gh, reads Project 199 Priority, enriches candidates with review, CI, file, and risky-area data, and applies the scoring model documented in PR-REVIEW-PRIORITIES.md.

Also use find-review-pr to surface security PRs whose Project Priority is Urgent or High. Merge these into the candidate pool.

Step 3: Label Version Targets

Present the ranked queue to the user. After they confirm which items to target, label them:

gh label create "<version>" --repo NVIDIA/NemoClaw --description "Release target" --color "1d76db" 2>/dev/null || true
gh pr edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"
gh issue edit <number> --repo NVIDIA/NemoClaw --add-label "<version>"

Step 4: Save State and Output the Plan

Pipe triage output into state:

node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/triage.ts \
  | node --experimental-strip-types --no-warnings .agents/skills/nemoclaw-maintainer-day/scripts/state.ts set-queue

Output the daily plan:

| Target | Item | Type | Owner | Next action |

|--------|------|------|-------|-------------|

| v0.0.8 | #1234 | PR | @author | Run merge gate |

| v0.0.8 | #1235 | Issue | unassigned | Needs PR |

Include: total items targeted, how many are PRs vs issues, how many are already merge-ready.

Notes

  • This skill runs once at the start of the day. Use /nemoclaw-maintainer-day during the day to execute.
  • On a PR, the target version label activates daily release work; actual release inclusion requires that PR to be merged with the label at cutoff.
  • On an issue, the target version label is tracking or "needs PR" coordination only.
  • Stragglers from previous versions should be addressed first — they already slipped once.

How to use it

Copy the folder

Take nvidia/nemoclaw-maintainer-morning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.