error-message-explainer_skill

Overview

This skill interprets Arduino, ESP32, and RP2040 compiler and upload errors in plain English for beginners. It turns cryptic messages into actionable fixes, code examples, and short explanations of why the error happens. The aim is fast troubleshooting so you can fix one error at a time and get back to building.

How this skill works

Paste or send the compiler/upload error output and the skill matches it against common patterns (undefined names, missing includes, type mismatches, upload failures, size limits, etc.). It explains the root cause, shows a minimal fix or code snippet, and gives a brief why—so you learn the underlying issue. When needed it suggests board-specific or upload steps (port/boot mode/driver checks).

When to use it

• You get a compile error like "not declared", "expected ';'", or "does not name a type".
• Upload failures (stk500, avrdude, ESP32 failed to connect) or port/boot issues.
• Library missing errors such as "fatal error: xyz.h: No such file or directory".
• Type conversion and function signature mismatches (no matching function, invalid conversion).
• Sketch too big or memory/flash related warnings preventing upload.

Best practices

• Read and fix the FIRST reported error; many later messages cascade from it.
• Check the line above the reported error for missing semicolons or unmatched braces.
• Include the exact error text and the file/line if available for precise suggestions.
• Try one fix at a time and recompile to isolate remaining issues.
• Use board-appropriate includes (ESP32 vs ESP8266) and confirm the selected board/port before diagnosing uploads.

Example use cases

• User pastes: "error: 'LED' was not declared in this scope" and receives typo/include checklist plus code fix.
• User reports: "avrdude: stk500_recv(): programmer is not responding" and receives step-by-step port/driver/boot advice.
• User copies: "fatal error: Adafruit_BME280.h: No such file or directory" and gets library install instructions.
• User sees: "Sketch too big" and gets tips to shrink footprint (F(), remove libs, use smaller types).
• User reports type errors like "invalid conversion from 'const char*' to 'char*'" and gets correct const usage or modifiable buffers.