CD nemoclaw-maintainer-day
Run a NemoClaw daytime maintainer pass over release-targeted work. Use for the maintainer queue or a requested recurring pass.
Run a NemoClaw daytime maintainer pass over release-targeted work.
As a process D 42/100 · Unfinished process — References files that are not bundled: ../_shared/pr-follow-up.md
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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-tokenscripts/triage.ts:332High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)... on Proj…lue {quoted
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../_shared/pr-follow-up.md - note
frontmatter-keyunknown frontmatter key "user_invocable"
Process rating: all ten parameters 42/100
Will not run. References files that are not bundled: ../_shared/pr-follow-up.md
- 0Tools and files. 1 referenced file(s) missing: ../_shared/pr-follow-up.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 12 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 982 tokens
- 100Progress reporting. Reports progress
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- -36 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.