nemoclaw-maintainer-policies

Provides read-only NemoClaw maintainer policy references for triage, labels, and releases.

22.3k|3.1k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-policies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-policies
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-policies
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-policies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maintainers and triage agents need consistent, authoritative answers about NemoClaw's GitHub workflow—Issue Types, label taxonomy, Project fields, release labels, and triage rules—without inventing labels or statuses that diverge from canonical policy.

Core Features & Use Cases

  • Policy Reference Index: Routes questions to the correct reference file covering workflow policy, triage instructions, label taxonomy, project workflow, daily flow, and release train.
  • Triage Payload Contract: Defines the dry-run JSON shape for issue and PR recommendations, including labels, Project fields, confidence levels, and questions for authors.
  • Label Validation: Ships a machine-readable label-taxonomy.json so agents can validate allowed label values and write policies before suggesting changes.
  • Use Case: A maintainer asks whether an issue should get a daily v0.0.x label; the skill directs the agent to release-train.md, which clarifies that issue labels are tracking signals while merged, labeled PRs own release inclusion.

Quick Start

Ask the agent what labels and Project Status to apply to a new NemoClaw bug report about a macOS onboarding failure.

Frequently Asked Questions about nemoclaw-maintainer-policies

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

FAQPage Schema
How do I triage a NemoClaw GitHub issue with labels?

Classify the issue with native GitHub Issue Type, then add area labels only when the affected surface is clear, plus platform, provider, or integration labels only with direct evidence. Recommend Project Priority and Status separately, and show a dry run before any write.

What labels should a pull request get in NemoClaw?

Apply exactly one PR type label—bug-fix, feature, refactor, or chore—based on evidence, plus area labels for review routing and security when the PR touches credentials, SSRF, or sandbox boundaries. Recommend Project Status Needs Review for conflict-free PRs awaiting maintainer review.

Does a v0.0.x label on an issue include it in the release?

No. Daily version labels on issues are tracking or needs-PR coordination signals only. Release inclusion requires a PR that both carries the daily version label and is merged by the release cutoff.

Can triage agents create new labels in NemoClaw?

Agents may only create, apply, and delete labels inside the agt: * namespace within an authorized agent workflow. Labels absent from the canonical taxonomy must be reported in an audit dry run, never created or applied.

When should I use the needs: info label?

Use needs: info only when the author must supply missing reproduction steps, versions, logs, or platform details before work can proceed. Optional clarifying questions should go in questions_for_author without the label.