New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Esp32 Development

by magnus919 in magnus919/agent-skills

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.

MITAuto-check passedDevelopment

Install Esp32 Development

skills CLI
$ npx skills add magnus919/agent-skills --skill esp32-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install magnus919/agent-skills esp32-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/esp32-development .claude/skills/esp32-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
esp32-development
GitHub stars
116
Token cost
~2.3k tokens
SKILL.md length
1,037 words
Files
21 (incl. scripts, references)
Skills in repo
130
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 7 steps: Identify the exact board, SoC family,… → Read the board schematic or pinout, the… → Start with read-only host and USB… → …
  • Identifying an ESP32 board
  • SKILL.md covers Operating contract, Pre-response evidence gate, First read-only discovery and Choose the path, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Esp32 Development is an agent skill from magnus919/agent-skills. 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.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 24 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `references/connectivity-power-and-ota.md`). Compatibility notes: Portable across agent harnesses. Live work requires the selected framework toolchain, a supported ESP32-family board, data-capable USB connection, and…

It sits in Development, covering Embedded systems. It works with ESP32, C++ and Rust. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.

When your agent uses it

  • Identifying an ESP32 board
  • Choosing a framework
  • Peripheral buses
  • Integrating sensors

Example prompts

  • “/esp32-development”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Portable across agent harnesses. Live work requires the selected framework toolchain, a supported ESP32-family board, data-capable USB connection, and platform serial permissions.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Identify the exact board, SoC family, module, flash/PSRAM size, USB transport, power source, and board revision. Do not transfer a pin map…
  2. Read the board schematic or pinout, the matching SoC/module datasheet, and every attached component datasheet before choosing pins or…
  3. Start with read-only host and USB discovery. Opening a serial monitor may toggle DTR/RTS and reset the target; use a no-reset option when…
  4. Choose one framework based on the product constraint. Reuse its project generator, examples, drivers, build system, flasher, monitor, and…
  5. Bring up one layer at a time: power and boot, serial log, one GPIO, one bus, bus scan or loopback, device identity register, raw readings…
  6. Before the first flash or hardware mutation, confirm the target port, chip family, image/partition layout, rollback or reflashing path…
  7. Preserve calibration controls for real sensors, clocks, ADCs, PWM devices, and actuators. Physical variation is expected.

What it can do on your machine

Read from SKILL.md and the folder at commit c545c2b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Portable across agent harnesses. Live work requires the selected framework toolchain, a supported ESP32-family board, data-capable USB connection, and platform serial permissions.

    From compatibility in the SKILL.md frontmatter.

Context cost

Esp32 Development loads about 2.3k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 1,037 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~132
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~18k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from magnus919/agent-skills at commit c545c2b, republished under its MIT licence (© magnus919). 1,037 words, ~2,267 tokens.

Download SKILL.mdSave it as .claude/skills/esp32-development/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.
name
esp32-development
description
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.
compatibility
Portable across agent harnesses. Live work requires the selected framework toolchain, a supported ESP32-family board, data-capable USB connection, and platform serial permissions.
license
MIT
metadata.source_index
references/source-index.md
metadata.research_checked
2026-07-15

ESP32 Development

Treat the board, attached circuit, firmware, and host toolchain as one system. An ESP32 task is complete only when the intended behavior is observed at the hardware boundary, not when compilation or flashing alone succeeds.

Operating contract

  1. Identify the exact board, SoC family, module, flash/PSRAM size, USB transport, power source, and board revision. Do not transfer a pin map between ESP32, S2, S3, C2, C3, C5, C6, H2, or P4 variants.
  2. Read the board schematic or pinout, the matching SoC/module datasheet, and every attached component datasheet before choosing pins or voltage levels.
  3. Start with read-only host and USB discovery. Opening a serial monitor may toggle DTR/RTS and reset the target; use a no-reset option when the running state matters.
  4. Choose one framework based on the product constraint. Reuse its project generator, examples, drivers, build system, flasher, monitor, and debugger before writing wrappers.
  5. Bring up one layer at a time: power and boot, serial log, one GPIO, one bus, bus scan or loopback, device identity register, raw readings, calibration, then application behavior.
  6. Before the first flash or hardware mutation, confirm the target port, chip family, image/partition layout, rollback or reflashing path, and electrical safety. Never guess a flash offset.
  7. Preserve calibration controls for real sensors, clocks, ADCs, PWM devices, and actuators. Physical variation is expected.

Pre-response evidence gate

Complete this gate before drafting a non-trivial plan or recommendation:

  1. Build a claim ledger for every material positive claim, negative claim, command, and numeric design choice. A URL in source-index.md is navigation, not evidence; retrieve the exact chip/current-version page or mark the claim UNKNOWN.
  2. Command help proves syntax only. Record required target state plus reset, DTR/RTS, download-mode, RAM-stub, port, and mutation effects from current documentation. If operational preconditions are unverified, do not present the command as executable.
  3. Missing hardware artifacts stay missing. Do not replace them with archetypes, examples, or words such as usually, typical, or some modules; state what the observed label does not establish.
  4. Do not invent thresholds, margins, intervals, durations, point counts, percentages, or model forms. Derive them from an authoritative source or a measurement criterion; otherwise leave them UNKNOWN.
  5. Audit the final response against the ledger. Remove or downgrade every material claim that lacks its required evidence.

First read-only discovery

sh
python3 scripts/esp32-preflight.py
python3 scripts/esp32-preflight.py --json
pio device list --json-output       # when PlatformIO is installed
mpremote connect list               # when mpremote is installed

The preflight script does not open serial ports. A USB descriptor can identify a bridge or board family, but it does not prove the chip is in download mode or that a firmware-specific protocol is active. Read decisions and preflight before probing an unknown board.

Choose the path

NeedRead first
Identify board, host, port, transport, or frameworkdecisions and preflight
Select safe pins, power, protection, pull-ups, or level shiftinghardware and electrical safety
Choose ESP-IDF, Arduino, MicroPython, CircuitPython, ESPHome, Zephyr, Rust, or NuttXfirmware frameworks
Create, build, flash, monitor, test, or debug using native CLIsnative tool workflows
Use GPIO, ADC, DAC, PWM, touch, I2C, SPI, UART, I2S, RMT, PCNT, TWAI/CAN, or USBperipherals and buses
Integrate a sensor, display, LED, relay, motor, servo, solenoid, or other loadsensors, actuators, and calibration
Add Wi-Fi, BLE, ESP-NOW, Zigbee/Thread, sleep, OTA, or production power behaviorconnectivity, power, and OTA
Diagnose boot, flashing, crashes, brownouts, buses, networking, or security statedebugging, recovery, and security
Refresh a command or version-sensitive claimsource index
Show full SKILL.md (482 more words)Show less

Minimal bring-up sequence

  1. Fill in templates/hardware-bringup.md and record the exact source for every pin and voltage decision.
  2. Run scripts/esp32-preflight.py; then use the selected framework's own board list and project generator.
  3. Build without hardware. Resolve every warning that changes pin, partition, flash, or security behavior.
  4. Connect only power and USB. Capture the boot log before attaching peripherals.
  5. Flash a framework example or generated minimal project using the framework-produced offsets and image metadata.
  6. Verify serial output, reset behavior, and chip identity. Then add one peripheral or load at a time.
  7. For buses, prove electrical idle levels and run a scan/loopback before introducing a driver. For actuators, test the control signal without the load, then use an external driver and supply.
  8. Run the requested behavior through repeated reset and power-cycle tests. If OTA is in scope, prove rollback or serial recovery before relying on it.

Templates and helper

  • templates/hardware-bringup.md — board, power, pin, component, and recovery worksheet.
  • templates/component-contract.md — datasheet-led sensor or actuator integration record.
  • templates/esp-idf-main.c — small ESP-IDF GPIO task with explicit configurable pins.
  • templates/platformio.ini — minimal PlatformIO environment with explicit board/framework and version-pinning placeholders.
  • templates/micropython-i2c-scan.py — configurable I2C electrical/identity probe.
  • templates/esphome-device.yaml and templates/esphome-secrets.yaml.example — safe ESPHome bring-up configuration with external secrets and explicit framework choice.
  • templates/zephyr-esp32.overlay — minimal devicetree GPIO/I2C overlay pattern.
  • scripts/esp32-preflight.py — dependency-free, non-mutating host/tool/port classifier; run --self-test for its deterministic check.

Hard boundaries

  • ESP32 GPIO is not generally 5 V tolerant. Use the exact datasheet limits and a level shifter or driver when required.
  • Do not power motors, relays, solenoids, servos, high-current LEDs, or large capacitive loads from a GPIO. Use a rated driver, external supply, shared reference where appropriate, and flyback protection for inductive loads.
  • Do not treat a GPIO number as universally safe. Strapping, flash/PSRAM, USB/JTAG, input-only, ADC, and wake restrictions vary by chip, module, board, and boot mode.
  • Do not erase flash as a generic first troubleshooting step. Capture the boot log, image metadata, partitions, calibration/NVS implications, and recovery artifacts first.
  • Secure boot, flash encryption, eFuses, and download-mode restrictions can be irreversible. Read the matching SoC and ESP-IDF security documentation and prove the recovery path on disposable hardware before production provisioning.
  • Never put Wi-Fi, API, OTA, or signing secrets in public templates or source control.

When not to use

Do not use this skill alone for PCB layout certification, RF/antenna design, mains-voltage work, functional-safety certification, medical devices, or a component whose authoritative datasheet is unavailable. Escalate those tasks to the appropriate electrical, RF, safety, or compliance discipline. For a non-ESP32 target, use that platform's own skill and tooling.

Exit criteria

The exact target and sources are recorded; electrical limits and pin choices are justified; the native build and flash tools complete without unexplained errors; logs show the intended image booted; each bus or device passes an identity-level check; calibrated behavior is observed at the physical boundary; and reset, power-cycle, and recovery behavior match the requested deployment mode.

© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 20 other files (scripts, references) in esp32-development of magnus919/agent-skills.

  • SKILL.md
  • README.md
  • evals/evals.json
  • references/connectivity-power-and-ota.md
  • references/debugging-recovery-and-security.md
  • references/decisions-and-preflight.md
  • references/firmware-frameworks.md
  • references/hardware-and-electrical-safety.md
  • references/native-tool-workflows.md
  • references/peripherals-and-buses.md
  • references/sensors-actuators-and-calibration.md
  • references/source-index.md
  • scripts/esp32-preflight.py
  • templates/component-contract.md
  • templates/esp-idf-main.c
  • templates/esphome-device.yaml
  • templates/esphome-secrets.yaml.example
  • … and 4 more

Open the folder on GitHubat commit c545c2b

Compare with similar skills

Esp32 Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Esp32 Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Esp32 Development this skillmagnus919/agent-skills116—~2.3kAutomated safety check: PassMIT
Esp32 Firmware Engineeralxv2016/folloup-sticky1161 repos~3.8kAutomated safety check: PassGPL-3.0
Auto EmbeddedDunCanYounG-1/MICU-auto-embedded253—~1.6kAutomated safety check: PassCC-BY-NC-4.0
Embedded Cpp14 MisraBlueAndi/Pixelix443—~2kAutomated safety check: PassMIT
Embedded Cpp14 MisraBlueAndi/Pixelix443—~2.2kAutomated safety check: PassMIT
C64 Meatloaf Debugidolpx/meatloaf128—~12kAutomated safety check: PassGPL-3.0

Similar skills

  • Esp32 Firmware Engineer

    alxv2016/folloup-sticky

    ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.

    116 GitHub starsUsed in 1 repo~3.8k tokens
    DevelopmentAuto-check passed

  • Auto Embedded

    DunCanYounG-1/MICU-auto-embedded

    全平台嵌入式 AI 开发框架（对标 Trellis）：把 RIPER-5 五阶段协议 + 四文件记忆 + 分层架构门禁 + Scout/Builder/Verifier 多 Agent + 24 个工具调用技能（build/flash/debug/serial/can/modbus/visa/static/memory/rtos/scons），做成『装进工程、项目级 hook…

    253 GitHub stars~1.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Embedded Cpp14 Misra

    BlueAndi/Pixelix

    A skill your agent uses when writing, reviewing, or refactoring C/C++ firmware code in this repository (src/, lib/, test/) — creating or editing .h/.hpp/.cpp files, applying MISRA-oriented and…

    443 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Embedded Cpp14 Misra

    BlueAndi/Pixelix

    Write, review and refactor embedded C/C++14 firmware code in this repository (src/, lib/, test/) with MISRA-oriented rules, defensive programming, Yoda conditions, single-exit/pathfinder control…

    443 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • C64 Meatloaf Debug

    idolpx/meatloaf

    Debug Commodore 64 BASIC programs, cc65-compiled C PRGs, and Meatloaf ESP32 firmware in tandem, using the Ultimate 64's REST API and Meatloaf's UART serial debug output.

    128 GitHub stars~12k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • RuView Quickstart

    ruvnet/RuView

    Gets a newcomer to a running RuView WiFi sensing dashboard, picking between a no-hardware Docker demo, a source build or live ESP32-S3 sensing.

    97k GitHub stars~794 tokensUpdated today
    DevOps & CloudAuto-check: notes

More from magnus919/agent-skills

All 130 skills in this repo

  • Artifact Pyramids

    magnus919/agent-skills

    Organize durable agent research outputs as summaries, analysis, and evidence dossiers.

    116 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Ascii City Engine

    magnus919/agent-skills

    Build portable, first-person colored ASCII city engines and small GIS-derived city packs.

    116 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Color Management

    magnus919/agent-skills

    Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.

    116 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Data Scientist

    magnus919/agent-skills

    A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…

    116 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Docker Compose

    magnus919/agent-skills

    Use Docker Compose to define, run, debug, and harden multi-container applications.

    116 GitHub stars~2k tokensUpdated today
    Auto-check: notes

  • Fpga Development

    magnus919/agent-skills

    Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.

    116 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Esp32 Development

What does Esp32 Development do?

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. Esp32 Development is an agent skill from magnus919/agent-skills. 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.

When should I use Esp32 Development?

Esp32 Development fits situations like: identifying an ESP32 board; choosing a framework; peripheral buses; integrating sensors.

How do I install Esp32 Development in Claude Code?

Run `npx skills add magnus919/agent-skills --skill esp32-development -a claude-code`. Or copy the skill folder (esp32-development in magnus919/agent-skills) into .claude/skills/esp32-development in your project. Claude Code loads it when a task matches its description.

How do I install Esp32 Development in Codex?

Run `npx skills add magnus919/agent-skills --skill esp32-development -a codex`. Or copy the skill folder (esp32-development in magnus919/agent-skills) into .agents/skills/esp32-development in your project. Codex loads it when a task matches its description.

Can I use Esp32 Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill esp32-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/esp32-development, .gemini/skills/esp32-development, .github/skills/esp32-development and .opencode/skills/esp32-development in your project.

What does Esp32 Development need to run?

Going by SKILL.md and its folder, Esp32 Development needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Portable across agent harnesses. Live work requires the selected framework toolchain, a supported ESP32-family board, data-capable USB connection, and platform serial permissions..

Does Esp32 Development access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Esp32 Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Esp32 Development use?

Esp32 Development is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Esp32 Development use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Esp32 Development?

Skills that share tags, products or a category with Esp32 Development: Esp32 Firmware Engineer (alxv2016/folloup-sticky, 116 stars), Auto Embedded (DunCanYounG-1/MICU-auto-embedded, 253 stars), Embedded Cpp14 Misra (BlueAndi/Pixelix, 443 stars) and Embedded Cpp14 Misra (BlueAndi/Pixelix, 443 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Esp32 Development?

magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 116 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 8, 2026.

Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.