AF hsb-ip-packetizer
Choose or explain HSB Sensor RX packetizer fields for HOLOLINK_def.svh. Do not use for full defs, validation, or runtime APB programming.
Choose or explain HSB Sensor RX packetizer fields for HOLOLINKdef.svh. Do not use for full defs, validation, or runtime APB programming.
As a process F 59/100 · Will not run — References files that are not bundled: references/handoff-contract.md, references/packetizer-def-fields.md, references/packetizer-architecture.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: references/handoff-contract.md - warning
missing-refreference to a missing file: references/packetizer-def-fields.md - warning
missing-refreference to a missing file: references/packetizer-architecture.md
Process rating: all ten parameters 59/100
- 0Tools and files. 3 referenced file(s) missing: references/handoff-contract.md, references/packetizer-def-fields.md, references/packetizer-architecture.md
- 0Result 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
- 100Steps. 78 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3374 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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 137: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.