nemoclaw-maintainer-classify-ci-failure

Classify one NemoClaw GitHub Actions job failure from bounded, redacted logs and an optional retained artifact. Use for CI failure classification, failed job diagnosis, or artifact-backed failure evidence.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, action-first skill body that leads with an executable command and surrounds it with relevant safety/operational constraints, including validation hard-stops. It uses a single well-signaled bundle reference rather than inlining the script's internals.

Suggestions

Break the long security/cleanup prose paragraph into a short bulleted list so the subprocess-boundary and signal-handling rules are scannable rather than embedded in narrative.

Add one or two example invocations showing artifact selection (--artifact-name) and --max-lines/--clip-mode so the common variants are as copy-paste ready as the default.

Surface the success-JSON output shape (and the 'unclassified = bounded evidence, not proof' note) as a short explicit step so the run -> classify -> report feedback loop reads as a checklist.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely earns its tokens on operationally necessary safety detail (subprocess boundary, path validation, signal handling) rather than concepts Claude already knows; a few long sentences could be tightened but it is mostly efficient.	4 / 5
Actionability	It opens with a concrete, copy-paste-ready 'node --experimental-strip-types ...' invocation plus documented flags and defaults, giving mostly executable guidance; it stops short of per-variant examples that would warrant a 5.	4 / 5
Workflow Clarity	The run-to-result sequence is clear and includes explicit validation/hard-stop checkpoints (nonzero log acquisition is a failure, cleanup failure exits nonzero, auth failure triggers a hard stop with retry guidance); minor gaps keep it just below a fully detailed feedback-loop checklist.	4 / 5
Progressive Disclosure	The body is an overview that points to one bundle script via a clearly signaled path in the code block, with a single one-level-deep reference and no nested indirection; minor organization gaps (a prose-heavy single section) keep it from a 5.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states a concrete capability and provides an explicit 'Use for ...' trigger clause with multiple natural phrases. It is specific, complete, and clearly distinct from sibling skills.

Dimension	Reasoning	Score
Specificity	Names the NemoClaw GitHub Actions domain and concrete elements ('classify one ... job failure from bounded, redacted logs and an optional retained artifact'), listing several specific actions rather than generic language; just short of the comprehensive multi-action score-5 example.	4 / 5
Completeness	Explicitly answers both what ('Classify one NemoClaw GitHub Actions job failure from bounded, redacted logs and an optional retained artifact') and when ('Use for CI failure classification, failed job diagnosis, or artifact-backed failure evidence') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are present ('CI failure classification', 'failed job diagnosis', 'artifact-backed failure evidence') with good synonym coverage, though it omits a few common variations a user might actually say.	4 / 5
Distinctiveness Conflict Risk	The NemoClaw-specific, bounded/redacted-log CI failure classification niche is tightly scoped with distinct triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NVIDIA/NemoClaw
Path: .agents/skills/nemoclaw-maintainer-classify-ci-failure/SKILL.md
Commit: e94c06f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.