CF nemoclaw-maintainer-classify-ci-failure
Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.
Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.
As a process F 20/100 · No process to follow — References files that are not bundled: ../nemoclaw-maintainer-audit-e2e-assertions/SKILL.md
ReferenceGitHubSoftware developmentData and analyticsAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../nemoclaw-maintainer-audit-e2e-assertions/SKILL.md - note
frontmatter-keyunknown frontmatter key "user_invocable"
Process rating: all ten parameters 20/100
Will not run. References files that are not bundled: ../nemoclaw-maintainer-audit-e2e-assertions/SKILL.md
- 0Tools and files. 1 referenced file(s) missing: ../nemoclaw-maintainer-audit-e2e-assertions/SKILL.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 756 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 109: 120–800 characters recommended
- +4Structure: 1 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.