PlotJuggler 4 Perf Profiling
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis.
Install Kernel Debugging Advanced
$ npx skills add mohitmishra786/low-level-dev-skills --skill kernel-debugging-advanced -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills kernel-debugging-advanced --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/kernel-dev/kernel-debugging-advanced .claude/skills/kernel-debugging-advanced && 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 "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .claude/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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/kernel-dev/kernel-debugging-advancedType 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 kernel-debugging-advanced -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills kernel-debugging-advanced --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/kernel-dev/kernel-debugging-advanced .agents/skills/kernel-debugging-advanced && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .agents/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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 kernel-debugging-advanced -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills kernel-debugging-advanced --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/kernel-dev/kernel-debugging-advanced .cursor/skills/kernel-debugging-advanced && 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 "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .cursor/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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/kernel-dev/kernel-debugging-advanced--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 kernel-debugging-advanced -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills kernel-debugging-advanced --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/kernel-dev/kernel-debugging-advanced .gemini/skills/kernel-debugging-advanced && 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 "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .gemini/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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 kernel-debugging-advancedInstalls 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 kernel-debugging-advanced -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/kernel-dev/kernel-debugging-advanced .github/skills/kernel-debugging-advanced && 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 "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .github/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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 kernel-debugging-advanced -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 kernel-debugging-advanced --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/kernel-dev/kernel-debugging-advanced .opencode/skills/kernel-debugging-advanced && 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 "kernel-debugging-advanced" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/kernel-debugging-advanced into .opencode/skills/kernel-debugging-advanced/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-debugging-advanced", 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
kernel-debugging-advanced- GitHub stars
- 253
- Token cost
- ~855 tokens
- SKILL.md length
- 192 words
- Files
- 1
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- MIT
At a glance
Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis.
- Works in 8 steps: ftrace function graph → trace-cmd record → perf in kernel context → …
- Tracing kernel functions
- 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
Kernel Debugging Advanced is an agent skill from mohitmishra786/low-level-dev-skills. Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis. Use when tracing kernel functions, profiling syscalls in kernel, dynamic instrumentation, or analyzing vmcore. Activates on queries about ftrace, trace-cmd, kprobe, kgdb, kernel crash dump, or dyndbg.
Its SKILL.md is about 860 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, covering Debugging, Mobile performance and Observability. It works with Linux. 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
- Tracing kernel functions
- Profiling syscalls in kernel
- Dynamic instrumentation
- Analyzing vmcore
Example prompts
- “/kernel-debugging-advanced”
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 c).
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
Kernel Debugging Advanced loads about 855 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 192 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). 192 words, ~855 tokens.
Download SKILL.mdSave it as
.claude/skills/kernel-debugging-advanced/SKILL.md (or your agent's skills folder).- name
- kernel-debugging-advanced
- description
- Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis. Use when tracing kernel functions, profiling syscalls in kernel, dynamic instrumentation, or analyzing vmcore. Activates on queries about ftrace, trace-cmd, kprobe, kgdb, kernel crash dump, or dyndbg.
Advanced Kernel Debugging
Purpose
Extend skills/kernel/kernel-debugging with production-grade tracing: ftrace, trace-cmd, kernel perf, kprobes/kretprobes, kgdb, crash dump analysis, and printk discipline. Not merged with kernel-debugging — that skill covers baseline kgdb/dyndbg; this one focuses on trace-cmd, function_graph, and live/post-mortem production workflows.
When to Use
- Latency spikes in kernel driver without obvious bug
- Tracing function call graph in kernel
- Live inspection without recompiling (kprobes, bpf)
- Post-mortem
vmcoreafter panic
Workflow
1. ftrace function graph
# Enable function graph tracer
echo function_graph > /sys/kernel/debug/tracing/current_tracer
echo my_driver_probe > /sys/kernel/debug/tracing/set_graph_function
echo 1 > /sys/kernel/debug/tracing/tracing_on
# reproduce issue
cat /sys/kernel/debug/tracing/trace
echo 0 > /sys/kernel/debug/tracing/tracing_onRequires CONFIG_FUNCTION_GRAPH_TRACER and debugfs mounted.
2. trace-cmd record
trace-cmd record -p function_graph -F my_probe
trace-cmd report
trace-cmd statPortable capture for sharing with others.
3. perf in kernel context
perf record -a -g -- sleep 10
perf report --stdio
perf probe --add my_driver:probeSee skills/profilers/linux-perf for userspace overlap.
4. kprobes (dynamic)
#include <linux/kprobes.h>
static struct kprobe kp = {
.symbol_name = "do_sys_open",
.pre_handler = handler,
};
register_kprobe(&kp);Use sparingly in production; prefer static tracepoints when available.
5. dyndbg and printk discipline
echo 'module mydriver +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file drivers/foo/*.c +p' > /sys/kernel/debug/dynamic_debug/controlpr_debug("state=%d\n", s); /* compile-time optional */
printk_ratelimited(KERN_WARNING "hw fault\n");6. kgdb / kdb
# kernel cmdline: kgdboc=ttyS0,115200 kgdbwait
echo g > /proc/sysrq-trigger # break into debugger (when configured)7. Crash dump (vmcore)
# after kdump capture
crash /usr/lib/debug/vmlinux vmcore
crash> bt
crash> dev -s8. Agent usage
/kernel-debugging-advanced Trace my_driver_ioctl latency with ftrace function_graphCommon Problems
| Symptom | Cause | Fix |
|---|---|---|
| Empty trace | Tracer not enabled | tracing_on; check current_tracer |
| ftrace overhead | Graph all functions | Filter with set_graph_function |
| kprobe fail | Inlined symbol | Try nearby symbol or static key |
| kgdb no connect | Wrong kgdboc tty | Match serial/USB gadget |
| crash no symbols | Missing debuginfo | Install linux-image-dbg / vmlinux |
Related Skills
skills/kernel/kernel-debugging— baseline kgdb, dyndbgskills/profilers/linux-perf— perf record/reportskills/observability/ebpf— BPF kprobe alternativeskills/kernel-dev/writing-char-drivers— ioctl trace targetsskills/debuggers/core-dumps— userspace core parallels
© 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/kernel-dev/kernel-debugging-advanced of mohitmishra786/low-level-dev-skills.
Open the folder on GitHubat commit bdc5847
Compare with similar skills
Kernel Debugging Advanced 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 |
|---|---|---|---|---|---|---|
| Kernel Debugging Advanced this skillmohitmishra786/low-level-dev-skills | 253 | — | ~855 | Automated safety check: Pass | MIT | |
| PlotJuggler 4 Perf ProfilingPlotJuggler/PlotJuggler | 6.2k | — | ~1.6k | Automated safety check: Notes | MPL-2.0 | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Dotnet Debuggingnovotnyllc/dotnet-artisan | 233 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Mecatl Perf MCP Interpretationstacklok/mecatl | 218 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| LoopX Performance Diagnosisloopx-project/loopx | 6.2k | — | ~880 | Automated safety check: Pass | Apache-2.0 |
Similar skills
The Art of Debugging
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
Dotnet Debugging
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
Mecatl Perf MCP Interpretation
stacklok/mecatl
Guides reading mecatl's perf MCP data to find why a running harness is slow, leaking goroutines or growing in memory, using cheap reads before any CPU capture.
LoopX Performance Diagnosis
loopx-project/loopx
Profiles a slow command or runtime you own with the right profiler for its language, using uninstrumented baseline timings and keeping raw profiling evidence local and private.
Advpl Debugging
thalysjuvenal/advpl-specialist
A skill your agent uses when the user asks to debug, diagnose, or fix an ADVPL/TLPP error on TOTVS Protheus -- compilation errors (syntax, missing includes, undeclared variables), runtime failures…
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 Kernel Debugging Advanced
What does Kernel Debugging Advanced do?
Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis. Kernel Debugging Advanced is an agent skill from mohitmishra786/low-level-dev-skills. Advanced kernel debugging skill for ftrace, trace-cmd, perf, kprobes, kgdb, and crash analysis.
When should I use Kernel Debugging Advanced?
Kernel Debugging Advanced fits situations like: tracing kernel functions; profiling syscalls in kernel; dynamic instrumentation; analyzing vmcore.
How do I install Kernel Debugging Advanced in Claude Code?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill kernel-debugging-advanced -a claude-code`. Or copy the skill folder (skills/kernel-dev/kernel-debugging-advanced in mohitmishra786/low-level-dev-skills) into .claude/skills/kernel-debugging-advanced in your project. Claude Code loads it when a task matches its description.
How do I install Kernel Debugging Advanced in Codex?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill kernel-debugging-advanced -a codex`. Or copy the skill folder (skills/kernel-dev/kernel-debugging-advanced in mohitmishra786/low-level-dev-skills) into .agents/skills/kernel-debugging-advanced in your project. Codex loads it when a task matches its description.
Can I use Kernel Debugging Advanced 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 kernel-debugging-advanced -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kernel-debugging-advanced, .gemini/skills/kernel-debugging-advanced, .github/skills/kernel-debugging-advanced and .opencode/skills/kernel-debugging-advanced in your project.
What does Kernel Debugging Advanced need to run?
SKILL.md names no scripts, command-line tools or credentials: Kernel Debugging Advanced is instructions for the agent only.
Does Kernel Debugging Advanced 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 Kernel Debugging Advanced 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 Kernel Debugging Advanced use?
Kernel Debugging Advanced 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 Kernel Debugging Advanced use?
About 855 tokens (SKILL.md is roughly 3.4k 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 Kernel Debugging Advanced?
Skills that share tags, products or a category with Kernel Debugging Advanced: PlotJuggler 4 Perf Profiling (PlotJuggler/PlotJuggler, 6.2k stars), The Art of Debugging (stas00/the-art-of-debugging, 1.7k stars), Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars) and Mecatl Perf MCP Interpretation (stacklok/mecatl, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kernel Debugging Advanced?
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.