nemoclaw-maintainer-e2e

Dispatches and inspects trusted GitHub Actions E2E runs for NemoClaw.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maintainers need a controlled, auditable way to run end-to-end tests against NemoClaw without accidentally exposing credentials, dispatching duplicate runs, or misinterpreting results as release approvals. This Skill routes E2E requests through the trusted GitHub Actions workflow with strict credential boundaries and verification steps.

Core Features & Use Cases

  • Mode-based dispatch: Routes requests to ordinary, focused, Launchable, or full E2E runs on main, or manual PR runs, each with defined selector and credential rules.
  • Release-decision inspection: Read-only inspection of the newest full main run, reporting Release qualification and Staging Brev Launchable job status without deciding whether a release can proceed.
  • Credential and resource boundaries: Documents which secrets each job can access, cleanup obligations, and rotation steps after failures.
  • Use Case: A maintainer asks to run the full E2E suite before tagging a release; the Skill dispatches one correlated workflow run, verifies the tested SHA matches origin/main, and reports job-level results and URLs.

Quick Start

Ask the agent to inspect the newest full E2E run on main and report the Release qualification status and tested commit.

Frequently Asked Questions about nemoclaw-maintainer-e2e

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

FAQPage Schema
How do I run the full E2E suite on NemoClaw main?

Dispatch the e2e.yaml workflow with RUN_MODE=full, which adds the Staging Brev Launchable job to the default suite. Generate one correlation ID, dispatch once, then find the run by its 'E2E full main' title and verify the tested SHA matches origin/main.

How do I run E2E tests against a pull request?

Use the manual PR mode, which keeps the trusted workflow on main and checks out the latest PR commit. NVIDIA-owned PRs can use the full candidate plan, while external PRs are restricted to credential-free controller selections.

Does a successful Release qualification job approve a release tag?

No. The Release qualification aggregate reports the full suite result but does not decide whether a tag can proceed. The release-tag skill owns the general E2E decision and records any exceptional justification.

What credentials does the Staging Brev Launchable job use?

It uses BREV_API_KEY and BREV_ORG_ID for trusted host-side Brev CLI operations, NEMOCLAW_IMAGE_DISPATCH_TOKEN as GH_TOKEN for the image repository, and NVIDIA_INFERENCE_API_KEY exported into the Brev guest. Candidate code in the guest can read the inference key.

What should I do if an E2E run does not appear after dispatch?

Do not dispatch again. Search GitHub Actions for the correlation ID using bounded polling of up to 30 attempts, and clean up resources from any matching run before investigating further.