BF jetson-link-docs
Bind pre-downloaded Jetson reference docs (developer guide, design guide, pinmux, schematics) into the active profile documents block. Use after staging docs on disk; not for downloading.
Bind pre-downloaded Jetson reference docs (developer guide, design guide, pinmux, schematics) into the active profile documents block.
As a process F 49/100 · Will not run — References files that are not bundled: ../../context/target-platform-contract.md, ../../references/platform_template.yaml, ../../references/bsp-platforms-catalogue.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: ../../references/platform_template.yaml - warning
missing-refreference to a missing file: ../../references/bsp-platforms-catalogue.md - warning
missing-refreference to a missing file: ../jetson-init-target/SKILL.md - warning
missing-refreference to a missing file: ../jetson-init-image/SKILL.md - warning
missing-refreference to a missing file: ../jetson-init-source/SKILL.md - warning
missing-refreference to a missing file: ../jetson-generate-kb/SKILL.md
Process rating: all ten parameters 49/100
- 0Tools and files. 7 referenced file(s) missing: ../../context/target-platform-contract.md, ../../references/platform_template.yaml, ../../references/bsp-platforms-catalogue.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 36 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3225 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (18 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
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 187: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 36 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.