nemoclaw-maintainer-triage

Triages NemoClaw GitHub issues and PRs with canonical labels, Issue Types, and Project fields.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-triage-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-triage
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-triage
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-triage-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of the NemoClaw repository face a growing inbox of untriaged issues and pull requests, and inconsistent labeling makes routing and prioritization unreliable. This Skill applies the repository's canonical triage policy to classify items, propose labels and Project fields, and apply only the changes a maintainer explicitly accepts. ## Core Features & Use Cases - Policy-driven triage: Loads the canonical workflow policy, triage instructions, label taxonomy, and examples from the nemoclaw-maintainer-policies reference package before evaluating any item. - Single-item and batch modes: Triages one issue or PR by number, or processes the full needs: triage inbox plus unlabeled items one at a time. - Dry-run approval workflow: Presents proposed Issue Type, Project Priority/Status, label additions and removals, confidence, and an optional comment, then applies only the accepted write set after re-reading live state. - Use Case: A maintainer asks to triage issue #142. The Skill fetches the issue via the GitHub CLI, proposes an Issue Type, Priority, and routing labels from the taxonomy, waits for approval, applies the changes, removes the needs: triage marker, and reports before-and-after state. ## Quick Start Ask the agent to triage issue number 142 in the NVIDIA/NemoClaw repository and show the proposed labels before applying them.

Frequently Asked Questions about nemoclaw-maintainer-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a GitHub issue with this Skill?

Provide an issue or PR number and the Skill fetches it with the GitHub CLI, loads the canonical triage policy, and presents a dry-run proposal with Issue Type, Project fields, and labels. It applies changes only after you explicitly accept the proposal.

How does batch triage of the needs: triage inbox work?

Batch mode collects open issues and PRs labeled needs: triage plus unlabeled items, deduplicates them, and processes one item at a time. Each item gets its own dry run, and the Skill waits for an apply, skip, or edited write set before moving on.

Can the Skill apply labels without maintainer approval?

No. The Skill always presents a dry-run proposal first and applies only the exact write set the maintainer accepts. It also refuses to write when the plan contains a low-confidence inference, an unknown label, or an unauthorized field.

Does it support labels outside the NemoClaw label taxonomy?

No. Only labels defined in the canonical label-taxonomy.json from the nemoclaw-maintainer-policies package may be proposed. The Skill prefers no label over a guessed one and never proposes unknown labels or PRR during triage.

What happens if an issue changes between proposal and approval?

Before each write, the Skill re-reads the item's Issue Type, Project fields, and labels. If the live state differs from the accepted proposal's base state, it stops and presents an updated proposal for a fresh acceptance.