serial-debug
CLI-first serial port debugging and macro automation with serial-mcp-server for Codex and Claude Code. Use when working with UART or USB-serial devices, listing serial ports, probing STM32/Arduino/ESP32 boards, writing or reading serial data, running JSON serial macros, controlling RTS/DTR, or using serial-mcp-server through MCP tools.
pinned to #6c05e38updated 2 months ago
Ask your AI client: “install skills/serial-debug”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/serial-debugmetahub onboarded this repo on the author's behalf.
If you own github.com/Adancurusul/serial-mcp-server on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
75
Last commit
2 months ago
Latest release
published
- #agent-skill
- #ai-agents
- #claude-code
- #cli
- #codex-skill
- #embedded
- #hardware-debugging
- #json-dsl
- #macro-automation
- #mcp
- #mcp-server
- #rust
- #serial
- #serial-debugging
- #skill
- #uart
- #usb-serial
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.6c05e38· 2 months ago
Kind-specific
3 passed1 warningSkill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at skills/serial-debug/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
315 words · 2,237 chars · 4 sections · 5 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent6c05e38warn2 months ago
Contents
Operating Rule
Use the serial-mcp-server CLI first unless the user explicitly asks for MCP or an MCP client is already configured. Keep stdout data separate from diagnostics, cite exact commands, and base hardware success on real command evidence from the device.
Workflow
- Confirm the binary is available:
serial-mcp-server --help
- List available ports before choosing a device:
serial-mcp-server list-ports --json
- For a device smoke test, probe the port first, then write/read only when the probe succeeds:
serial-mcp-server probe --port <port> --baud 115200 --json
serial-mcp-server write --port <port> --baud 115200 --data H --read --timeout-ms 1000 --json
- If RTS or DTR is involved, state the requested line levels and use the control-line command:
serial-mcp-server set-control-lines --port <port> --rts high --dtr low --json
- For repeatable serial procedures, prefer JSON macro packs and validate or plan them before real hardware execution:
serial-mcp-server macro validate --file <pack.json> --json
serial-mcp-server macro plan --file <pack.json> --macro <name> --json
serial-mcp-server macro run --file <pack.json> --macro <name> --simulate-read <response> --json
serial-mcp-server macro run --file <pack.json> --macro <name> --port <port> --baud 115200 --json
Macro packs are restricted JSON DSL files. v0.3 supports send, delay, expect contains, expect equals, and assemblies that call macros. It does not support shell commands, language execution, loops, variables, Quick commands, or RTS/DTR macro steps.
References
- Read
references/cli.mdfor exact command behavior, output expectations, and automation rules. - Read
references/mcp.mdwhen the user asks for MCP setup or MCP tool usage. - Read
references/hardware-safety.mdbefore changing baud, wiring, voltage levels, RTS, DTR, or reset/boot lines. - Read
references/troubleshooting.mdwhen a command fails, times out, returns no ports, or cannot open the device.
Reporting
Report the command, exit status, and the relevant JSON or error excerpt. If no hardware is connected, limit the validation summary to discovery and help paths.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/serial-debug