AC lygo-lora-mesh
LYGO LoRa mesh — compact Layer D roots pulse on stock Meshtastic. IP up = living-mesh HTTP; IP down = LY1 text packet ≤200 bytes. No board = NAMED_SHADOW. Scripts encode/decode/compare only: no network, no subprocess, no serial driver, no firmware fork. Use when the user wants Meshtastic, LoRa, off-grid mesh, RF gossip, or /lygo-lora-mesh.
LYGO LoRa mesh — compact Layer D roots pulse on stock Meshtastic.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenexamples/demo_badge.json:2High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)"signature": "Delt…-v1",
detectorfixture
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 706 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
- +2Single-language instructions
- +3Description length 341: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.