BF esp32-development
Build, configure, flash, test, debug, and recover firmware for ESP32-family boards, including ESP-IDF C/C++, Arduino/PlatformIO, MicroPython, CircuitPython, ESPHome, Zephyr, Rust, and NuttX. Use when identifying an ESP32 board, choosing a framework, wiring GPIO or peripheral buses, integrating sensors or actuators, diagnosing serial/boot/power/network failures, or planning OTA and production security. Do not use as a substitute for the exact board schematic, SoC datasheet, or attached component datasheet.
Build, configure, flash, test, debug, and recover firmware for ESP32-family boards, including ESP-IDF C/C++, Arduino/PlatformIO, MicroPython, CircuitPython…
As a process F 43/100 · Will not run — References files that are not bundled: templates/esp-idf-main.c, templates/esphome-secrets.yaml.example, templates/zephyr-esp32.overlay
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/esp-idf-main.c - warning
missing-refreference to a missing file: templates/esphome-secrets.yaml.example - warning
missing-refreference to a missing file: templates/zephyr-esp32.overlay
Process rating: all ten parameters 43/100
- 0Tools and files. 3 referenced file(s) missing: templates/esp-idf-main.c, templates/esphome-secrets.yaml.example, templates/zephyr-esp32.overlay
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2053 tokens
- 100Progress reporting. Reports progress
- low No test case covers injection arriving through data
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 510: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.