reSpeaker Clip firmware-dev skill (clip-dev)
Agent skill that encodes the reSpeaker Clip firmware's real build constraints, AT command contracts, and audio pipeline truth so coding agents stop re-deriving facts that are easy to get wrong.
What it does and how it connects
clip-dev is an agent skill that ships inside the reSpeaker Clip firmware repository. It tells a coding agent to treat the checked-out source as authoritative and to read CLAUDE.md before changing firmware, then routes each task to its source of truth: AT commands in at_commands.c, BLE and UDP transport files, audio and DSP in audio.c and Kconfig, storage in storage.c, and power behavior in clip_event.c, storage.c and battery.c.
The skill pins down the firmware's real build and protocol facts so agents stop re-deriving them: the nRF5340 board builds with NCS v3.3.0 and west against board clip/nrf5340/cpuapp, production images use a snippet that disables console logging for meaningful idle-current measurement, session IDs are exactly 14 decimal digits, and success replies are {"ok":true,"data":...} while failures use {"ok":false,"msg":"..."}.
It also records the current protocol rules: use AT+GSTAT, not AT+STATUS?, recording commands are START, STOP, PAUSE, RESUME and MARK, audio mode is normal or enhanced with no runtime bitrate or codec commands, and AT+WIFI=on returns AP credentials with UDP file transfer on port 8089. The firmware itself runs on Zephyr RTOS on the Nordic nRF5340, with PDM microphones, SpeexDSP preprocessing, Opus encoding, BLE, Wi-Fi AP, USB and microSD storage, and a production idle current of about 170 microamps stated in the README.
What engineers report
My Clip draws about 35 mA on battery, about 200× the ~0.17 mA idle figure in `docs/power.md`.
2026-11-06Read the original
Alternatives
Compare side by side- zephyr-agent-skills
An agent skill for Zephyr development in general, rather than a skill encoding one device's firmware build and AT contracts.
- LabWired Core
A simulator that runs firmware on a virtual instance of a real chip, rather than a skill that pins down one real device's firmware facts.
- Adsum IoT Coder
An IoT coding agent, rather than a firmware skill for a single wearable recorder.
- agentic-hil
Hardware-in-the-loop agent testing, rather than build and protocol facts for one Zephyr device.
- zbot
An embedded agent, rather than a skill that stops agents re-deriving one firmware's constraints.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- PlatformIO support for Zephyr quietly ended, creating surprise workflow dead ends.Error Index
- First physical run on a NUCLEO-H723ZG asked for ADC_ACQ_TIME_DEFAULT, which the STM32 driver reads as the shortest window, so three ADC3 inputs sagged as voltage rose (A4 read 214 mV low at 3.2 V) and five ADC1 inputs read ~35 mV high, yet all tests passed because everything sat inside the old 150 mV tolerance.Error Index
- sntp_simple returns -ETIMEDOUT long before the caller's timeout after a stale response, because the code compares against positive ETIMEDOUT; reproduced on an ESP32-S3 station right after it joins Wi-Fi.Error Index
Sources
Not verified
- Pricing: none stated on the repo.
- No GitHub releases are returned by the releases API because the existing releases are prereleases; the newest is prerelease v0.1.4 dated 2026-09-21, so latest release fields are null.
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.