Wokwi Agent Skills
AI coding agents can write firmware, but they can't tell whether it works without a board on the desk. The Wokwi agent skills close that loop. Each skill teaches the agent one job on the Wokwi simulator: the commands to run, the output to expect and the pitfalls to avoid.
A skill is a folder with a SKILL.md file in the open Agent Skills format, so the same files work in Claude Code, Cursor, Codex, Copilot and other agents that read skills. The agent picks up a skill when your request matches it, for example "check this firmware for memory leaks".
The skills run the Wokwi CLI (0.29.0 or newer) or idf.py wokwi, and both need a CLI token. Create a token on the Wokwi CI Dashboard and set the WOKWI_CLI_TOKEN environment variable where the agent runs.
Available skills
| Skill | Use it to | Related docs |
|---|---|---|
find-memory-leaks | Catch slow leaks in ESP-IDF firmware. The simulator watches the heap while a scenario drives hours of use in seconds. | Heap monitoring |
test-lvgl-ui | Regression-test an LVGL (or any other) display UI in CI, with taps, swipes and pixel-exact screenshot comparison. | Automation scenarios |
debug-esp32-firmware | Decode a panic backtrace, reproduce the bug with scripted inputs, trace a bus to a VCD file and attach GDB without a debug probe. | Debugging with GDB |
verify-esp-idf-build | Run and check an ESP-IDF build with idf.py wokwi right after building, with no devkit attached. | ESP-IDF simulation extension |
New skills are added to the skills repository first, so check its README for the current list.
Install the skills
Claude Code
Install all the skills as a plugin:
/plugin marketplace add wokwi/skills
/plugin install wokwi@wokwi-skills
The skills are then available as /wokwi:<skill>, for example /wokwi:find-memory-leaks.
To add a single skill to one project without the plugin, copy its folder (skills/<name>/) from the repository into the .claude/skills/ directory of your project, or into ~/.claude/skills/ to use it in every project.
Other agents
Copy the skill folder to the directory your agent loads skills from, or paste the body of SKILL.md into the instructions file the agent reads (AGENTS.md, .cursorrules, copilot-instructions.md). The files are plain Markdown with a small YAML header.
Skills and MCP
The skills don't need the Wokwi MCP server: the agent runs wokwi-cli like any other command, then reads the exit code and the output. The MCP server is the other way to connect an agent to Wokwi. It gives the agent tools to control a running simulation step by step: start it, read the serial output, press a button, take a screenshot. You can use both in the same project.