Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .claude/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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.
Type 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.
skills CLI
$ npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .agents/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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.
skills CLI
$ npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .cursor/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .gemini/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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.
Installs 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).
skills CLI
$ npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .github/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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.
skills CLI
$ npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "rust-debugging" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/rust/rust-debugging into .opencode/skills/rust-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-debugging", 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
rust-debugging
GitHub stars
253
Token cost
~1.6k tokens
SKILL.md length
252 words
Files
2 (incl. references)
Skills in repo
138
Repo updated
First seen
Licence
MIT
At a glance
Rust debugging skill for systems programming. An agent skill from mohitmishra786/low-level-dev-skills.
Works in 8 steps: Build for debugging → GDB with Rust pretty-printers → LLDB with Rust pretty-printers → …
Debugging Rust binaries with GDB
SKILL.md covers Purpose, Triggers, Workflow and Related skills
Calls cargo
What it does
Rust Debugging is an agent skill from mohitmishra786/low-level-dev-skills. Rust debugging skill for systems programming. Use when debugging Rust binaries with GDB or LLDB, enabling Rust pretty-printers, interpreting panics and backtraces, debugging async/await with tokio-console, stepping through nostd code, or using dbg! and tracing macros effectively. Activates on queries about rust-gdb, rust-lldb, RUSTBACKTRACE, Rust panics, debugging async Rust, tokio-console, or pretty-printers.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rust-gdb-pretty-printers.md`).
It sits in Development, covering Debugging, Async programming and Observability. It works with Rust. 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
Debugging Rust binaries with GDB
Enabling Rust pretty-printers
Interpreting panics and backtraces
Debugging async/await with tokio-console
Example prompts
“/rust-debugging”
Requirements
Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
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
Shell commands in SKILL.md call:
cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Rust Debugging loads about 1.6k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 252 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~108
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~2.7k
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.
Download SKILL.mdSave it as .claude/skills/rust-debugging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
rust-debugging
description
Rust debugging skill for systems programming. Use when debugging Rust binaries with GDB or LLDB, enabling Rust pretty-printers, interpreting panics and backtraces, debugging async/await with tokio-console, stepping through no_std code, or using dbg! and tracing macros effectively. Activates on queries about rust-gdb, rust-lldb, RUST_BACKTRACE, Rust panics, debugging async Rust, tokio-console, or pretty-printers.
Rust Debugging
Purpose
Guide agents through debugging Rust programs: GDB/LLDB with Rust pretty-printers, backtrace configuration, panic triage, async debugging with tokio-console, and #[no_std] debugging strategies.
Triggers
"How do I use GDB/LLDB to debug a Rust binary?"
"How do I get a full backtrace from a Rust panic?"
"How do I debug async Rust / Tokio?"
"Rust pretty-printers aren't working in GDB"
"How do I debug a Rust panic in production?"
"How do I use dbg! and tracing in Rust?"
Workflow
1. Build for debugging
bash
# Debug build (default) — full debug info, no optimization
cargo build
# Release with debug info (for profiling real workloads)
cargo build --release --profile release-with-debug
# Or configure in Cargo.toml:
# [profile.release-with-debug]
# inherits = "release"
# debug = true
# Run directly
cargo run
cargo run -- arg1 arg2
2. GDB with Rust pretty-printers
bash
# Use rust-gdb wrapper (sets up pretty-printers automatically)
rust-gdb target/debug/myapp
# Or set up manually in ~/.gdbinit:
# python
# import subprocess, sys
# ...
Common GDB session for Rust:
gdb
# Basic
(gdb) break main
(gdb) run arg1 arg2
(gdb) next # step over
(gdb) step # step into
(gdb) continue
# Rust-aware inspection
(gdb) print my_string # Shows String content via pretty-printer
(gdb) print my_vec # Shows Vec elements
(gdb) print my_option # Shows Some(value) or None
(gdb) info locals
# Break on panic
(gdb) break rust_panic
(gdb) break core::panicking::panic
# Backtrace
(gdb) bt # Short backtrace
(gdb) bt full # Full with locals
(lldb) b main::main
(lldb) r arg1 arg2
(lldb) n # next (step over)
(lldb) s # step into
(lldb) c # continue
(lldb) frame variable # show locals
(lldb) p my_string # print variable with pretty-printer
(lldb) bt # backtrace
(lldb) bt all # all threads
4. Backtrace configuration
bash
# Short backtrace (default on panic)
RUST_BACKTRACE=1 ./myapp
# Full backtrace with all frames
RUST_BACKTRACE=full ./myapp
# With symbols (requires debug build or separate debug info)
RUST_BACKTRACE=full ./target/debug/myapp
# Capture backtrace programmatically
use std::backtrace::Backtrace;
let bt = Backtrace::capture();
eprintln!("{bt}");
For release binaries, keep debug symbols in a separate file:
bash
# Build release with debug info
cargo build --release
objcopy --only-keep-debug target/release/myapp target/release/myapp.debug
strip --strip-debug target/release/myapp
objcopy --add-gnu-debuglink=target/release/myapp.debug target/release/myapp
5. Panic triage
rust
// Set a custom panic hook for structured logging
use std::panic;
panic::set_hook(Box::new(|info| {
let backtrace = std::backtrace::Backtrace::force_capture();
eprintln!("PANIC: {info}");
eprintln!("{backtrace}");
// Log to file, send to Sentry, etc.
}));
Common panic patterns:
Panic message
Likely cause
index out of bounds: the len is N but the index is M
Array/vec OOB access
called Option::unwrap() on a None value
Unwrap on None
called Result::unwrap() on an Err value
Unwrap on error
attempt to subtract with overflow
Integer underflow (debug build)
assertion failed
Failed assert! or assert_eq!
stack overflow
Infinite recursion
Use panic = "abort" in release to get a crash dump instead of unwind.
6. The dbg! macro
rust
// dbg! prints file, line, value and returns the value
let result = dbg!(some_computation(x));
// prints: [src/main.rs:15] some_computation(x) = 42
// Chain multiple values
let (a, b) = dbg!((compute_a(), compute_b()));
// Inspect inside iterator chains
let sum: i32 = (0..10)
.filter(|x| dbg!(x % 2 == 0))
.map(|x| dbg!(x * x))
.sum();
7. Structured logging with tracing
toml
[dependencies]
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
rust
use tracing::{debug, error, info, instrument, warn};
#[instrument] // Auto-traces function entry/exit with arguments
fn process(id: u64, data: &str) -> Result<(), Error> {
debug!("Processing item");
info!(item_id = id, "Started processing");
if data.is_empty() {
warn!(item_id = id, "Empty data");
return Err(Error::EmptyData);
}
error!(item_id = id, err = ?some_result, "Failed");
Ok(())
}
// Initialize in main
tracing_subscriber::fmt()
.with_env_filter("myapp=debug,warn")
.init();
bash
# Control log levels at runtime
RUST_LOG=debug ./myapp
RUST_LOG=myapp::module=trace,warn ./myapp
8. Async debugging with tokio-console
toml
[dependencies]
console-subscriber = "0.3"
tokio = { version = "1", features = ["full", "tracing"] }
rust
// In main
console_subscriber::init();
bash
# Install and run tokio-console
cargo install tokio-console
tokio-console # Connects to running Rust process at port 6669
Rust Debugging 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.
Rust Debugging compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Rust Debugging this skillmohitmishra786/low-level-dev-skills
Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe debugging techniques with…
Deploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside…
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
Guides reading and writing AArch64 and ARM Thumb assembly: compiler output, inline asm, registers, the AAPCS calling convention and NEON or SVE basics.
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.
Rust debugging skill for systems programming. An agent skill from mohitmishra786/low-level-dev-skills. Rust Debugging is an agent skill from mohitmishra786/low-level-dev-skills. Rust debugging skill for systems programming.
When should I use Rust Debugging?
Rust Debugging fits situations like: debugging Rust binaries with GDB; enabling Rust pretty-printers; interpreting panics and backtraces; debugging async/await with tokio-console.
How do I install Rust Debugging in Claude Code?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a claude-code`. Or copy the skill folder (skills/rust/rust-debugging in mohitmishra786/low-level-dev-skills) into .claude/skills/rust-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Rust Debugging in Codex?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill rust-debugging -a codex`. Or copy the skill folder (skills/rust/rust-debugging in mohitmishra786/low-level-dev-skills) into .agents/skills/rust-debugging in your project. Codex loads it when a task matches its description.
Can I use Rust Debugging 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 rust-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-debugging, .gemini/skills/rust-debugging, .github/skills/rust-debugging and .opencode/skills/rust-debugging in your project.
What does Rust Debugging need to run?
Going by SKILL.md and its folder, Rust Debugging needs the command-line tools its instructions call (cargo). Our summary lists: Python 3.
Does Rust Debugging access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rust Debugging 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 Rust Debugging use?
Rust Debugging 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 Rust Debugging use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Rust Debugging?
Skills that share tags, products or a category with Rust Debugging: Debugging Techniques (ancoleman/ai-design-components, 526 stars), Operating Livekit Agents (livekit-examples/agent-starter-python, 264 stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars) and YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rust Debugging?
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.