Borrowing it
Nothing to install: this file belongs to wedsamuel1230/electronic-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wedsamuel1230/electronic-mcp-server/main/.github/skills/error-message-explainer/SKILL.mdgit clone --depth 1 https://github.com/wedsamuel1230/electronic-mcp-serverWrote 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/electronic-mcp-server/error-message-explainer)<a href="https://agentmods.dev/skills/wedsamuel1230/electronic-mcp-server/error-message-explainer"><img src="https://agentmods.dev/badge/skills/wedsamuel1230/electronic-mcp-server/error-message-explainer.svg" alt="Measured on agentmods" height="20"></a>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.00066 | $0.02556 |
| Opus 5 | $0.00033 | $0.01278 |
| Sonnet 5 | $0.00013 | $0.00511 |
| Haiku 4.5 | $0.00007 | $0.00256 |
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 6d 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.
This is a copy
86% identical to error-message-explainer — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 422 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
Quick Start
Analyze error from file:
uv run scripts/parse_errors.py --file error_log.txt
Analyze single error:
uv run scripts/parse_errors.py --message "error: 'LED' was not declared in this scope"
Interactive mode:
uv run scripts/parse_errors.py --interactive
Pipe from compiler:
arduino-cli compile 2>&1 | uv run 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)
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:
// WRONG
int ledpin = 13; // lowercase 'p'
digitalWrite(ledPin, HIGH); // uppercase 'P' - DIFFERENT!
// CORRECT
int ledPin = 13;
digitalWrite(ledPin, HIGH);
Example - Missing Include:
// 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.
// WRONG - error points to line 3
int x = 5 // ← missing ; here!
int y = 10;
// CORRECT
int x = 5;
int y = 10;
What ships with it
2 files 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.
- 6d ago First seen · 422 lines · 66 tokens per session scan A 5c322368c1b9
error-message-explainer is a skill published in the GitHub repository wedsamuel1230/electronic-mcp-server (1 stars, last pushed 8mo ago), licensed MIT. It adds 66 tokens to every session and 2,556 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to error-message-explainer, differing in 30 lines, and is treated as a copy.
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…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…