Skip to content
cccskills
FreePublished on GitHub

nemoclaw-maintainer-classify-ci-failure

Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.

OriginalShow the original description

Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.

Works withGitHub
See how to install

Good for

  • Classifying a failed GitHub Actions job
  • Inspecting saved artifacts for failure evidence
  • Gathering initial evidence for an E2E failure

Files included (3)

  • SKILL.md3.1 KB
  • agents/openai.yaml390 B
  • scripts/classify-ci-failure.mts47.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->

Classify a CI Failure

When the failed job is part of E2E, first load Audit E2E Assertions. This classifier can locate the failure signature. Its bounded output does not replace the complete log review and itemized source audit required before an E2E repair push or expensive rerun.

Run the classifier from a NemoClaw checkout:

node --no-warnings \
  .agents/skills/nemoclaw-maintainer-classify-ci-failure/scripts/classify-ci-failure.mts \
  --workdir "$PWD" --job-id <job-id>

The repository is fixed to NVIDIA/NemoClaw. Optional flags include --artifact-name. --max-lines accepts integers from 1 through 500 and defaults to 120. --clip-mode accepts head or tail and defaults to tail.

The script uses authenticated gh reads. It performs no GitHub writes. It bounds and redacts log output. When an artifact is selected, it bounds pagination, compressed and expanded sizes, entries, paths, file reads, and reported failures. It rejects malformed ZIPs, links, special files, duplicate or unsafe paths, ambiguous listings, and size mismatches. Temporary files use process-owned directories under a fixed private root. The classifier attempts to remove them directly through the filesystem after success or failure. If removal fails, the classifier exits nonzero. It reports a bounded, redacted diagnostic with a direct removal command. Each command runs beneath a stable detached group leader that stays alive until every group descendant exits. This is an internal trusted-subprocess boundary: the classifier invokes Bash and GNU coreutils by fixed paths. It finds gh only in /usr/bin, /usr/local/bin, or $HOME/.local/bin after it validates the path, ownership, permissions, and file type. It treats artifacts as data and never executes artifact content or caller-selected programs. On SIGHUP, SIGINT, or SIGTERM, the classifier rejects new commands, terminates and drains every owned group, synchronously removes tracked directories, and exits with the conventional cancellation code. If normal cleanup fails, it reports a bounded, redacted error and a removal command that remains valid if TMPDIR changes.

Run the script from a Linux NemoClaw checkout with Node.js 22.19 or later, /proc, Bash, authenticated gh in a trusted location, and GNU coreutils (dd, stat, tail, and wc).

Any nonzero log acquisition result is a classifier failure. After the cleanup attempt, the script exits nonzero with no success JSON and reports a bounded, redacted diagnostic. On GitHub authentication or authorization failure, stop, follow the repository GitHub access hard stop, and ask the user to correct the configured gh access (including SSO or token scope) before rerunning. Treat unclassified as bounded evidence, not proof that no known cause exists.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.

  • Publishing implemented changes as a pull request
  • Updating an open pull request after review feedback
  • Tracking automated checks and reviews on the latest commit
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.

  • Implement an accepted issue within its agreed scope
  • Repair a classified pull request finding
  • Validate failure, recovery, and cleanup behavior
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.

  • Setting up a local NemoClaw development environment
  • Checking readiness before starting development
  • Repairing local dependency, build, or hook problems
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.

  • Plan implementation for a named issue
  • Divide a large change into useful steps
  • Define acceptance criteria and test evidence
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.

  • Assess the impact of a dependency upgrade
  • Plan migrations for a Hermes upgrade
  • Verify base images and selected artifacts
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

Update NemoClaw documentation after merged changes or audit it for outdated guidance. Verify current behavior against source and tests, edit the pages responsible for that guidance, and check affected links and generated variants.

  • Catch up documentation after merged changes
  • Audit documentation for outdated guidance
  • Update guides for changed user behavior
NVIDIA/NemoClaw22.8KUpdated Oct 22, 2026

See all skills by NVIDIA

Report a problem with this skill