BD nemoclaw-maintainer-refactor-docs
Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes. Use for structural documentation refactors.
Reorganize NemoClaw documentation pages, navigation, or content ownership while preserving published routes.
As a process D 42/100 · Unfinished process — References files that are not bundled: ../_shared/documentation-writing-review.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../_shared/documentation-writing-review.md - note
edit-residuethe text marks something as outdated (lines 54, 68): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 42/100
- 0Tools and files. 1 referenced file(s) missing: ../_shared/documentation-writing-review.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. 7 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1042 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 31 items
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.