Zephyr Debug
Use when reproducing or isolating the root cause of a Zephyr build, toolchain, QEMU, boot, board, or runtime failure.
Install
npx skills add processmission/agent-skills --skill zephyr-debuggit clone --depth 1 https://github.com/processmission/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/zephyr/zephyr-debug ~/.claude/skills/zephyr-debugPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Zephyr Debug ## Audit workflow For every non-trivial task that writes to the workspace, choose a stable task slug and keep agent-only records under: ```text .zephyr-skills/<agent-task>/ ├── audit.md # Baseline, decisions, evidence, verification, and gaps ├── commands.md # Redacted commands, working directories, and results ├── scripts/ # Intermediate debug documents, scripts, and harnesses ├── output/ # Non-Zephyr dependencies and temporary binaries └── logs/ # Decisive build, test, runtime, or diagnostic logs ``` Put every generated intermediate debugging document, debug script, and scaffolding or harness script, including Bash and Python scripts, under `scripts/`, never in a build directory. Put non-Zephyr third-party source or libraries acquired solely for the agent's task, and temporary binaries produced by agent-only probes or tools, under `output/`. Do not copy normal Zephyr build artifacts there. Keep other agent plans and temporary evidence in the same task directory. In a Git worktree, add `/.zephyr-skills/` to the repository-local exclude file returned by `git rev-parse --git-path info/exclude` before writing audit artifacts. Preserve existing entries, avoid duplicates, and verify before handoff that `git status --short` contains no `.zephyr-skills/` paths. Keep Zephyr-native build trees, binaries, and test outputs separate: honor a user-specified path, otherwise use defaults such as configured `build.dir-fmt`, `build/`, or
Details
- Skill name
zephyr-debug- Repository
- processmission/agent-skills
- Path
skills/zephyr/zephyr-debug/SKILL.md- License
- MIT
- Repo updated
- 8 October 2026
FAQ
What does the Zephyr Debug skill do?
Use when reproducing or isolating the root cause of a Zephyr build, toolchain, QEMU, boot, board, or runtime failure.
How do I install the Zephyr Debug skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add processmission/agent-skills --skill zephyr-debug. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Zephyr Debug popular?
It lives in processmission/agent-skills, which has 9 GitHub stars and 3 forks.
Related skills
De AI Writing
9processmission/agent-skills
Detect, mark, and remove AI writing tics from Chinese and English drafts, so the text reads normally: denser, clearer, free of phrasing that obstructs reading. Use to de-AI a text, strip filler or clichés, or clear editing notes out of the body. Applies language- and model-specific rule tables and keeps the editing process out of the article. It rewrites style; personality and authorship stay out of scope.
Docs Translate Zh
9processmission/agent-skills
Translate English technical documentation into faithful, natural Simplified Chinese with full-article context, reviewable RST or Markdown sources, and searchable bilingual terminology. Use for documentation translation, Chinese documentation maintenance, migration from fragmented PO translations, or verification of translated Sphinx sites and requested GitHub Pages deployment.
Interactive Gdb Debugging
9processmission/agent-skills
Drive GDB interactively through persistent tmux sessions for local binaries, remote targets, QEMU gdbstub connections, cross-debuggers, stepping, breakpoints, state inspection, and core-dump analysis. Use when a task needs gdb, gdb-multiarch, an architecture-specific GDB, QEMU -s -S, target remote, or an adaptive debugging workflow that must react to debugger output.
Brainstorm
9claudekit/skillmark
Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.
Zap
8KyberNetwork/kyberswap-skills
This skill should be used when the user asks to "zap into a pool", "add liquidity", "zap in", "provide liquidity", "LP into", "zap out", "remove liquidity from pool", "withdraw from position", "migrate position", "move liquidity", "migrate LP", "rebalance position", or wants to add, remove, or migrate liquidity in concentrated liquidity pools in one transaction. Uses KyberSwap Zap as a Service (ZaaS) API to handle token ratio calculation, swaps, and deposits in a single transaction across 13 EVM chains.
Code Review
9claudekit/skillmark
Review code quality, receive feedback with technical rigor, verify completion claims. Use before PRs, after implementing features, when claiming task completion, for subagent reviews.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.