Official agent skill

Nemoclaw Maintainer Triage

by NVIDIA in NVIDIA/NemoClaw

Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.

OfficialApache-2.0Auto-check passed

Install Nemoclaw Maintainer Triage

skills CLI
$ npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-maintainer-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NemoClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nemoclaw-maintainer-triage .claude/skills/nemoclaw-maintainer-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nemoclaw-maintainer-triage
GitHub stars
23k
Token cost
~1.2k tokens
SKILL.md length
490 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.

  • Works in 5 steps: Load Canonical Policy → Determine Mode → Present the Dry Run → …
  • SKILL.md covers Step 1: Load Canonical Policy, Step 2: Determine Mode, Step 3: Present the Dry Run and Step 4: Apply Only the…, plus 2 more sections
  • Calls gh

What it does

Nemoclaw Maintainer Triage is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Run agents like Hermes, LangChain Deep Agents, and OpenClaw more securely inside NVIDIA OpenShell with managed inference. The licence is Apache-2.0.

Example prompts

  • “/nemoclaw-maintainer-triage”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Load Canonical Policy
  2. Determine Mode
  3. Present the Dry Run
  4. Apply Only the Accepted Write Set
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit fcbbab0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nemoclaw Maintainer Triage loads about 1.2k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 490 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/NemoClaw at commit fcbbab0, republished under its Apache-2.0 licence (© NVIDIA). 490 words, ~1,154 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-maintainer-triage/SKILL.md (or your agent's skills folder).
name
nemoclaw-maintainer-triage
description
Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.
user_invocable
true
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->

NemoClaw Maintainer — Triage

Use Issue Type for issue classification. Use Project fields for priority and lifecycle. Use labels for routing and action queues.

Step 1: Load Canonical Policy

Before evaluating an item, read these files in order:

  1. workflow-policy.md
  2. triage-instructions.md
  3. label-taxonomy.json
  4. examples.md

Do not use another label guide. The policy package is the source of truth for Issue Type, Project fields, labels, confidence, authorization, and output shape.

Step 2: Determine Mode

Single-item mode — the user provides an issue or PR number:

bash
gh issue view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author,projectItems
gh pr view <number> --repo NVIDIA/NemoClaw --json number,title,body,labels,url,author,files,isDraft,mergeStateStatus,projectItems,statusCheckRollup

Use the command for the item type. For issues, read Issue Type through the GitHub GraphQL API. Read Project Priority and Status from Project 199. Do not infer them from labels.

Batch mode — collect both normal inbox items and unlabeled items:

bash
gh issue list --repo NVIDIA/NemoClaw --state open --label "needs: triage" --limit 50 --json number,title,body,labels,url,author
gh issue list --repo NVIDIA/NemoClaw --state open --limit 50 --json number,title,body,labels,url,author
gh pr list --repo NVIDIA/NemoClaw --state open --label "needs: triage" --limit 50 --json number,title,body,labels,url,author,isDraft,mergeStateStatus
gh pr list --repo NVIDIA/NemoClaw --state open --limit 50 --json number,title,body,labels,url,author,isDraft,mergeStateStatus

Keep unlabeled items from the unfiltered results. Combine them with the needs: triage results. Remove duplicates by item type and number. Process one item at a time.

Step 3: Present the Dry Run

Use the JSON-compatible payload defined by canonical triage-instructions.md. Include:

  • native Issue Type for issues
  • Project Priority and Status recommendations
  • only labels from label-taxonomy.json
  • labels to remove, including a completed needs: triage inbox marker
  • confidence, rationale, questions, and human_review_required
  • the proposed public comment, when one is useful.

Prefer no label over a guessed label. Do not use labels for Issue Type, Priority, Status, or resolution. Do not propose an unknown label. Do not propose PRR during triage.

In batch mode, present each dry run and wait for an explicit apply, skip, or edited write set before moving to the next item.

Show full SKILL.md (232 more words)Show less

Step 4: Apply Only the Accepted Write Set

Acceptance authorizes only the fields, labels, and comment in the proposal. Before each write, re-read Issue Type, Project fields, and labels, then resolve all live IDs. Do not store mutable IDs in this skill. If the state differs from the accepted proposal's base state, stop and present an updated proposal for acceptance. Resume writes only after the user accepts the updated proposal.

Apply writes in this order:

  1. Set native Issue Type and accepted Project fields.
  2. Add and remove canonical labels.
  3. Remove needs: triage when the inbox action is complete.
  4. Post the accepted comment, if any.

Do not write if the accepted plan contains a low-confidence inference, an unknown label, or an unauthorized field. Return a corrected proposal.

Step 5: Report

For every applied item, report:

  • Issue Type before and after, when applicable
  • Project Priority and Status before and after
  • labels added and removed
  • whether a comment was posted
  • any proposed write that was skipped and why.

Do not write an external activity log unless the invoking maintainer explicitly asks for one.

Batch Ordering

Prioritize candidates using policy evidence, not labels that duplicate Project Priority:

  1. Security, outage, or data-loss reports that might need Project Priority Urgent or High.
  2. Items that need a response from an author or maintainer.
  3. Items waiting longest for triage.
  4. Remaining items by recency.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/nemoclaw-maintainer-triage of NVIDIA/NemoClaw.

Open the folder on GitHubat commit fcbbab0

Compare with similar skills

Nemoclaw Maintainer Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nemoclaw Maintainer Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Maintainer Triage this skillNVIDIA/NemoClaw23k—~1.2kAutomated safety check: PassApache-2.0
Maintainer Triageredis/node-redis18k—~1.9kAutomated safety check: PassMIT
.NET MAUI Issue Label Triagedotnet/maui23k—~9.8kAutomated safety check: PassMIT
Form Field Multiple Labelsthedaviddias/Front-End-Checklist74k—~450Automated safety check: PassMIT
Ouroboros Maintainer TriageQ00/ouroboros6.2k—~1.7kAutomated safety check: PassMIT
Triaging Issuespytorch/pytorch104k—~4.2kAutomated safety check: PassCustom licence

Similar skills

  • Maintainer Triage

    redis/node-redis

    Official

    Batch-triage and act on a set of node-redis PRs (or issues) by filter — fan out the maintainer-review methodology across them, present a one-word verdict plus a tldr to the user one at a time for…

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Official

    Applies the full manual-label policy of the dotnet/maui issue triage command, judging type, area, platform, status, regression and priority against the evidence in each issue.

    23k GitHub stars~9.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Form Field Multiple Labels

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use a single label for each form field.

    74k GitHub stars~450 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed
  • Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Triaging Issues

    pytorch/pytorch

    Triages GitHub issues by routing to oncall teams, applying labels, and closing questions.

    104k GitHub stars~4.2k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Maintainer Triage

    mohitagw15856/pm-claude-skills

    Get an open-source repo's issue backlog from 400-and-drowning to triaged-and-honest in one pass — a label taxonomy that encodes decisions, batch triage rules you can apply in seconds per issue…

    1.4k GitHub stars~1.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from NVIDIA/NemoClaw

All 30 skills in this repo
  • Official

    Find open issues that a NemoClaw PR may also fix or conflict with.

    23k GitHub stars~893 tokensUpdated today
    Auto-check passed
  • Official

    Run a NemoClaw daytime maintainer pass over release-targeted work.

    23k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.

    23k GitHub stars~644 tokensUpdated today
    Auto-check passed

Questions about Nemoclaw Maintainer Triage

What does Nemoclaw Maintainer Triage do?

Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch. Nemoclaw Maintainer Triage is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.

How do I install Nemoclaw Maintainer Triage in Claude Code?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-triage -a claude-code`. Or copy the skill folder (.agents/skills/nemoclaw-maintainer-triage in NVIDIA/NemoClaw) into .claude/skills/nemoclaw-maintainer-triage in your project. Claude Code loads it when a task matches its description.

How do I install Nemoclaw Maintainer Triage in Codex?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-triage -a codex`. Or copy the skill folder (.agents/skills/nemoclaw-maintainer-triage in NVIDIA/NemoClaw) into .agents/skills/nemoclaw-maintainer-triage in your project. Codex loads it when a task matches its description.

Can I use Nemoclaw Maintainer Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemoclaw-maintainer-triage, .gemini/skills/nemoclaw-maintainer-triage, .github/skills/nemoclaw-maintainer-triage and .opencode/skills/nemoclaw-maintainer-triage in your project.

What does Nemoclaw Maintainer Triage need to run?

Going by SKILL.md and its folder, Nemoclaw Maintainer Triage needs the command-line tools its instructions call (gh).

Does Nemoclaw Maintainer Triage access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nemoclaw Maintainer Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nemoclaw Maintainer Triage use?

Nemoclaw Maintainer Triage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemoclaw Maintainer Triage use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemoclaw Maintainer Triage?

Skills that share tags, products or a category with Nemoclaw Maintainer Triage: Maintainer Triage (redis/node-redis, 18k stars), .NET MAUI Issue Label Triage (dotnet/maui, 23k stars), Form Field Multiple Labels (thedaviddias/Front-End-Checklist, 74k stars) and Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Maintainer Triage?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NemoClaw, which has 22,692 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 10, 2026.

Source: NVIDIA/NemoClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.