CD nemoclaw-contributor-plan-issue
Plan or divide a named NemoClaw issue into independently useful changes with acceptance evidence. Use for planning requests before implementation.
Plan or divide a named NemoClaw issue into independently useful changes with acceptance evidence.
As a process D 44/100 · Unfinished process — References files that are not bundled: ../_shared/code-change-considerations.md, ../_shared/implementation-discovery.md, ../_shared/code-change-considerations.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
missing-refreference to a missing file: ../_shared/code-change-considerations.md - warning
missing-refreference to a missing file: ../_shared/implementation-discovery.md - warning
missing-refreference to a missing file: ../_shared/code-change-considerations.md - warning
missing-refreference to a missing file: ../../references/e2e-authoring.md - warning
missing-refreference to a missing file: ../_shared/root-cause-and-state-checks.md - warning
missing-refreference to a missing file: ../_shared/security-rubric.md - warning
missing-refreference to a missing file: ../_shared/git-github-hard-stop.md - warning
missing-refreference to a missing file: ../../../AGENTS.md - warning
missing-refreference to a missing file: ../../references/e2e-authoring.md - warning
missing-refreference to a missing file: ../../references/e2e-authoring.md
Process rating: all ten parameters 44/100
- 0Tools and files. 10 referenced file(s) missing: ../_shared/code-change-considerations.md, ../_shared/implementation-discovery.md, ../_shared/code-change-considerations.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 993 tokens
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 146: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 6 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.