Skip to content
Skill

Circuit debugger

Systematic hardware debugging guide for Arduino/ESP32/RP2040 circuits

Install
Scripts
Python
Platforms
Claude Code, Codex, Cursor
GitHub stars
32
Last commit
1 month ago
License
MIT
Listing updated
today

When your agent uses it

Systematic hardware debugging guide for Arduino/ESP32/RP2040 circuits. Use when user reports: circuit not working, components getting hot, no power, intermittent failures, unexpected behavior, sensor not responding, LED not lighting, motor not spinning. Guides through power checks, continuity testing, signal tracing, and component isolation using multimeter techniques.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 5 files (52 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the embedded-engineering-skills plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add wedsamuel1230/embedded-engineering-skills
/plugin install embedded-engineering-skills@embedded-engineering-skills

Or copy only this skill to ~/.claude/skills/circuit-debugger:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/wedsamuel1230/embedded-engineering-skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/circuit-debugger &&
cp -R "$tmp/skills/circuit-debugger" ~/.claude/skills/circuit-debugger &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/circuit-debugger inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/circuit-debugger to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/wedsamuel1230/embedded-engineering-skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/circuit-debugger &&
cp -R "$tmp/skills/circuit-debugger" ~/.agents/skills/circuit-debugger &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/circuit-debugger inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/circuit-debugger to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/wedsamuel1230/embedded-engineering-skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/circuit-debugger &&
cp -R "$tmp/skills/circuit-debugger" ~/.cursor/skills/circuit-debugger &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/circuit-debugger inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/wedsamuel1230/embedded-engineering-skills.git --path skills/circuit-debugger

Or copy the folder to ~/.gemini/skills/circuit-debugger yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/circuit-debugger:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/wedsamuel1230/embedded-engineering-skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/circuit-debugger &&
cp -R "$tmp/skills/circuit-debugger" ~/.copilot/skills/circuit-debugger &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/circuit-debugger inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/wedsamuel1230/embedded-engineering-skills.git

Then copy embedded-engineering-skills/skills/circuit-debugger into your agent's skills folder as circuit-debugger. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Circuit debugger FAQ

How do I install Circuit debugger in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/circuit-debugger to use it in all your projects, or to .claude/skills/circuit-debugger in one project. Or install the embedded-engineering-skills plugin, which includes it: /plugin marketplace add wedsamuel1230/embedded-engineering-skills, then /plugin install embedded-engineering-skills@embedded-engineering-skills.

Does Circuit debugger run scripts?

Yes. It runs Python scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Circuit debugger?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Circuit debugger?

The closest alternatives to Circuit debugger are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Make repo contribution.

More from wedsamuel1230/embedded-engineering-skills

  1. Use when users need Arduino CLI commands for board discovery, library installation, compilation, upload, or serial-port troubleshooting on W

    • Open source
    • 32 GitHub stars
  2. Generate Arduino and embedded C++ snippets for sensors, actuators, buses, state machines, timing, data logging, and hardware abstraction

    • Open source
    • 32 GitHub stars
  3. Build complete Arduino and embedded projects across Arduino IDE, Arduino CLI, PlatformIO, and vendor-specific toolchains

    • Open source
    • 32 GitHub stars
  4. Read and analyze Arduino or embedded serial output for structured runtime debugging across Arduino IDE, Arduino CLI, PlatformIO, and vendor-

    • Open source
    • 32 GitHub stars
  5. Route Arduino and embedded-system requests across Arduino IDE, Arduino CLI, PlatformIO, and vendor-specific tools

    • Open source
    • 32 GitHub stars
  6. Helps choose the right battery type and charging solution for Arduino/ESP32/RP2040 projects

    • Open source
    • 32 GitHub stars

Alternatives to Circuit debugger

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools