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.