espos-own-firmwarelisted
Install: claude install-skill signalk-espOS/skills
# Your own firmware on espOS, from repo to boat
Verified against espOS v0.24.0, registry `schema: 1`, and the firmware repos'
workflows as of late October 2026. This is the order of work for someone outside the
project; `espos-firmware-project` has the detail behind each step and
`espos-keys-ota-fleet` the signing and OTA side. Two reference firmwares run all of
this in production:
* [dirkwa/espos-ble-gateway](https://github.com/dirkwa/espos-ble-gateway): five
chips, one image per chip, 8 and 16 MB layouts for the ESP32, S3 and C6 dev kits,
espOS's shared `build-firmware.yml`. **Start here** for the project layout.
* [dirkwa/espos-p4-cockpit](https://github.com/dirkwa/espos-p4-cockpit): one chip,
two display boards, one image per board, a fully inline release job.
For the workflow files themselves (`ci.yml`, `track-espos.yml`, `pr-title.yml`,
`label-by-title.yml`), copy the newest repo,
[dirkwa/espos-bathy-bridge](https://github.com/dirkwa/espos-bathy-bridge), or the
Zigbee coordinator once its first PR merges. The repos copy each other and the older
copies miss fixes found later:
| Fix | Where it is | Missing from |
|---|---|---|
| `track-espos.yml` falls back to the workflow token when the App is not installed on the repo (the key alone answers 404 and failed every run) | nmea-gateway #16, bathy-bridge #9 | ble-gateway, cockpit |
| `track-espos.yml` closes a prerelease bump of the tag it now tracks (`sort -V` ranks `v1.2.0-rc1` above `v1.2.0`) | bathy-bridge #1 |