New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Nemoclaw Maintainer Classify CI Failure

by NVIDIA in NVIDIA/NemoClaw

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

OfficialApache-2.0Auto-check passedTesting & QA

Install Nemoclaw Maintainer Classify CI Failure

skills CLI
$ npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-classify-ci-failure -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NemoClaw nemoclaw-maintainer-classify-ci-failure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NemoClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nemoclaw-maintainer-classify-ci-failure .claude/skills/nemoclaw-maintainer-classify-ci-failure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nemoclaw-maintainer-classify-ci-failure
GitHub stars
23k
Token cost
~806 tokens
SKILL.md length
389 words
Files
3 (incl. scripts)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Tasks that involve Failing and flaky tests
  • Runs TypeScript scripts from its folder; calls node
  • Tasks that involve CI/CD

What it does

Nemoclaw Maintainer Classify CI Failure is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml`).

It sits in Testing & QA, covering Failing and flaky tests and CI/CD. It works with NVIDIA AI Platform and GitHub Actions. The repository describes itself as: Run agents like Hermes, LangChain Deep Agents, and OpenClaw more securely inside NVIDIA OpenShell with managed inference. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Failing and flaky tests
  • Tasks that involve CI/CD

Example prompts

  • “/nemoclaw-maintainer-classify-ci-failure”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit fcbbab0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nemoclaw Maintainer Classify CI Failure loads about 806 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~806

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/NemoClaw at commit fcbbab0, republished under its Apache-2.0 licence (© NVIDIA). 389 words, ~806 tokens.

Download SKILL.mdSave it as .claude/skills/nemoclaw-maintainer-classify-ci-failure/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
nemoclaw-maintainer-classify-ci-failure
description
Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.
user_invocable
true
<!-- 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:

bash
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.

Show full SKILL.md (99 more words)Show less

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.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .agents/skills/nemoclaw-maintainer-classify-ci-failure of NVIDIA/NemoClaw.

  • SKILL.md
  • agents/openai.yaml
  • scripts/classify-ci-failure.mts

Open the folder on GitHubat commit fcbbab0

Compare with similar skills

Nemoclaw Maintainer Classify CI Failure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nemoclaw Maintainer Classify CI Failure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemoclaw Maintainer Classify CI Failure this skillNVIDIA/NemoClaw23k—~806Automated safety check: PassApache-2.0
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
CI Triagecanton-network/splice117—~1.4kAutomated safety check: PassApache-2.0
Babysit PRZenUml/web-sequence150—~871Automated safety check: PassMIT
Instructor QAcognesy/instructor-php328—~1.3kAutomated safety check: PassMIT

Similar skills

  • Megatron-LM CI Failure Triage

    NVIDIA/Megatron-LM

    Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • GreptimeDB Fuzz CI Failure Investigation

    GreptimeTeam/greptimedb

    Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

  • CI Triage

    canton-network/splice

    Triage a failed splice GitHub Actions job (cn-test-failures ref) into a reproducible evidence packet - fetch job log and artifact, isolate the flagged lines, check the known flake families for…

    117 GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Babysit PR

    ZenUml/web-sequence

    Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.

    150 GitHub stars~871 tokensUpdated 5 days ago
    Testing & QAAuto-check passed

  • Instructor QA

    cognesy/instructor-php

    Run multi-dimensional quality assurance for InstructorPHP. An agent skill from cognesy/instructor-php.

    328 GitHub stars~1.3k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Analysing CI Failures

    golemcloud/golem

    Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.

    1.5k GitHub stars~862 tokensUpdated today
    Testing & QAAuto-check passed

More from NVIDIA/NemoClaw

All 30 skills in this repo

  • Nemoclaw Maintainer Cross Issue Sweep

    NVIDIA/NemoClaw

    Official

    Find open issues that a NemoClaw PR may also fix or conflict with.

    23k GitHub stars~893 tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Day

    NVIDIA/NemoClaw

    Official

    Run a NemoClaw daytime maintainer pass over release-targeted work.

    23k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemoclaw Contributor Update Dependencies

    NVIDIA/NemoClaw

    Official

    Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Fix E2E Failures

    NVIDIA/NemoClaw

    Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Nemoclaw Maintainer Analyze CI Performance

    NVIDIA/NemoClaw

    Official

    Analyze retained NemoClaw CI timings for slow CLI tests, runner queues, or base-image publication.

    23k GitHub stars~644 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Nemoclaw Maintainer Classify CI Failure

What does Nemoclaw Maintainer Classify CI Failure do?

Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts. Nemoclaw Maintainer Classify CI Failure is an agent skill from NVIDIA/NemoClaw, published by the product's own GitHub organization. Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.

When should I use Nemoclaw Maintainer Classify CI Failure?

Nemoclaw Maintainer Classify CI Failure fits situations like: tasks that involve Failing and flaky tests; tasks that involve CI/CD.

How do I install Nemoclaw Maintainer Classify CI Failure in Claude Code?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-classify-ci-failure -a claude-code`. Or copy the skill folder (.agents/skills/nemoclaw-maintainer-classify-ci-failure in NVIDIA/NemoClaw) into .claude/skills/nemoclaw-maintainer-classify-ci-failure in your project. Claude Code loads it when a task matches its description.

How do I install Nemoclaw Maintainer Classify CI Failure in Codex?

Run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-classify-ci-failure -a codex`. Or copy the skill folder (.agents/skills/nemoclaw-maintainer-classify-ci-failure in NVIDIA/NemoClaw) into .agents/skills/nemoclaw-maintainer-classify-ci-failure in your project. Codex loads it when a task matches its description.

Can I use Nemoclaw Maintainer Classify CI Failure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NemoClaw --skill nemoclaw-maintainer-classify-ci-failure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemoclaw-maintainer-classify-ci-failure, .gemini/skills/nemoclaw-maintainer-classify-ci-failure, .github/skills/nemoclaw-maintainer-classify-ci-failure and .opencode/skills/nemoclaw-maintainer-classify-ci-failure in your project.

What does Nemoclaw Maintainer Classify CI Failure need to run?

Going by SKILL.md and its folder, Nemoclaw Maintainer Classify CI Failure needs TypeScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Nemoclaw Maintainer Classify CI Failure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nemoclaw Maintainer Classify CI Failure safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nemoclaw Maintainer Classify CI Failure use?

Nemoclaw Maintainer Classify CI Failure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemoclaw Maintainer Classify CI Failure use?

About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemoclaw Maintainer Classify CI Failure?

Skills that share tags, products or a category with Nemoclaw Maintainer Classify CI Failure: Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars), GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), CI Triage (canton-network/splice, 117 stars) and Babysit PR (ZenUml/web-sequence, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemoclaw Maintainer Classify CI Failure?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NemoClaw, which has 22,692 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 10, 2026.

Source: NVIDIA/NemoClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.