error-message-explainer — Claude Code skill: errors and install
error-message-explainer explains compiler, upload, boot, power, and runtime failures in Arduino and embedded projects. Use it when an IDE or board error needs a board-specific recovery plan.
MIT 206 installs ★ 33 updated 2026-10-15
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a claude-codeWhat error-message-explainer does
This skill turns compiler and upload messages into plain explanations, likely causes, and concrete code fixes. It keeps build evidence separate from upload, board, and system evidence, so a code correction is not presented as a hardware repair. The workflow covers Arduino IDE, Arduino CLI, PlatformIO, and vendor-specific tools.
The package includes scripts/parse_errors.py, which can inspect error_log.txt, one supplied message, interactive input, or output piped from arduino-cli compile. A separate Uno R4 reference covers WiFi, OTA, USB, and board-recognition caveats. Before suggesting a reset, flash erase, bootloader repair, or reflash, capture the board revision, tool and library versions, port, power path, and last known-good image.
What it helps with
- interpret a compiler diagnostic
- trace an upload failure
- separate code faults from board faults
- choose a recovery path for a specific board
- parse a compiler log with
parse_errors.py
Example prompts for the agent
- Explain the errors in
error_log.txtand give a fix for my exact board. - Analyze the output of
arduino-cli compileand separate build problems from upload problems. - Explain this compiler message, show the code change, and tell me why it happens.
How to install error-message-explainer
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a claude-code2Manually: put the files in place
~/.claude/skills/error-message-explainer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/error-message-explainer/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a codex2Manually: put the files in place
.agents/skills/error-message-explainer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a cursor2Manually: put the files in place
.cursor/skills/error-message-explainer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wedsamuel1230/embedded-engineering-skills skills/error-message-explainer2Manually: put the files in place
.github/skills/error-message-explainer/SKILL.md1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a gemini-cli2Platform CLI
gemini skills install https://github.com/wedsamuel1230/embedded-engineering-skills --path skills/error-message-explainerManually: put the files in place
.devin/skills/error-message-explainer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about error-message-explainer
How do I install error-message-explainer in Claude Code?
Run npx skills add wedsamuel1230/embedded-engineering-skills --skill error-message-explainer -a claude-code. The skill file will be placed at ~/.claude/skills/error-message-explainer/SKILL.md.
What does error-message-explainer do?
It explains compiler, upload, boot, power, and runtime errors in Arduino and embedded projects. The skill gives a board-aware fix and keeps software issues separate from hardware or system failures.
What should I collect before resetting or reflashing a board?
Record the board and revision, tool and library versions, port, power path, and last known-good image first. The recovery guidance then covers failed uploads, boot failures, power faults, and corrupted firmware.
Source text
SKILL.md · MIT
---
name: error-message-explainer
description: Explain Arduino and embedded compiler, upload, boot, power, and runtime errors in plain English. Use when a user shares an error or failure from Arduino IDE, Arduino CLI, PlatformIO, or a vendor-specific tool. Separate build, upload, hardware, and system evidence and give a board-specific recovery path without assuming UNO, ESP32, or RP2040 behavior.
metadata: {triggers: "compiler error, upload failure, boot failure, power error, runtime error"}
---
# Error Message Explainer
Translates cryptic compiler errors into actionable fixes for Arduino/ESP32/RP2040 projects.
## Resources
This skill includes bundled tools:
- **scripts/parse_errors.py** - Automated error analysis with 20+ error patterns
- **../../docs/board-support/uno-r4-family.md** - Shared Uno R4 board-family caveats
## Quick Start
**Analyze error from file:**
```bash
uv run --no-project scripts/parse_errors.py --file error_log.txt
```
**Analyze single error:**
```bash
uv run --no-project scripts/parse_errors.py --message "error: 'LED' was not declared in this scope"
```
**Interactive mode:**
```bash
uv run --no-project scripts/parse_errors.py --interactive
```
**Pipe from compiler:**
```bash
arduino-cli compile 2>&1 | uv run --no-project scripts/parse_errors.py --stdin
```
## How to Use This Skill
When user pastes an error message:
1. Identify the error type from patterns below
2. Explain what it means in simple terms
3. Show the specific fix with code example
4. Explain WHY this error happens (educational value)
5. If the target is Uno R4 family and the failure touches WiFi, OTA, USB, or
board recognition, open `../../docs/board-support/uno-r4-family.md`
## Recovery Boundary
Before recommending a reset, erase, bootloader repair, or reflash, capture the
exact board/revision, tool and library versions, port, power path, and last
known-good image. Use [the router recovery reference](../arduino-workflow-router/references/failure-recovery.md)
for failed uploads, boot failures, power faults, or corrupted firmware. Do not
call a compile fix a hardware or system fix.
## Common Compilation Errors
### 1. "'xyz' was not declared in this scope"
```
error: 'xyz' was not declared in this scope
```
**Meaning:** Compiler doesn't recognize the name `xyz`.
**Common Causes & Fixes:**
| Cause | Fix |
|-------|-----|
| Typo in variable/function name | Check spelling, C++ is case-sensitive! |
| Variable used before declaration | Move declaration before first use |
| Missing `#include` | Add required library header |
| Function defined after it's called | Add forward declaration or move function up |
**Example - Typo:**
```cpp
// WRONG
int ledpin = 13; // lowercase 'p'
digitalWrite(ledPin, HIGH); // uppercase 'P' - DIFFERENT!
// CORRECT
int ledPin = 13;
digitalWrite(ledPin, HIGH);
```
**Example - Missing Include:**
```cpp
// WRONG - Servo not defined!
Servo myServo;
// CORRECT
#include <Servo.h>
Servo myServo;
```
---
### 2. "expected ';' before..."
```
error: expected ';' before 'xyz'
```
**Meaning:** Missing semicolon on the previous line.
**Fix:** Add `;` at end of the line ABOVE the error.
```cpp
// WRONG - error points to line 3
int x = 5 // ← missing ; here!
int y = 10;
// CORRECT
int x = 5;
int y = 10;
```
**Pro Tip:** The error line number is where compiler noticed the problem, not where the missing `;` is!
---
### 3. "expected ')' before..." or "expected '}' before..."
```
error: expected ')' before ';'
error: expected '}' at end of input
```
**Meaning:** Mismatched parentheses or braces.
**Common Patterns:**
```cpp
// WRONG - unmatched parenthesis
if (x > 5 { // missing )
}
// WRONG - unmatched brace
void setup() {
Serial.begin(115200);
// missing closing }
// CORRECT
if (x > 5) {
}
void setup() {
Serial.begin(115200);
}
```
**Debugging Tip:** Use IDE auto-format (Ctrl+T) to reveal mismatches.
---
### 4. "invalid conversion from 'const char*' to 'char*'"
```
error: invalid conversion from 'const char*' to 'char*'
```
**Meaning:** Trying to modify a string literal (which is read-only).
```cpp
// WRONG
char* message = "Hello"; // string literals are const!
message[0] = 'h'; // can't modify!
// CORRECT (if you need to modify)
char message[] = "Hello"; // creates modifiable copy
message[0] = 'h'; // OK!
// CORRECT (if read-only is fine)
const char* message = "Hello";
```
---
### 5. "no matching function for call to..."
```
error: no matching function for call to 'SomeClass::method(int, int, int)'
note: candidate: void SomeClass::method(int, int)
```
**Meaning:** Function called with wrong number or type of arguments.
```cpp
// WRONG - too many arguments
myServo.write(90, 100); // write() takes only 1 argument!
// CORRECT
myServo.write(90);
```
**Read the "note:" lines** - they show what arguments ARE accepted.
---
### 6. "multiple definition of 'xyz'"
```
error: multiple definition of 'xyz'
```
**Meaning:** Same variable/function defined in multiple files.
**Fixes:**
```cpp
// In header file (.h), use 'extern':
extern int globalVar; // declaration only
// In ONE .cpp file, define it:
int globalVar = 0; // actual definition
```
Or for functions in header:
```cpp
// WRONG - defined in header, included multiple times
int add(int a, int b) { return a + b; }
// CORRECT - use 'inline'
inline int add(int a, int b) { return a + b; }
```
---
### 7. "'xyz' does not name a type"
```
error: 'WiFiClient' does not name a type
```
**Meaning:** Class/type not recognized.
**Fixes:**
| Board | Library | Include |
|-------|---------|---------|
| ESP32 | WiFi | `#include <WiFi.h>` |
| ESP8266 | WiFi | `#include <ESP8266WiFi.h>` |
| Arduino + WiFi Shield | WiFi | `#include <WiFi.h>` |
```cpp
// WRONG
WiFiClient client; // WiFiClient unknown!
// CORRECT for ESP32
#include <WiFi.h>
WiFiClient client;
```
---
### 8. "redefinition of 'xyz'"
```
error: redefinition of 'int x'
```
**Meaning:** Variable declared twice in same scope.
```cpp
// WRONG
int count = 0;
int count = 0; // redefinition!
// WRONG in loops
for (int i = 0; i < 10; i++) {
int i = 5; // shadows loop variable!
}
// CORRECT
int count = 0; // declare once
count = 5; // assign without 'int'
```
---
## Upload Errors
### 9. "avrdude: stk500_recv(): programmer is not responding"
```
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt X of 10: not in sync
```
**Meaning:** Arduino IDE can't communicate with the board.
**Fixes (try in order):**
1. ✅ Correct board selected? (Tools → Board)
2. ✅ Correct port selected? (Tools → Port)
3. ✅ USB cable is data cable (not charge-only)?
4. ✅ Try different USB port
5. ✅ Nothing connected to pins 0/1 (TX/RX)?
6. ✅ Press reset button during upload
7. ✅ Install/reinstall USB drivers
---
### 10. "A fatal error occurred: Failed to connect to ESP32"
```
A fatal error occurred: Failed to connect to ESP32:
Timed out waiting for packet header
```
**Meaning:** ESP32 not entering bootloader mode.
**Fix:** Hold BOOT button while uploading:
1. Click Upload in IDE
2. When "Connecting..." appears, hold BOOT button
3. Release when upload starts
4. Some boards: hold BOOT, press EN/RST, release BOOT
---
### 11. "Sketch too big"
```
Sketch too big; see https://support.arduino.cc/...
Sketch uses 34816 bytes (107%) of program storage space.
Maximum is 32256 bytes.
```
**Meaning:** Program doesn't fit in flash memory.
**Fixes:**
```cpp
// 1. Use F() macro for strings (saves RAM + sometimes Flash)
Serial.println(F("This string in flash")); // instead of RAM
// 2. Remove unused libraries
// Each #include adds code even if not used
// 3. Use smaller data types
uint8_t x = 5; // instead of int (2 bytes saved)
// 4. Choose board with more flash (ESP32 has 4MB vs Arduino's 32KB)
```
---
## Library Errors
### 12. "fatal error: xyz.h: No such file or directory"
```
fatal error: Adafruit_BME280.h: No such file or directory
```
**Meaning:** Library not installed.
**Fix:**
1. Sketch → Include Library → Manage Libraries
2. Search for library name
3. Click Install
4. If not in Library Manager: download ZIP, Sketch → Include Library → Add .ZIP Library
---
### 13. "exit status 1 / Error compiling for board..."
```
exit status 1
Error compiling for board Arduino Uno.
```
**Meaning:** Generic error - scroll UP to find the real error message.
**The actual error is ABOVE this line!** Look for lines containing `error:`.
---
## Type Errors
### 14. "cannot convert 'String' to 'const char*'"
```
error: cannot convert 'String' to 'const char*'
```
**Meaning:** Function expects C-string but got Arduino String.
```cpp
// WRONG
String myString = "hello";
someFunction(myString); // if someFunction expects const char*
// CORRECT
String myString = "hello";
someFunction(myString.c_str()); // convert to C-string
```
---
### 15. "invalid operands to binary expression"
```
error: invalid operands of types 'const char*' and 'const char*' to binary 'operator+'
```
**Meaning:** Can't use `+` with C-strings.
```cpp
// WRONG
const char* a = "hello";
const char* b = " world";
const char* c = a + b; // doesn't work!
// CORRECT - use String
String a = "hello";
String b = " world";
String c = a + b; // works!
// Or use snprintf
char c[20];
snprintf(c, sizeof(c), "%s%s", a, b);
```
---
## Quick Reference Table
| Error Contains | Likely Problem | Quick Fix |
|----------------|----------------|-----------|
| "not declared" | Typo or missing include | Check spelling, add #include |
| "expected ';'" | Missing semicolon | Add ; to line ABOVE error |
| "expected ')'" | Unmatched parenthesis | Count ( and ) |
| "expected '}'" | Unmatched brace | Count { and } |
| "no matching function" | Wrong arguments | Check function signature |
| "does not name a type" | Missing library | Add #include |
| "multiple definition" | Defined in multiple files | Use extern |
| "stk500" | Upload failed | Check board/port/cable |
| "No such file" | Library not installed | Install via Library Manager |
| "too big" | Out of flash | Use F(), remove unused code |
## Debugging Strategy
1. Read the FIRST error (later ones often cascade)
2. Note the FILE and LINE NUMBER
3. Look at that line AND the line above
4. Check for common patterns above
5. Fix ONE error at a time, recompile
6. Repeat until clean
## Shared Output Contract
Use [the shared Arduino skill contract](../../docs/arduino-skill-contract.md):
state assumptions, required tools and versions, implementation steps,
tests/evidence by proof stage, known limitations, and recovery/security notes.
© wedsamuel1230 · MIT · wedsamuel1230/embedded-engineering-skills