Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Protocol analysis skill for serial bus debugging. An agent skill from mohitmishra786/low-level-dev-skills.
Install Protocol Analysis
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qemu/protocol-analysis .claude/skills/protocol-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .claude/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qemu/protocol-analysis .agents/skills/protocol-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .agents/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qemu/protocol-analysis .cursor/skills/protocol-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .cursor/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitmishra786/low-level-dev-skills.git --path skills/qemu/protocol-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qemu/protocol-analysis .gemini/skills/protocol-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .gemini/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qemu/protocol-analysis .github/skills/protocol-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .github/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills protocol-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qemu/protocol-analysis .opencode/skills/protocol-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "protocol-analysis" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/qemu/protocol-analysis into .opencode/skills/protocol-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "protocol-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
protocol-analysis- GitHub stars
- 253
- Token cost
- ~781 tokens
- SKILL.md length
- 236 words
- Files
- 1
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- MIT
At a glance
Protocol analysis skill for serial bus debugging. An agent skill from mohitmishra786/low-level-dev-skills.
- Works in 8 steps: Capture stack → PulseView quick start → I2C decode expectations → …
- Decoding I2C/SPI/UART with logic analyzer concepts
- SKILL.md covers Purpose, When to Use, Workflow and Common Problems, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Protocol Analysis is an agent skill from mohitmishra786/low-level-dev-skills. Protocol analysis skill for serial bus debugging. Use when decoding I2C/SPI/UART with logic analyzer concepts, sigrok/PulseView, or Python capture scripts. Activates on queries about logic analyzer, sigrok, PulseView, decode I2C SPI UART, or bus protocol capture.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Python. The repository describes itself as: A curated suite of AI agent skills for systems and low-level programming with C/C++, Rust, and Zig toolchains, covering compilers, debuggers, profilers, build systems…. The licence is MIT.
When your agent uses it
- Decoding I2C/SPI/UART with logic analyzer concepts
- Sigrok/PulseView
- Python capture scripts
Example prompts
- “/protocol-analysis”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bdc5847. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
sigrok.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Protocol Analysis loads about 781 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 236 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitmishra786/low-level-dev-skills at commit bdc5847, republished under its MIT licence (© mohitmishra786). 236 words, ~781 tokens.
Download SKILL.mdSave it as
.claude/skills/protocol-analysis/SKILL.md (or your agent's skills folder).- name
- protocol-analysis
- description
- Protocol analysis skill for serial bus debugging. Use when decoding I2C/SPI/UART with logic analyzer concepts, sigrok/PulseView, or Python capture scripts. Activates on queries about logic analyzer, sigrok, PulseView, decode I2C SPI UART, or bus protocol capture.
Protocol Analysis (I2C / SPI / UART)
Purpose
Guide agents through software-side serial bus analysis: logic analyzer workflow, sigrok/PulseView decoding, correlating captures with firmware drivers, and Python-based parsing — bridging skills/baremetal/spi-i2c-baremetal and hardware bring-up.
When to Use
- Sensor not responding — verify clock and data on bus
- Compare kernel driver transactions vs datasheet
- Document expected transaction format for CI/regression
- Teaching protocol layers without expensive lab gear (sim + decode)
Workflow
1. Capture stack
Physical probe → logic analyzer hardware (or GPIO bit-bang)
├── sigrok-cli / PulseView GUI
├── Protocol decoder (i2c, spi, uart)
└── Export VCD/CSV for scriptsOpen-source: sigrok with cheap FX2LA boards.
2. PulseView quick start
# List devices
pulseview
# CLI capture (device-dependent)
sigrok-cli --driver fx2lafw --config samplerate=1MHz \
--channels 0=SDA,1=SCL \
--samples 1m \
--protocols i2c3. I2C decode expectations
| Phase | Lines |
|---|---|
| START | SDA fall while SCL high |
| Address + R/W | 7 bits + ACK |
| Data bytes | ACK per byte |
| STOP | SDA rise while SCL high |
NACK at address → wrong 0x48 or device held in reset.
4. SPI decode
Check mode (CPOL/CPHA), bit order (MSB first typical), CS polarity, and word size. Compare to spi_setup() in skills/kernel-dev/bus-drivers-i2c-spi.
5. UART decode
Set baud (9600/115200), frame (8N1), and signal polarity. Async — sample rate must be ≥ 4× baud for LA.
6. Python post-process (csv)
import csv
with open("capture.csv") as f:
for ts, ch0, ch1 in csv.reader(f):
# edge detect, reconstruct bits
pass7. Correlate with firmware
Logic capture timestamp
├── Match driver reg write sequence
├── Compare inter-byte delay vs datasheet max
└── Flag extra clock pulses (mode fault)8. Agent usage
/protocol-analysis Decode this I2C capture — device NACKs after register 0x0F writeCommon Problems
| Symptom | Cause | Fix |
|---|---|---|
| Garbage decode | Wrong samplerate | ≥ 4× bus speed |
| Floating lines | Missing pull-ups | Enable internal pull or external |
| SPI shifted bits | Mode mismatch | CPOL/CPHA table from RM |
| UART framing errors | Baud drift | Measure actual bit time |
| No decoder | Missing sigrok build | Install sigrok-cli + decoders |
Related Skills
skills/baremetal/spi-i2c-baremetal— firmware-side protocolskills/baremetal/uart-serial-baremetal— UART configskills/kernel-dev/bus-drivers-i2c-spi— kernel transactionsskills/profilers/strace-ltrace— userspace syscall trace analogskills/embedded/openocd-jtag— scope alongside SWD debug
© mohitmishra786, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/qemu/protocol-analysis of mohitmishra786/low-level-dev-skills.
Open the folder on GitHubat commit bdc5847
Compare with similar skills
Protocol Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Protocol Analysis this skillmohitmishra786/low-level-dev-skills | 253 | — | ~781 | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Merge Dependabot PRsonyx-dot-app/onyx | 32k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| LangBot Plugin Developmentlangbot-app/LangBot | 18k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Senior Architect Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 7 repos | ~1.2k | Automated safety check: Notes | Custom licence |
Similar skills
Merge Dependabot PRs
onyx-dot-app/onyx
Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
LangBot Plugin Development
langbot-app/LangBot
Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.
Senior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Flowsint Enricher Builder
reconurge/flowsint
Guides building Flowsint enrichers and types: where definitions live, how the base class and vault work, and when a new type is warranted.
More from mohitmishra786/low-level-dev-skills
All 138 skills in this repoARM and AArch64 Assembly
mohitmishra786/low-level-dev-skills
Guides reading and writing AArch64 and ARM Thumb assembly: compiler output, inline asm, registers, the AAPCS calling convention and NEON or SVE basics.
RISC-V Assembly Guide
mohitmishra786/low-level-dev-skills
Reference for RISC-V assembly on RV32 and RV64: register names and calling convention, extension naming, GCC and Clang inline asm, and QEMU with GDB debugging.
x86-64 Assembly Reference
mohitmishra786/low-level-dev-skills
Explains x86-64 registers, the System V AMD64 calling convention, and how to read compiler-generated or inline assembly.
Bazel for C and C++
mohitmishra786/low-level-dev-skills
Guides your agent through Bazel for C/C++ projects: BUILD files, Bzlmod dependencies, toolchain registration, remote execution, dependency queries and sandbox debugging.
Binary Hardening
mohitmishra786/low-level-dev-skills
Binary hardening skill for security-hardened C/C++ builds. An agent skill from mohitmishra786/low-level-dev-skills.
Binutils
mohitmishra786/low-level-dev-skills
GNU binutils skill for binary manipulation and analysis. An agent skill from mohitmishra786/low-level-dev-skills.
Related
Works with
Categories
Questions about Protocol Analysis
What does Protocol Analysis do?
Protocol analysis skill for serial bus debugging. An agent skill from mohitmishra786/low-level-dev-skills. Protocol Analysis is an agent skill from mohitmishra786/low-level-dev-skills. Protocol analysis skill for serial bus debugging.
When should I use Protocol Analysis?
Protocol Analysis fits situations like: decoding I2C/SPI/UART with logic analyzer concepts; sigrok/PulseView; Python capture scripts.
How do I install Protocol Analysis in Claude Code?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a claude-code`. Or copy the skill folder (skills/qemu/protocol-analysis in mohitmishra786/low-level-dev-skills) into .claude/skills/protocol-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Protocol Analysis in Codex?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a codex`. Or copy the skill folder (skills/qemu/protocol-analysis in mohitmishra786/low-level-dev-skills) into .agents/skills/protocol-analysis in your project. Codex loads it when a task matches its description.
Can I use Protocol Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitmishra786/low-level-dev-skills --skill protocol-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/protocol-analysis, .gemini/skills/protocol-analysis, .github/skills/protocol-analysis and .opencode/skills/protocol-analysis in your project.
What does Protocol Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Protocol Analysis is instructions for the agent only. Our summary lists: Python 3.
Does Protocol Analysis access the network?
SKILL.md names 1 domain. As links in the text: sigrok.org. This is read from the text; nothing was executed.
Is Protocol Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Protocol Analysis use?
Protocol Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Protocol Analysis use?
About 781 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Protocol Analysis?
Skills that share tags, products or a category with Protocol Analysis: Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars), Kedro Babysit (kedro-org/kedro, 11k stars) and LangBot Plugin Development (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Protocol Analysis?
mohitmishra786 (a GitHub user) maintains it in mohitmishra786/low-level-dev-skills, which has 253 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on June 27, 2026.
Source: mohitmishra786/low-level-dev-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.