AC lora-cad-scanner
LoRa Channel Activity Detection (CAD) scanner for LilyGo T3 v1.6 (ESP32-PICO-D4 + SX1276) with HackRF One support. Scans a configurable frequency range using multiple BW/SF combinations, displays live progress on the SSD1306 OLED, stores detected channels in device RAM, emits structured 15-minute reports over Serial, and sends Telegram notifications for new detections via an OpenClaw cron pipeline. Use when scanning for LoRa devices in a frequency band, setting up a LilyGo T3 as a LoRa scanner/sniffer, building RF monitoring pipelines with Telegram alerting, or doing RF reconnaissance with HackRF + LilyGo together.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-background-processREADME.md:201Starts a background / autostarted process (documentation of a security skill)nohup python3 scripts/lora_monitor.py >> lora_monitor.log 2>&1 &
security skill -
low Dangerous commands
cmd-background-processreferences/setup.md:54Starts a background / autostarted process (documentation of a security skill)nohup python3 lora_monitor.py > lora_monitor.log 2>&1 &
security skill -
low Dangerous commands
cmd-background-processSKILL.md:52Starts a background / autostarted process (documentation of a security skill)nohup python3 scripts/lora_monitor.py > lora_monitor.log 2>&1 &
security skill
Files scanned: 9. 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 53/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1284 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 622: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.