AF jetson-flash-image
Use to flash a promoted BSP image to a Jetson DUT in RCM mode via flash.sh or l4t_initrd_flash.sh. Do NOT use for BSP customization, image promotion, or carrier derivation.
Use to flash a promoted BSP image to a Jetson DUT in RCM mode via flash.sh or l4tinitrdflash.sh. Do NOT use for BSP customization, image promotion, or carrier…
As a process F 57/100 · Will not run — References files that are not bundled: ../../context/target-platform-contract.md, ../../context/bsp-customization-software-layers.md, references/recovery-mode-boardctl.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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../context/target-platform-contract.md - warning
missing-refreference to a missing file: ../../context/bsp-customization-software-layers.md - warning
missing-refreference to a missing file: references/recovery-mode-boardctl.md - warning
missing-refreference to a missing file: ../jetson-promote-image/SKILL.md - warning
missing-refreference to a missing file: ../jetson-promote-image/SKILL.md - warning
missing-refreference to a missing file: references/eeprom-cross-check.md - warning
missing-refreference to a missing file: references/default-user-staging.md - warning
missing-refreference to a missing file: ../jetson-promote-image/references/kernel-image-and-initramfs.md - warning
missing-refreference to a missing file: ../../context/bsp-customization-workflow.md - warning
missing-refreference to a missing file: ../jetson-promote-image/SKILL.md - warning
missing-refreference to a missing file: ../jetson-derive-carrier/SKILL.md
Process rating: all ten parameters 57/100
- 0Tools and files. 11 referenced file(s) missing: ../../context/target-platform-contract.md, ../../context/bsp-customization-software-layers.md, references/recovery-mode-boardctl.md
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4829 tokens
- 85Steps. 38 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (10 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 172: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.