nemoclaw-maintainer-triage

Automate GitHub label triage for NVIDIA/NemoClaw issues and pull requests.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-triage-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-triage
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-maintainer-triage
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-maintainer-triage-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintainers quickly and consistently label NVIDIA/NemoClaw issues and PRs by generating label suggestions and an optional triage comment based on up-to-date instructions.

Core Features & Use Cases

  • Instruction-driven label guidance: Reads the single source of truth from references/triage-instructions.md at runtime so label choices follow the latest guide and formatting rules.
  • Single-item and batch triage: Supports triaging one specified issue/PR number or iterating through up to 50 unlabeled open items in a controlled approval workflow.
  • Approval-based GitHub actions with logging: Applies suggested labels and posts a triage comment via the GitHub CLI only after user approval, then logs each approved decision to the daily-rhythm activity folder.

Quick Start

Ask the AI to batch-triage up to 50 unlabeled open NemoClaw issues and PRs, present each suggestion for approval, apply labels when approved, and log the session results.

Frequently Asked Questions about nemoclaw-maintainer-triage

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

FAQPage Schema
How do I automate GitHub issue and pull request triage for consistent labeling?

Batch triaging GitHub issues and pull requests uses an AI workflow that fetches up to 50 unlabeled open items, generates label suggestions from a live instruction guide, and applies changes via GitHub CLI only after user approval. It logs each session to maintain triage consistency.

What is the best way to apply consistent labels to multiple unlabeled GitHub issues at once?

Batch labeling unlabeled GitHub issues is handled by iterating through up to 50 open items, generating labels and triage comments based on a live instruction guide, and applying GitHub CLI label edits only after explicit user approval to maintain consistency.

Does AI-assisted GitHub label triage require manual approval before applying changes?

Yes, AI-assisted GitHub label triage requires explicit user approval before applying changes. The workflow generates suggestions and triage comments, waits for user confirmation, then uses GitHub CLI to apply labels and posts comments while logging each decision.

How do I keep AI-generated triage comments aligned with the latest GitHub labeling instructions?

Keeping AI-generated triage comments aligned with the latest GitHub labeling instructions is achieved by loading triage-instructions.md at runtime, ensuring the AI generates labels and comments that strictly follow the most current formatting rules and guidance.

Can I triage a single GitHub pull request instead of running a full batch workflow?

Yes, you can triage a single GitHub pull request by specifying its number. The workflow supports single-item processing to generate labels and triage comments, apply changes via GitHub CLI after approval, and log the session alongside batch capabilities for up to 50 items.

What are the limitations of using an approval-based workflow for GitHub issue labeling?

The approval-based workflow limits throughput by requiring manual confirmation for each item before applying labels via GitHub CLI. It processes up to 50 unlabeled open items per session and relies on runtime loading of triage-instructions.md to generate accurate label suggestions.