jl-codes/platformio-mcp

platformio-dashboard

Open and operate the PIO Agent dashboard when the user asks to view projects, devices, logs, approvals, tasks, locks, or monitor state in a visual interface. Do not use for unattended or scheduled runs.

get-started

Set up PIO Agent in Codex for a first PlatformIO project inspection. Use when a user has just installed the plugin, asks how to start, or needs help checking local prerequisites. Do not use for flashing or unattended hardware actions.

pio-manager

The Single Source of Truth for executing PlatformIO operations via the pio-agent CLI (compiling, flashing, log-reading, uploading filesystems, managing libraries, testing, and port claims). Agents MUST route all hardware executions through this skill. Use…

pio-manager

The Single Source of Truth for executing PlatformIO operations via the pio-agent CLI (compiling, flashing, log-reading, uploading filesystems, managing libraries, testing, and port claims). Agents MUST route all hardware executions through this skill. Use…

platformio-debug

Diagnose and fix PlatformIO build, upload, and configuration failures. Use when resolving compiler errors, missing libraries, platformio.ini issues, memory overflows, port conflicts, permission errors, failed uploads, crash backtraces, or firmware size…

serial-diagnostics

Diagnose embedded runtime behavior through serial logs after build/upload. Use when investigating boot loops, crashes, watchdog resets, panic output, missing boot markers, peripheral initialization issues, or silent serial sessions.

esp32-flash-monitor

Run the common ESP32 workflow in PlatformIO: build, flash, monitor, diagnose, patch, and retry. Use for ESP32/ESP8266/ESP32-S3/ESP32-C3 projects using Arduino or ESP-IDF.

firmware-bringup

Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.

hardware-in-the-loop-test

Validate firmware behavior on real hardware rather than compilation-only checks. Use when running physical acceptance tests, confirming boot markers, validating sensor output, or checking runtime timing/telemetry.

platformio-monitoring-automation

Create or update recurring PlatformIO build, device-presence, serial-health, or bounded lab-test monitoring when the user asks to schedule, watch, monitor repeatedly, or receive follow-ups. Do not use for one-time interactive diagnostics.

sbc-deploy

Deploy and validate services on single-board computers such as Raspberry Pi, Jetson, Orange Pi, BeagleBone, and Coral. Use when checking SSH connectivity, runtime dependencies, logs, service health, Docker workloads, or systemd deployment.

embedded-systems

Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption. Invoke for STM32, ESP32, FreeRTOS, bare-metal, power optimization, real-time systems.

house-style-documentation

Consistently and thoroughly document TypeScript/Node code following the project's "house style". Use this skill whenever documenting, refactoring, or creating new TypeScript modules to ensure they meet the specific JSDoc, method, and naming standards. Also…

esp32-flash-monitor

Run the common ESP32 workflow in PlatformIO: build, flash, monitor, diagnose, patch, and retry. Use for ESP32/ESP8266/ESP32-S3/ESP32-C3 projects using Arduino or ESP-IDF.

firmware-bringup

Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.

hardware-in-the-loop-test

Validate firmware behavior on real hardware rather than compilation-only checks. Use when running physical acceptance tests, confirming boot markers, validating sensor output, or checking runtime timing/telemetry.

platformio-debug

Diagnose and fix PlatformIO build, upload, and configuration failures. Use when resolving compiler errors, missing libraries, platformio.ini issues, memory overflows, port conflicts, permission errors, or failed uploads.

serial-diagnostics

Diagnose embedded runtime behavior through serial logs after build/upload. Use when investigating boot loops, crashes, watchdog resets, panic output, missing boot markers, peripheral initialization issues, or silent serial sessions.