Best use case
serial-debug is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using serial-debug should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/serial-debug/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How serial-debug Compares
| Feature / Agent | serial-debug | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill: Serial Debugging & Hardware Communication Standards ## 1. UART (Universal Asynchronous Receiver/Transmitter) * **Standard Config**: 115200 8N1 (8 bits, No parity, 1 stop bit). * **Debugging Logic**: * **Garbage Characters?**: Baud rate mismatch or clock drift (check internal RC oscillator). * **TX but no RX?**: Check TX/RX swap. * **Missing Data?**: Buffer overflow. Use DMA or ring buffers for non-blocking logging. ## 2. I2C (Inter-Integrated Circuit) * **Pull-ups**: Ensure SDA/SCL have 4.7k - 10k resistors to VCC. * **Scanning**: Use an I2C scanner script to verify slave address (7-bit vs 8-bit notation). * **Stuck Bus**: If SDA is stuck LOW, clock the SCL 9 times manually to reset slave state. * **Speed**: Start at 100kHz (Standard Mode) before attempting 400kHz (Fast Mode). ## 3. SPI (Serial Peripheral Interface) * **Mode**: Verify CPOL/CPHA settings (Modes 0-3). Incorrect mode causes bit-shifted data. * **Chip Select (CS)**: Must be pulled LOW for the duration of the entire frame. * **Signal Integrity**: For long leads, reduce clock speed. ## 4. Hardware Safety & Probing * **Common Ground**: MUST connect logic analyzer ground to target ground. * **Voltage Levels**: Ensure 3.3V vs 5V compatibility. Use level shifters if necessary. * **Logic Analyzer**: Prefer PulseView/Sigrok for protocol decoding over raw oscilloscope traces for complex transactions.
Related Skills
usb-debug
No description provided.
register-debug
No description provided.
lora-debug
No description provided.
Skill: Debugging & Testing Standards
> **Skill ID**: `SKILL_DEBUGGING`
ble-debug
No description provided.
vuln-scan
Multi-language dependency security scan - Use Safety CLI and OSV-Scanner to quickly detect dependency vulnerabilities in Python/JS/Java projects
SKILL_ONBOARDING.md
> **Purpose**: Conduct a one-time "Handshake Interview" with the user to establish their Developer Persona.
sql-lint
SQL code style check - Use SQLFluff to check SQL statement style and syntax (supports PostgreSQL, MySQL, SQLite, etc.)
security-check
Check dependency security vulnerabilities
rust-lint
Rust code quality check - Use Clippy and Rustfmt to ensure Rust code standards and performance optimization
run-tests
Run project test suite
owasp-scan
OWASP dependency vulnerability scan - Use OWASP Dependency-Check to detect known CVE vulnerabilities in project dependencies