CD nemoclaw-maintainer-verify-stale
Reproduce stale NemoClaw bug reports on the reported and newest releases, then propose evidence-backed triage. Never auto-closes issues.
Reproduce stale NemoClaw bug reports on the reported and newest releases, then propose evidence-backed triage.
As a process D 41/100 · Unfinished process — References files that are not bundled: ../_shared/documentation-writing-review.md
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreference/candidate-selection.md:57High-entropy token-like string (may be an id, hash or a credential)... on Proj…lue {
Files scanned: 8. 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: ../_shared/documentation-writing-review.md - note
frontmatter-keyunknown frontmatter key "user_invocable" - note
edit-residuethe text marks something as outdated (lines 16): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 41/100
Will not run. References files that are not bundled: ../_shared/documentation-writing-review.md
- 0Tools and files. 1 referenced file(s) missing: ../_shared/documentation-writing-review.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 18 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1322 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 136: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 18 items
- +4Reference files are cited in the instructions (6 of 6)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.