Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add wedsamuel1230/arduino-skills --skill error-message-explainergit clone --depth 1 https://github.com/wedsamuel1230/arduino-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wedsamuel1230/arduino-skills/error-message-explainer)<a href="https://agentmods.dev/skills/wedsamuel1230/arduino-skills/error-message-explainer"><img src="https://agentmods.dev/badge/skills/wedsamuel1230/arduino-skills/error-message-explainer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wedsamuel1230/arduino-skills/error-message-explainer"><img src="https://agentmods.dev/badge/skills/wedsamuel1230/arduino-skills/error-message-explainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00080 | $0.02806 |
| Opus 5 | $0.00040 | $0.01403 |
| Sonnet 5 | $0.00016 | $0.00561 |
| Haiku 4.5 | $0.00008 | $0.00281 |
Grade A, and why
error-message-explainer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- error-message-explainer — 86% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
uv run --no-project scripts/parse_errors.py --file error_log.txt
Analyze single error:
uv run --no-project scripts/parse_errors.py --message "error: 'LED' was not declared in this scope"
Interactive mode:
uv run --no-project scripts/parse_errors.py --interactive
Pipe from compiler:
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:
- Identify the error type from patterns below
- Explain what it means in simple terms
- Show the specific fix with code example
- Explain WHY this error happens (educational value)
- 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 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 |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 438 lines · 80 tokens per session scan A 90aec1a81060
error-message-explainer is a skill published in the GitHub repository wedsamuel1230/arduino-skills (21 stars, last pushed 21d ago), licensed MIT. It adds 80 tokens to every session and 2,806 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
analyze-kernel-bottleneck
Systematically identify whether a GPU kernel is compute-bound, memory-bound, or latency-bound using roofline analysis, occupancy calculations, compute/load ratio per tile, and SASS instruction inspection. Produces a decision matrix for optimization strategy selection (cp.async, warp interleaving, tiling…
mcubuddy
Use when debugging MCU firmware or boards with McuBuddy, including probe, boot, HardFault, peripheral, register, memory, ELF/SVD, RTOS, RTT/UART, Keil, GDB, pyOCD, J-Link, ST-Link, or CMSIS-DAP work.
fpga-hardware-design-and-review-guide
Comprehensive FPGA hardware design guide based on real-world project experience. Covers pipeline architecture, timing optimization, SystemVerilog coding patterns, CDC handling, and practical debugging techniques. Use this skill when: (1) designing FPGA modules with timing constraints, (2) implementing video processing…
cuda-debugger
Debugs CUDA kernel errors using compute-sanitizer (memcheck, racecheck, initcheck, synccheck), cuda-gdb (non-interactive batch backtrace), and cuobjdump (PTX/SASS/register analysis). Use when a CUDA kernel crashes (segfault, illegal memory access), produces wrong results, hangs, or when the user asks to debug or…