signalk-espOS/skills

Claude Code skills distilled from building espOS,
a SignalK runtime for ESP32 devices. They encode what actually went wrong and what the
measurement showed — not a paraphrase of the ESP-IDF docs.
Install:
espos-firmware is not espOS-specific: its three skills are about ESP-IDF, the ESP
Component Registry and GitHub Actions, and apply to any ESP32 firmware project.
espos-dev is the opposite: how espOS and its child repos fit together, for anyone
working on them.
espos-firmware
Three sibling skills, installed together.
espos-memory-budget
Why a board with 8 MB of PSRAM still exhausts internal RAM, which pool TLS and the
radio really draw from, and how to size task stacks from a high-water measurement
instead of a guess. Includes the four PSRAM traps (starting with
CONFIG_SPIRAM_MALLOC_ALWAYSINTERNAL defaulting to 16384, which leaves PSRAM
entirely unused), which task stacks can move to PSRAM and which cannot, why IRAM is
heap on a unified-SRAM part like the C5, and the per-stage boot budget that turns "it
runs out of memory" into a number you can act on.
espos-registry-components
Why a component's optional dependencies and feature checks silently stop working when
a consumer installs it from the ESP Component Registry rather than a checkout: target
names are namespaced (myns__mycomp), so if(mycomp IN_LIST BUILD_COMPONENTS) is
false and the feature compiles out with no error. Includes the same defect in IDF's
own idf_component_optional_requires(), a namespace-tolerant replacement, and why
your CI probably cannot catch this.
espos-firmware-releases
Publishing firmware a browser-based flasher can download. GitHub serves release assets
with no CORS header, so a web page cannot fetch them at all; the fix is a mirror
branch, and doing that safely on a shared branch means --force-with-lease with a
retry. Includes the GitHub Actions concurrency behaviour that silently drops a release,
and the rollback traps that can delete another release's firmware.
espos-dev
Four sibling skills for working on espOS itself and the projects built on it.
espos-ecosystem
Which repo owns what (espOS, registry, signalk-espos-manager, the cockpit and its WASM
preview, the BLE gateway, the HMI designer, the stream plugin), the contracts between
them that must change in lockstep, where a fix belongs, and the house rules that differ
per repo. Load it first.
espos-firmware-project
Starting and building a firmware on espOS: the one-time repository setup (secrets,
the Docker Hub login CI needs and the three quiet ways it fails, Dependabot for action
pins, the release App), the CMake prologue and optional components, sdkconfig
layering, partition tables, the IDF version pin, the locked build wrapper, host tests,
bumping the espos submodule without breaking dependencies.lock, gating a target on
a minimum espOS release, and releasing through espOS's reusable workflows.